BIZTRAC BETA
Activities of housing cooperatives

ØVREVOLL BOLIGSELSKAP AS

Org. no. 930596183 Limited company (AS) Oslo Incorporated 1952 Active
Ownership graph ↗
Revenue 2024 NOK 6.4m
Operating profit NOK 2.2m
Equity NOK −13.0m
Incorporated 1952
Share capital NOK 116,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−13,0 mill kr).
  • Nylig endring 2026-05-19 Adresseendring registrert 2026-05-19.

ØVREVOLL BOLIGSELSKAP AS is registered as a limited company in Oslo, Oslo with organisation number 930596183. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1952. Registered share capital is NOK 116,000, divided into 105 shares. The company's stated purpose is: “Øvrevoll Boligselskap AS (Øvrevollkollektivet AS) er et aksjeselskap hvis formål er overtakelse av festekontrakt på g.nr. 20, b.nr. 333, Øvrevoll i Bærum samt bebyggelse og drift av eiendommen.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.4m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 6.4m
Operating profit
NOK 2.2m
Equity
NOK −13.0m
Est. value
NOK 9.4m

Financial health · 2024

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

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

Who owns ØVREVOLL BOLIGSELSKAP AS?

No shareholders are registered for ØVREVOLL BOLIGSELSKAP AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ØVREVOLL BOLIGSELSKAP AS

What is the revenue of ØVREVOLL BOLIGSELSKAP AS?

ØVREVOLL BOLIGSELSKAP AS had revenue of NOK 6.4m in 2024.

Where is ØVREVOLL BOLIGSELSKAP AS based?

ØVREVOLL BOLIGSELSKAP 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.