BIZTRAC BETA
Rental and operating of own or leased real estate

PHPM HOLDING AS

Org. no. 819712212 Limited company (AS) Asker Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 168,000
Incorporated 2017
Share capital NOK 200,000

PHPM HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 819712212. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Investeringer i fast eiendom, verdipapirer, kapitalplasseringer og andre formuesobjekter, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 168,000
Est. value
NOK 154,000

Financial health · 2024

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

Who owns PHPM HOLDING AS?

PER HERLOF SELLÆG
PHPM HOLDING AS
NOK 0 rev. · NOK 0 profit

PHPM HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PHPM HOLDING AS own?

PHPM HOLDING AS holds stakes in 14 companies:

See the full ownership structure →

Frequently asked questions about PHPM HOLDING AS

Who owns PHPM HOLDING AS?

PER HERLOF SELLÆG is the largest registered owner, with 60.0%.

What is the revenue of PHPM HOLDING AS?

PHPM HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of PHPM HOLDING AS?

Per Herlof Sellæg is registered as general manager of PHPM HOLDING AS.

Where is PHPM HOLDING AS based?

PHPM HOLDING AS has its business address in Slemmestad.

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.