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

KANALPARKEN 1 BORETTSLAG

Org. no. 833065572 Housing cooperative (BRL) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 25.4m
Operating profit NOK 22.5m
Equity NOK 34.7m
Incorporated 2024

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

Key figures · 2025

Revenue
NOK 25.4m
Operating profit
NOK 22.5m
Equity
NOK 34.7m
Est. value
NOK 73.5m

Financial health · 2025

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

Who owns KANALPARKEN 1 BORETTSLAG?

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

Frequently asked questions about KANALPARKEN 1 BORETTSLAG

What is the revenue of KANALPARKEN 1 BORETTSLAG?

KANALPARKEN 1 BORETTSLAG had revenue of NOK 25.4m in 2025.

Where is KANALPARKEN 1 BORETTSLAG based?

KANALPARKEN 1 BORETTSLAG has its business address in Oslo.

Property

Business address 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.