BIZTRAC BETA
Uoppgitt

PHOL HOLDING AS

Org. no. 933244059 Limited company (AS) Holmestrand Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 19,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).

PHOL HOLDING AS is registered as a limited company in Holmestrand, Vestfold with organisation number 933244059. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og fast eiendom, og andre produkter/tjenester som naturlig hører til dette. Kjøp og salg av aksjer, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 19,000
Est. value
NOK 22,000

Financial health · 2025

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

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

Who owns PHOL HOLDING AS?

PATRICK FINNIE SANDO
PHOL HOLDING AS
NOK 0 rev. · NOK −16,000 profit

PHOL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PHOL HOLDING AS own?

PHOL HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PHOL HOLDING AS

Who owns PHOL HOLDING AS?

PATRICK FINNIE SANDO is the largest registered owner, with 100.0%.

What is the revenue of PHOL HOLDING AS?

PHOL HOLDING AS had revenue of NOK 0 in 2025.

Where is PHOL HOLDING AS based?

PHOL HOLDING AS has its business address in Sande I Vestfold.

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.