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

ORREMYR BORETTSLAG

Org. no. 951081450 Housing cooperative (BRL) Oslo Incorporated 1971 Active
Ownership graph ↗
Revenue 2025 NOK 34.4m
Operating profit NOK 8.5m
Equity NOK 35.3m
Incorporated 1971

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

Key figures · 2025

Revenue
NOK 34.4m
Operating profit
NOK 8.5m
Equity
NOK 35.3m
Est. value
NOK 35.7m

Financial health · 2025

Liquidity
0.50
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.6%
Good
Equity as a share of total capital

Who owns ORREMYR BORETTSLAG?

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

Frequently asked questions about ORREMYR BORETTSLAG

What is the revenue of ORREMYR BORETTSLAG?

ORREMYR BORETTSLAG had revenue of NOK 34.4m in 2025.

Where is ORREMYR BORETTSLAG based?

ORREMYR BORETTSLAG has its business address in Oslo.

Property

Business address Odvar Solbergs vei 22, 0970 Oslo
Cadastral unit 301-96/64/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 36 units

6 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.