biztrac. BETA
COMPANY REGISTER PROFILE
980629228 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

PROSEP (NORWAY) AS

Org. no. 980629228 Limited company (AS) Sandnes Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 12.9m
Operating profit NOK 2.1m
Equity NOK 38.1m
Incorporated 1999
Share capital NOK 6.0m

PROSEP (NORWAY) AS is registered as a limited company in Sandnes, Rogaland with organisation number 980629228. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 1999. Registered share capital is NOK 6.0m, divided into 13044 shares. The company's stated purpose is: “Utvikling av gassrenseteknologi, gass-separasjonsteknologi og alt som hermed står i forbindelse, herunder produksjon av tilliggende produkter, markedsføring, konsulentvirksomhet, kjøp og salg, deltakelse i andre selskaper etc.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.9m in revenue and NOK 2.1m in operating profit.

Former names: FRAMO PURIFICATION AS, PROPURE AS

Key figures · 2025

Revenue
NOK 12.9m
▼ −48 %
Operating profit
NOK 2.1m
▼ −70 %
Equity
NOK 38.1m
▼ −7 %
Est. value
NOK 28.5m

Financial health · 2025

Liquidity
0.57
Weak
Current assets ÷ current liabilities
Profitability
6.0%
Weak
Return on total assets
Solidity
47.8%
Very good
Equity as a share of total capital

Who owns PROSEP (NORWAY) AS?

PROSEP (NORWAY) AS
NOK 12.9m rev. · NOK 2.1m profit

PROSEP (NORWAY) AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROSEP (NORWAY) AS

Who owns PROSEP (NORWAY) AS?

PUREGROUP AS is the largest registered owner, with 100.0%.

What is the revenue of PROSEP (NORWAY) AS?

PROSEP (NORWAY) AS had revenue of NOK 12.9m in 2025.

Where is PROSEP (NORWAY) AS based?

PROSEP (NORWAY) AS has its business address in Sandnes.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.