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

BERG EIENDOM HARALDSVANG AS

Org. no. 985215847 Limited company (AS) Haugesund Incorporated 2002 Active
Ownership graph ↗
Operating profit NOK −37,000
Equity NOK 6.5m
Incorporated 2002
Share capital NOK 100,000

Signals

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

BERG EIENDOM HARALDSVANG AS is registered as a limited company in Haugesund, Rogaland with organisation number 985215847. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Erverv, utvikling, drift og salg av fast eiendom samt hva hermed står i forbindelse.”.

Former names: SVERRE EINAR BERG AS, ARBE EIENDOM HARALDSVANG AS

Key figures · 2025

Operating profit
NOK −37,000
▼ −49 %
Equity
NOK 6.5m
▲ +8 %
Est. value
NOK 6.2m

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 HARALDSVANG AS?

BERG EIENDOM HARALDSVANG AS
· NOK −37,000 profit

BERG EIENDOM HARALDSVANG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BERG EIENDOM HARALDSVANG AS own?

BERG EIENDOM HARALDSVANG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BERG EIENDOM HARALDSVANG AS

Who owns BERG EIENDOM HARALDSVANG AS?

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

Where is BERG EIENDOM HARALDSVANG AS based?

BERG EIENDOM HARALDSVANG 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.