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

HAGO BURETTSLAG

Org. no. 832296902 Housing cooperative (BRL) Ringerike Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 1.4m
Equity NOK 281,000
Incorporated 2023

HAGO BURETTSLAG is registered as a housing cooperative in Ringerike, Buskerud with organisation number 832296902. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2023. The company's stated purpose is: “Borettslag”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 1.4m
Equity
NOK 281,000
Est. value
NOK 4.0m

Financial health · 2025

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

Who owns HAGO BURETTSLAG?

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

Frequently asked questions about HAGO BURETTSLAG

What is the revenue of HAGO BURETTSLAG?

HAGO BURETTSLAG had revenue of NOK 1.8m in 2025.

Where is HAGO BURETTSLAG based?

HAGO BURETTSLAG has its business address in Hønefoss.

Property

Business address v/Ringbo BBL Hvervenmoveien 49, 3511 Hønefoss
Cadastral unit 3305-38/209/0/0
Building Annen kontorbygning · 12 units

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