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

HELGERUD BOLIGSAMEIE

Org. no. 920758851 Condominium flat owner (ESEK) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Equity NOK 5.9m
Incorporated 2017

HELGERUD BOLIGSAMEIE is registered as a condominium flat owner in Bærum, Akershus with organisation number 920758851. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2017. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue.

Key figures · 2025

Revenue
NOK 2.8m
Equity
NOK 5.9m
Est. value
NOK 6.7m

Financial health · 2025

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

Who owns HELGERUD BOLIGSAMEIE?

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

Frequently asked questions about HELGERUD BOLIGSAMEIE

What is the revenue of HELGERUD BOLIGSAMEIE?

HELGERUD BOLIGSAMEIE had revenue of NOK 2.8m in 2025.

Where is HELGERUD BOLIGSAMEIE based?

HELGERUD BOLIGSAMEIE has its business address in Gjettum.

Property

Business address Dr. Schmidts vei 3A, 1346 Gjettum
Cadastral unit 3201-80/32/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 74 units

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