BIZTRAC BETA
Rental and operating of own or leased real estate

GH EIENDOM AS

Org. no. 912048683 Limited company (AS) Oslo Incorporated 1943 Active
Ownership graph ↗
Revenue 2025 NOK 18.4m
Operating profit NOK 13.7m
Equity NOK 46.0m
Incorporated 1943
Share capital NOK 5.0m

Signals

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

GH EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 912048683. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1943. Registered share capital is NOK 5.0m. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 18.4m in revenue and NOK 13.7m in operating profit.

Key figures · 2025

Revenue
NOK 18.4m
Operating profit
NOK 13.7m
Equity
NOK 46.0m
Est. value
NOK 58.8m

Financial health · 2025

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

Who owns GH EIENDOM AS?

NOPARK 1 AS
GH EIENDOM AS
NOK 18.4m rev. · NOK 13.7m profit

GH EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GH EIENDOM AS own?

GH EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Group structure

GH EIENDOM AS er morselskap for 10 datterselskaper:

Frequently asked questions about GH EIENDOM AS

Who owns GH EIENDOM AS?

NOPARK 1 AS is the largest registered owner, with 100.0%.

What is the revenue of GH EIENDOM AS?

GH EIENDOM AS had revenue of NOK 18.4m in 2025.

Where is GH EIENDOM AS based?

GH EIENDOM AS has its business address in Oslo.

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.