biztrac. BETA
COMPANY REGISTER PROFILE
934957695 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BERG EIENDOM KONSERN AS

Org. no. 934957695 Limited company (AS) Haugesund Incorporated 2025 Active
Operating profit NOK −2,000
Equity NOK 471.3m
Incorporated 2025
Share capital NOK 6.2m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).

BERG EIENDOM KONSERN AS is registered as a limited company in Haugesund, Rogaland with organisation number 934957695. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 6.2m, divided into 2035005 shares. The company's stated purpose is: “Være eierselskap for Berg Eiendom Haugaland AS, Berg Eiendom Raglamyr AS og andre selsaper under Berg-konsernet, og forvaltning av konsernets overskuddslikviditet, samt annen virksomhet fobundet med dette.”.

Key figures · 2025

Operating profit
NOK −2,000
Equity
NOK 471.3m
Est. value
NOK 430.0m

Financial health · 2025

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

Who owns BERG EIENDOM KONSERN AS?

BERG EIENDOM KONSERN AS has 10 registered shareholders:

All shareholders and roles →

Which companies does BERG EIENDOM KONSERN AS own?

BERG EIENDOM KONSERN AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

BERG EIENDOM KONSERN AS er morselskap for 2 datterselskaper:

Frequently asked questions about BERG EIENDOM KONSERN AS

Who owns BERG EIENDOM KONSERN AS?

Merete Iren Berg Hjorthaug is the largest registered owner, with 33.3%.

Where is BERG EIENDOM KONSERN AS based?

BERG EIENDOM KONSERN AS has its business address in Haugesund.

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

Report a problem

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