BIZTRAC BETA
Rental and operating of own or leased real estate

ØAV 88 AS

Org. no. 998468531 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 47.7m
Operating profit NOK −168.4m
Equity NOK −35.1m
Incorporated 2012
Share capital NOK 856,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−35,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−168,4 mill kr).

ØAV 88 AS is registered as a limited company in Oslo, Oslo with organisation number 998468531. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 856,000, divided into 856457 shares. The company's stated purpose is: “Ervervelse og utvikling av tomter og eiendommer for utleie og salg, samt drive slik aktivitet som naturlig faller innunder dette, herunder å eie andeler i andre selskap med tilsvarende aktivitet.”. The most recent filed accounts, for the 2024 financial year, show NOK 47.7m in revenue and NOK −168.4m in operating profit.

Key figures · 2024

Revenue
NOK 47.7m
Operating profit
NOK −168.4m
Equity
NOK −35.1m

Financial health · 2024

Liquidity
1.79
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-7.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ØAV 88 AS?

OSLO PENSJONSFORSIKRING AS
ØAV 88 AS
NOK 47.7m rev. · NOK −168.4m profit

ØAV 88 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØAV 88 AS

Who owns ØAV 88 AS?

OSLO PENSJONSFORSIKRING AS is the largest registered owner, with 100.0%.

What is the revenue of ØAV 88 AS?

ØAV 88 AS had revenue of NOK 47.7m in 2024.

Where is ØAV 88 AS based?

ØAV 88 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.