BIZTRAC BETA
Site preparation

PH EIENDOM & HOLDING AS

Org. no. 989227394 Limited company (AS) Klepp Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −83,000
Equity NOK 34.2m
Incorporated 2005
Share capital NOK 1.0m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−83k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PH EIENDOM & HOLDING AS is registered as a limited company in Klepp, Rogaland with organisation number 989227394. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 1 shares. The company's stated purpose is: “Investering i andre selskaper samt kjøp, salg og utleie av fast eiendom, utleie av andre driftsmidler samt alt som hører naturlig til dette.”.

Key figures · 2025

Operating profit
NOK −83,000
Equity
NOK 34.2m
Est. value
NOK 27.0m

Financial health · 2025

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

Who owns PH EIENDOM & HOLDING AS?

PÅL HATTELAND
PH EIENDOM & HOLDING AS
· NOK −83,000 profit

PH EIENDOM & HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PH EIENDOM & HOLDING AS own?

PH EIENDOM & HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about PH EIENDOM & HOLDING AS

Who owns PH EIENDOM & HOLDING AS?

PÅL HATTELAND is the largest registered owner, with 100.0%.

Who is the general manager of PH EIENDOM & HOLDING AS?

Pål Hatteland is registered as general manager of PH EIENDOM & HOLDING AS.

Where is PH EIENDOM & HOLDING AS based?

PH EIENDOM & HOLDING AS has its business address in Kleppe.

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.