BIZTRAC BETA
Business and other management consultancy activities

UNNINVEST II AS

Org. no. 988139130 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 18.4m
Operating profit NOK 15.0m
Equity NOK 203.1m
Incorporated 2005
Share capital NOK 2.1m

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-23 Adresseendring registrert 2026-06-23.

UNNINVEST II AS is registered as a limited company in Oslo, Oslo with organisation number 988139130. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 2.1m, divided into 5000 shares. The company's stated purpose is: “Å drive virksomhet innenfor utvikling og investering i andre selskaper og alt som står i forbindelse med de forannevnte virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.4m in revenue and NOK 15.0m in operating profit.

Key figures · 2024

Revenue
NOK 18.4m
Operating profit
NOK 15.0m
Equity
NOK 203.1m
Est. value
NOK 170.5m

Financial health · 2024

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

Who owns UNNINVEST II AS?

OFFENTLIG EIENDOM AS
UNNINVEST II AS
NOK 18.4m rev. · NOK 15.0m profit

UNNINVEST II AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UNNINVEST II AS

Who owns UNNINVEST II AS?

OFFENTLIG EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of UNNINVEST II AS?

UNNINVEST II AS had revenue of NOK 18.4m in 2024.

Where is UNNINVEST II AS based?

UNNINVEST II 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.