BIZTRAC BETA
Uoppgitt

PROSANO AS

Org. no. 967271748 Limited company (AS) Oslo Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −469,000
Equity NOK 47.9m
Incorporated 1993
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−469k kr).
  • Nylig endring 2026-03-09 Adresseendring registrert 2026-03-09.

PROSANO AS is registered as a limited company in Oslo, Oslo with organisation number 967271748. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 1993. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Delta i andre selskaper, eie fast eiendom og verdipapirer, forskning og utvikling av biomaterialer, konsulentvirksomhet og alt som står i forbindelse. Eie næring innen forretningsdrift, konsulentvirksomhet og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −469,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −469,000
Equity
NOK 47.9m
Est. value
NOK 56.3m

Financial health · 2024

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

Who owns PROSANO AS?

JAN EIRIK ELLINGSEN
PROSANO AS
NOK 0 rev. · NOK −469,000 profit

PROSANO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PROSANO AS own?

PROSANO AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about PROSANO AS

Who owns PROSANO AS?

JAN EIRIK ELLINGSEN is the largest registered owner, with 100.0%.

What is the revenue of PROSANO AS?

PROSANO AS had revenue of NOK 0 in 2024.

Where is PROSANO AS based?

PROSANO AS has its business address in Oslo.

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.