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

OREBAKKEN BORETTSLAG

Org. no. 950444932 Housing cooperative (BRL) Oslo Incorporated 1973 Active
Ownership graph ↗
Revenue 2025 NOK 23.6m
Operating profit NOK 2.6m
Equity NOK 42.1m
Incorporated 1973

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

Key figures · 2025

Revenue
NOK 23.6m
Operating profit
NOK 2.6m
Equity
NOK 42.1m
Est. value
NOK 29.3m

Financial health · 2025

Liquidity
10.05
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
53.8%
Very good
Equity as a share of total capital

Who owns OREBAKKEN BORETTSLAG?

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

Frequently asked questions about OREBAKKEN BORETTSLAG

What is the revenue of OREBAKKEN BORETTSLAG?

OREBAKKEN BORETTSLAG had revenue of NOK 23.6m in 2025.

Where is OREBAKKEN BORETTSLAG based?

OREBAKKEN BORETTSLAG has its business address in Oslo.

Property

Business address c/o 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.