BIZTRAC BETA
Support services to forestry

P O SKOGSSERVICE AS

Org. no. 923130098 Limited company (AS) Bygland Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 696,000
Operating profit NOK 121,000
Equity NOK 476,000
Incorporated 2019
Share capital NOK 30,000

P O SKOGSSERVICE AS is registered as a limited company in Bygland, Agder with organisation number 923130098. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utleie av maskinførere. Befaring/planlegging av tømmerhogst, befaring slepe til fremføring av tømmer, frakt av gods utafor vei, følge/varselbil ved frakt av maskiner på vei, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 696,000 in revenue and NOK 121,000 in operating profit.

Key figures · 2025

Revenue
NOK 696,000
Operating profit
NOK 121,000
Equity
NOK 476,000
Est. value
NOK 556,000

Financial health · 2025

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

Who owns P O SKOGSSERVICE AS?

PÅL OLSEN
P O SKOGSSERVICE AS
NOK 696,000 rev. · NOK 121,000 profit

P O SKOGSSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about P O SKOGSSERVICE AS

Who owns P O SKOGSSERVICE AS?

PÅL OLSEN is the largest registered owner, with 100.0%.

What is the revenue of P O SKOGSSERVICE AS?

P O SKOGSSERVICE AS had revenue of NOK 696,000 in 2025.

Who is the general manager of P O SKOGSSERVICE AS?

Pål Olsen is registered as general manager of P O SKOGSSERVICE AS.

Where is P O SKOGSSERVICE AS based?

P O SKOGSSERVICE AS has its business address in Bygland.

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.