BIZTRAC BETA
Rental and operating of own or leased real estate

BERGEN HELSEHUS AS

Org. no. 891710232 Limited company (AS) Bergen Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 38.6m
Operating profit NOK 27.1m
Equity NOK 55.9m
Incorporated 2007
Share capital NOK 1.1m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BERGEN HELSEHUS AS is registered as a limited company in Bergen, Vestland with organisation number 891710232. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 1.1m, divided into 100000 shares. The company's stated purpose is: “Erverv, drift, forvaltning, utvikling og salg av fast eiendom direkte eller via eierineresser i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 38.6m in revenue and NOK 27.1m in operating profit.

Key figures · 2024

Revenue
NOK 38.6m
Operating profit
NOK 27.1m
Equity
NOK 55.9m
Est. value
NOK 87.8m

Financial health · 2024

Liquidity
0.69
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.2%
Satisfactory
Equity as a share of total capital

Who owns BERGEN HELSEHUS AS?

GC RIEBER EIENDOM AS
BERGEN HELSEHUS AS
NOK 38.6m rev. · NOK 27.1m profit

BERGEN HELSEHUS AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BERGEN HELSEHUS AS er morselskap for 34 datterselskaper:

Frequently asked questions about BERGEN HELSEHUS AS

Who owns BERGEN HELSEHUS AS?

GC RIEBER EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BERGEN HELSEHUS AS?

BERGEN HELSEHUS AS had revenue of NOK 38.6m in 2024.

Where is BERGEN HELSEHUS AS based?

BERGEN HELSEHUS AS has its business address in Bergen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.