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

SAMEIET MARIDALSVEIEN 9

Org. no. 971275987 Condominium flat owner (ESEK) Oslo Incorporated 1984 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 380,000
Equity NOK −61,000
Incorporated 1984

Signals

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

SAMEIET MARIDALSVEIEN 9 is registered as a condominium flat owner in Oslo, Oslo with organisation number 971275987. 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 administrasjon av eiendommen Gnr 218 Bnr 105 i Oslo kommune, med fellesanlegg av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 380,000 in operating profit.

Former names: SAMEIET MARIDALSVEIEN 9 A B C V/ADV.WELLEN & HAGELUND, SAMEIET MARIDALSVEIEN 9 A

Key figures · 2025

Revenue
NOK 3.0m
▲ +5 %
Operating profit
NOK 380,000
▲ +32 %
Equity
NOK −61,000
▲ +45 %
Est. value
NOK 854,000

Financial health · 2025

Liquidity
2.96
Very good
Current assets ÷ current liabilities
Profitability
9.1%
Satisfactory
Return on total assets
Solidity
-1.5%
Weak
Equity as a share of total capital

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

Who owns SAMEIET MARIDALSVEIEN 9?

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

Frequently asked questions about SAMEIET MARIDALSVEIEN 9

What is the revenue of SAMEIET MARIDALSVEIEN 9?

SAMEIET MARIDALSVEIEN 9 had revenue of NOK 3.0m in 2025.

Where is SAMEIET MARIDALSVEIEN 9 based?

SAMEIET MARIDALSVEIEN 9 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.