BIZTRAC BETA
Rental and operating of own or leased real estate

PH EIENDOM AS

Org. no. 933573974 Limited company (AS) Grimstad Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 80,000
Operating profit NOK 40,000
Equity NOK 53,000
Incorporated 2024
Share capital NOK 30,000

PH EIENDOM AS is registered as a limited company in Grimstad, Agder with organisation number 933573974. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eiendomsutvikling, oppføring, restaurering, reparasjon og vedlikehold av bygg, samt annen virksomhet som naturlig hører sammen med dette. Investeringer i aksjer, andeler og andre verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 80,000 in revenue and NOK 40,000 in operating profit.

Key figures · 2025

Revenue
NOK 80,000
Operating profit
NOK 40,000
Equity
NOK 53,000
Est. value
NOK 112,000

Financial health · 2024

Liquidity
0.47
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.0%
Weak
Equity as a share of total capital

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

Who owns PH EIENDOM AS?

STIAN HOMME
PH EIENDOM AS
NOK 80,000 rev. · NOK 40,000 profit

PH EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PH EIENDOM AS

Who owns PH EIENDOM AS?

STIAN HOMME is the largest registered owner, with 50.0%.

What is the revenue of PH EIENDOM AS?

PH EIENDOM AS had revenue of NOK 80,000 in 2025.

Who is the general manager of PH EIENDOM AS?

Stian Homme is registered as general manager of PH EIENDOM AS.

Where is PH EIENDOM AS based?

PH EIENDOM AS has its business address in Grimstad.

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.