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

HUSEBYBAKKEN BORETTSLAG

Org. no. 848305812 Housing cooperative (BRL) Oslo Incorporated 1965 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 649,000
Equity NOK 3.4m
Incorporated 1965

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

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK 649,000
Equity
NOK 3.4m
Est. value
NOK 3.1m

Financial health · 2025

Liquidity
1.79
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 HUSEBYBAKKEN BORETTSLAG?

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

Frequently asked questions about HUSEBYBAKKEN BORETTSLAG

What is the revenue of HUSEBYBAKKEN BORETTSLAG?

HUSEBYBAKKEN BORETTSLAG had revenue of NOK 4.3m in 2025.

Where is HUSEBYBAKKEN BORETTSLAG based?

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