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

KLOPPEDALEN BOLIGSAMEIE

Org. no. 990302081 Condominium flat owner (ESEK) Oslo Incorporated 1984 Active
Revenue 2025 NOK 1.4m
Operating profit NOK 267,000
Equity NOK −4.1m
Incorporated 1984

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4,1 mill kr).

KLOPPEDALEN BOLIGSAMEIE is registered as a condominium flat owner in Oslo, Oslo with organisation number 990302081. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1984. The company's stated purpose is: “Ivareta sameiernes fellesinteresser og administrasjonen av eiendommen, gnr 79, bnr 169 og 199 i Asker kommune, med fellesanlegg av enhver art. Vedlikehold og utbedringer som vil sikre den enkelte seksjon og eiendom verdistigning.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 267,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
▲ +2 %
Operating profit
NOK 267,000
▼ −32 %
Equity
NOK −4.1m
▼ −1 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
2.74
Very good
Current assets ÷ current liabilities
Profitability
45.1%
Very good
Return on total assets
Solidity
-681.2%
Weak
Equity as a share of total capital

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

Who owns KLOPPEDALEN BOLIGSAMEIE?

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

Frequently asked questions about KLOPPEDALEN BOLIGSAMEIE

What is the revenue of KLOPPEDALEN BOLIGSAMEIE?

KLOPPEDALEN BOLIGSAMEIE had revenue of NOK 1.4m in 2025.

Where is KLOPPEDALEN BOLIGSAMEIE based?

KLOPPEDALEN BOLIGSAMEIE 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.