BIZTRAC BETA
Logging

HOLTH SKOGSDRIFT AS

Org. no. 850376182 Limited company (AS) Aurskog-Høland Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 52.6m
Operating profit NOK 3.2m
Equity NOK 8.6m
Incorporated 1988
Employees 32
Share capital NOK 400,000

HOLTH SKOGSDRIFT AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 850376182. The business is classified under logging (NACE 02.200). The company was incorporated in 1988 and has 32 registered employees. Registered share capital is NOK 400,000, divided into 40 shares. The company's stated purpose is: “Skogsdrift, kjøp og salg av skogsmaskiner og alt som står i forbindelse herved.”. The most recent filed accounts, for the 2024 financial year, show NOK 52.6m in revenue and NOK 3.2m in operating profit.

Key figures · 2024

Revenue
NOK 52.6m
Operating profit
NOK 3.2m
Equity
NOK 8.6m
Est. value
NOK 15.5m

Financial health · 2024

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

Who owns HOLTH SKOGSDRIFT AS?

JAN BIRGER HOLTH
HOLTH SKOGSDRIFT AS
NOK 52.6m rev. · NOK 3.2m profit

HOLTH SKOGSDRIFT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HOLTH SKOGSDRIFT AS own?

HOLTH SKOGSDRIFT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HOLTH SKOGSDRIFT AS

Who owns HOLTH SKOGSDRIFT AS?

JAN BIRGER HOLTH is the largest registered owner, with 92.5%.

What is the revenue of HOLTH SKOGSDRIFT AS?

HOLTH SKOGSDRIFT AS had revenue of NOK 52.6m in 2024.

Who is the general manager of HOLTH SKOGSDRIFT AS?

Jan Birger Holth is registered as general manager of HOLTH SKOGSDRIFT AS.

Where is HOLTH SKOGSDRIFT AS based?

HOLTH SKOGSDRIFT AS has its business address in Rømskog.

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.