BIZTRAC BETA
Rental and operating of own or leased real estate

PTHR HOLDING AS

Org. no. 989072692 Limited company (AS) Sola Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 417,000
Operating profit NOK 204,000
Equity NOK 10.0m
Incorporated 2005
Share capital NOK 100,000

PTHR HOLDING AS is registered as a limited company in Sola, Rogaland with organisation number 989072692. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer, samt hva herved står i forbindelse, herunder investering i selskap, eiendom og andre finansaktiva.”. The most recent filed accounts, for the 2024 financial year, show NOK 417,000 in revenue and NOK 204,000 in operating profit.

Key figures · 2024

Revenue
NOK 417,000
Operating profit
NOK 204,000
Equity
NOK 10.0m
Est. value
NOK 7.2m

Financial health · 2024

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

Who owns PTHR HOLDING AS?

PER OVE ØGLÆND
PTHR HOLDING AS
NOK 417,000 rev. · NOK 204,000 profit

PTHR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PTHR HOLDING AS own?

PTHR HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about PTHR HOLDING AS

Who owns PTHR HOLDING AS?

PER OVE ØGLÆND is the largest registered owner, with 100.0%.

What is the revenue of PTHR HOLDING AS?

PTHR HOLDING AS had revenue of NOK 417,000 in 2024.

Who is the general manager of PTHR HOLDING AS?

Per Ove Øglænd is registered as general manager of PTHR HOLDING AS.

Where is PTHR HOLDING AS based?

PTHR HOLDING AS has its business address in Røyneberg.

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.