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

BOLIGSAMEIET IDUNS GATE 2

Org. no. 987726474 Condominium flat owner (ESEK) Oslo Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK −587,000
Equity NOK −7.2m
Incorporated 1996

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7,2 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−587k kr).
  • Nylig endring 2026-05-21 Adresseendring registrert 2026-05-21.

BOLIGSAMEIET IDUNS GATE 2 is registered as a condominium flat owner in Oslo, Oslo with organisation number 987726474. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1996. The company's stated purpose is: “Eierseksjonssameie.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK −587,000 in operating profit.

Former names: BOLIGSAMEIET IDUNSGATE 2

Key figures · 2025

Revenue
NOK 4.6m
▲ +156 %
Operating profit
NOK −587,000
▲ +91 %
Equity
NOK −7.2m
▼ −20 %

Financial health · 2025

Liquidity
10.83
Very good
Current assets ÷ current liabilities
Profitability
-27.9%
Not satisfactory
Return on total assets
Solidity
-377.8%
Weak
Equity as a share of total capital

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

Who owns BOLIGSAMEIET IDUNS GATE 2?

No shareholders are registered for BOLIGSAMEIET IDUNS GATE 2 in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BOLIGSAMEIET IDUNS GATE 2

What is the revenue of BOLIGSAMEIET IDUNS GATE 2?

BOLIGSAMEIET IDUNS GATE 2 had revenue of NOK 4.6m in 2025.

Where is BOLIGSAMEIET IDUNS GATE 2 based?

BOLIGSAMEIET IDUNS GATE 2 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.