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

EIERSEKSJONSAMEIET MUNKEDAMSVEIEN 59

Org. no. 991808604 Condominium flat owner (ESEK) Oslo Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK −264,000
Equity NOK 344,000
Incorporated 2003

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−264k kr).

EIERSEKSJONSAMEIET MUNKEDAMSVEIEN 59 is registered as a condominium flat owner in Oslo, Oslo with organisation number 991808604. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2003. The company's stated purpose is: “Ivareta sameiernes fellesinteresser og administrasjon av eiendommern, gnr. 209, bnr. 235 i Oslo kommune, med fellesanlegg av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −264,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
▲ +12 %
Operating profit
NOK −264,000
▼ −304 %
Equity
NOK 344,000
▼ −43 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
2.17
Very good
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
54.0%
Very good
Equity as a share of total capital

Who owns EIERSEKSJONSAMEIET MUNKEDAMSVEIEN 59?

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

Frequently asked questions about EIERSEKSJONSAMEIET MUNKEDAMSVEIEN 59

What is the revenue of EIERSEKSJONSAMEIET MUNKEDAMSVEIEN 59?

EIERSEKSJONSAMEIET MUNKEDAMSVEIEN 59 had revenue of NOK 1.6m in 2025.

Where is EIERSEKSJONSAMEIET MUNKEDAMSVEIEN 59 based?

EIERSEKSJONSAMEIET MUNKEDAMSVEIEN 59 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.