BIZTRAC BETA
Uoppgitt

GHP EIENDOM AS

Org. no. 929132599 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK −727
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−727 kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

GHP EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 929132599. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift/utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK −727

Financial health · 2024

Liquidity
0.80
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GHP EIENDOM AS?

Geir Paulsen
GHP EIENDOM AS
NOK 0 rev. · NOK −8,000 profit

GHP EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GHP EIENDOM AS own?

GHP EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GHP EIENDOM AS

Who owns GHP EIENDOM AS?

Geir Paulsen is the largest registered owner, with 50.0%.

What is the revenue of GHP EIENDOM AS?

GHP EIENDOM AS had revenue of NOK 0 in 2025.

Where is GHP EIENDOM AS based?

GHP EIENDOM AS has its business address in Trondheim.

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.