biztrac. BETA
COMPANY REGISTER PROFILE
993071676 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

NORDBYHAGEN BOLIGSAMEIE, FELT B9

Org. no. 993071676 Condominium flat owner (ESEK) Oslo Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 331,000
Equity NOK −138,000
Incorporated 2008

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−138k kr).

NORDBYHAGEN BOLIGSAMEIE, FELT B9 is registered as a condominium flat owner in Oslo, Oslo with organisation number 993071676. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2008. The company's stated purpose is: “Ivareta driften av sameiet, administrere bruk og vedlikehold av fellesareale og ivareta alle andre saker av felles interesser for sameierne.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 331,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
▲ +39 %
Operating profit
NOK 331,000
▲ +58 %
Equity
NOK −138,000
▲ +66 %
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
10.07
Very good
Current assets ÷ current liabilities
Profitability
52.0%
Very good
Return on total assets
Solidity
-18.7%
Weak
Equity as a share of total capital

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

Who owns NORDBYHAGEN BOLIGSAMEIE, FELT B9?

No shareholders are registered for NORDBYHAGEN BOLIGSAMEIE, FELT B9 in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about NORDBYHAGEN BOLIGSAMEIE, FELT B9

What is the revenue of NORDBYHAGEN BOLIGSAMEIE, FELT B9?

NORDBYHAGEN BOLIGSAMEIE, FELT B9 had revenue of NOK 2.7m in 2025.

Where is NORDBYHAGEN BOLIGSAMEIE, FELT B9 based?

NORDBYHAGEN BOLIGSAMEIE, FELT B9 has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.