BIZTRAC BETA
Uoppgitt

PHR HOLDING AS

Org. no. 889047682 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −65,000
Equity NOK 103.2m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−65k kr).

PHR HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 889047682. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer, selskapsandeler og andeler i næringsvirksomhet og eiendommer; samt handel med aksjer og verdipapirer, herunder lånefinansierte investeringer med verdipapirer og valuta, hvor selskapet kan pantsette sine aktiver i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −65,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −65,000
Equity
NOK 103.2m
Est. value
NOK 113.6m

Financial health · 2024

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

Who owns PHR HOLDING AS?

PER HARALD RASMUSSEN
PHR HOLDING AS
NOK 0 rev. · NOK −65,000 profit

PHR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PHR HOLDING AS own?

PHR HOLDING AS holds stakes in 17 companies:

See the full ownership structure →

Frequently asked questions about PHR HOLDING AS

Who owns PHR HOLDING AS?

PER HARALD RASMUSSEN is the largest registered owner, with 100.0%.

What is the revenue of PHR HOLDING AS?

PHR HOLDING AS had revenue of NOK 0 in 2024.

Where is PHR HOLDING AS based?

PHR HOLDING AS has its business address in Oslo.

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.