BIZTRAC BETA
Other technical consultancy

PROSEP (NORWAY) AS

Org. no. 980629228 Limited company (AS) Sandnes Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 24.8m
Operating profit NOK 6.7m
Equity NOK 41.1m
Incorporated 1999
Share capital NOK 6.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

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 2024 financial year, show NOK 24.8m in revenue and NOK 6.7m in operating profit.

Key figures · 2024

Revenue
NOK 24.8m
Operating profit
NOK 6.7m
Equity
NOK 41.1m
Est. value
NOK 41.9m

Financial health · 2024

Liquidity
0.70
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
42.0%
Very good
Equity as a share of total capital

Who owns PROSEP (NORWAY) AS?

PUREGROUP AS
PROSEP (NORWAY) AS
NOK 24.8m rev. · NOK 6.7m 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 24.8m in 2024.

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 15.06.2026.

Report a problem

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