BIZTRAC BETA
Rental and operating of own or leased real estate

GULLHAUG EIENDOM AS

Org. no. 989383779 Limited company (AS) Holmestrand Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 1.2m
Equity NOK 7.7m
Incorporated 2005
Share capital NOK 1.0m

GULLHAUG EIENDOM AS is registered as a limited company in Holmestrand, Vestfold with organisation number 989383779. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Selskapets formål er å leie ut næringslokaler, eie aksjer og å drive eiendomsutviklings- virksomhet og investere i fast eiendom direkte, eller gjennom å eie aksjer i tilsvarende virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 1.2m
Equity
NOK 7.7m
Est. value
NOK 8.2m

Financial health · 2025

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

Who owns GULLHAUG EIENDOM AS?

HANS GUNNAR RYGH
GULLHAUG EIENDOM AS
NOK 2.5m rev. · NOK 1.2m profit

GULLHAUG EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does GULLHAUG EIENDOM AS own?

GULLHAUG EIENDOM AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about GULLHAUG EIENDOM AS

Who owns GULLHAUG EIENDOM AS?

HANS GUNNAR RYGH is the largest registered owner, with 40.0%.

What is the revenue of GULLHAUG EIENDOM AS?

GULLHAUG EIENDOM AS had revenue of NOK 2.5m in 2025.

Where is GULLHAUG EIENDOM AS based?

GULLHAUG EIENDOM AS has its business address in Holmestrand.

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.