BIZTRAC BETA
Rental and operating of own or leased real estate

PAHO AS

Org. no. 890702732 Limited company (AS) Skien Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −236,000
Equity NOK 10.5m
Incorporated 2006
Share capital NOK 568,000

Signals

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

PAHO AS is registered as a limited company in Skien, Telemark with organisation number 890702732. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 568,000, divided into 1419 shares. The company's stated purpose is: “Kjøp og salg av aksjer eller andeler i andre selskaper eller annen virksomhet, herunder kjøp og salg, utleie og forvaltning av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −236,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −236,000
Equity
NOK 10.5m
Est. value
NOK 9.0m

Financial health · 2025

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

Who owns PAHO AS?

PER ARNE HOLMBERG
PAHO AS
NOK 0 rev. · NOK −236,000 profit

PAHO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PAHO AS own?

PAHO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about PAHO AS

Who owns PAHO AS?

PER ARNE HOLMBERG is the largest registered owner, with 100.0%.

What is the revenue of PAHO AS?

PAHO AS had revenue of NOK 0 in 2024.

Who is the general manager of PAHO AS?

Kari Holmberg is registered as general manager of PAHO AS.

Where is PAHO AS based?

PAHO AS has its business address in Skien.

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.