BIZTRAC BETA
COMPANY REGISTER PROFILE
994483781 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Activities of housing cooperatives

MØLLEHJULET BORETTSLAG

Org. no. 994483781 Housing cooperative (BRL) Oslo Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 24.2m
Operating profit NOK 17.0m
Equity NOK 107.7m
Incorporated 2009

MØLLEHJULET BORETTSLAG is registered as a housing cooperative in Oslo, Oslo with organisation number 994483781. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2009. The company's stated purpose is: “Borettslag.”. The most recent filed accounts, for the 2025 financial year, show NOK 24.2m in revenue and NOK 17.0m in operating profit.

Key figures · 2025

Revenue
NOK 24.2m
Operating profit
NOK 17.0m
Equity
NOK 107.7m
Est. value
NOK 98.3m

Financial health · 2025

Liquidity
4.51
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
22.9%
Good
Equity as a share of total capital

Who owns MØLLEHJULET BORETTSLAG?

No shareholders are registered for MØLLEHJULET BORETTSLAG in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about MØLLEHJULET BORETTSLAG

What is the revenue of MØLLEHJULET BORETTSLAG?

MØLLEHJULET BORETTSLAG had revenue of NOK 24.2m in 2025.

Where is MØLLEHJULET BORETTSLAG based?

MØLLEHJULET BORETTSLAG has its business address in Oslo.

Property

Business address v/OBOS Hammersborg torg 1, 0179 Oslo
Cadastral unit 301-208/279/0/0

1650 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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