BIZTRAC BETA
Rental and operating of own or leased real estate

HP EIENDOM AS

Org. no. 994179799 Limited company (AS) Stavanger Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 1.6m
Equity NOK 2.8m
Incorporated 2009
Share capital NOK 1.3m

HP EIENDOM AS is registered as a limited company in Stavanger, Rogaland with organisation number 994179799. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 1.3m, divided into 1100 shares. The company's stated purpose is: “Holdingselskap, eie aksjer, andeler og lignende i andre selskaper, samt utleie, drift, kjøp og salg av fast eiendom og det som hører naturlig til.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 1.6m
Equity
NOK 2.8m
Est. value
NOK 5.3m

Financial health · 2025

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

Who owns HP EIENDOM AS?

HANS PETTER BRUN
HP EIENDOM AS
NOK 2.6m rev. · NOK 1.6m profit

HP EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HP EIENDOM AS own?

HP EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HP EIENDOM AS

Who owns HP EIENDOM AS?

HANS PETTER BRUN is the largest registered owner, with 100.0%.

What is the revenue of HP EIENDOM AS?

HP EIENDOM AS had revenue of NOK 2.6m in 2025.

Who is the general manager of HP EIENDOM AS?

Hans Petter Brun is registered as general manager of HP EIENDOM AS.

Where is HP EIENDOM AS based?

HP EIENDOM AS has its business address in Stavanger.

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.