BIZTRAC BETA
Activities of housing cooperatives

BOLIGSELSKAPET FAGERHEIMSGATEN 9 AS

Org. no. 929918932 Limited company (AS) Oslo Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 1.6m
Equity NOK −14.7m
Incorporated 1990
Share capital NOK 130,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−14,7 mill kr).

BOLIGSELSKAPET FAGERHEIMSGATEN 9 AS is registered as a limited company in Oslo, Oslo with organisation number 929918932. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1990. Registered share capital is NOK 130,000. The company's stated purpose is: “Eie og drive eiendommen gnr. 227 bnr. 124 i Oslo med adresse Fagerheimgt. 9, 0567 Oslo samt organisere og forvalte andre tiltak som har sammenheng med aksjeeiernes bointeresser.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 1.6m
Equity
NOK −14.7m
Est. value
NOK 6.8m

Financial health · 2024

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

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

Who owns BOLIGSELSKAPET FAGERHEIMSGATEN 9 AS?

No shareholders are registered for BOLIGSELSKAPET FAGERHEIMSGATEN 9 AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BOLIGSELSKAPET FAGERHEIMSGATEN 9 AS

What is the revenue of BOLIGSELSKAPET FAGERHEIMSGATEN 9 AS?

BOLIGSELSKAPET FAGERHEIMSGATEN 9 AS had revenue of NOK 3.7m in 2024.

Where is BOLIGSELSKAPET FAGERHEIMSGATEN 9 AS based?

BOLIGSELSKAPET FAGERHEIMSGATEN 9 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.