BIZTRAC BETA
Support services to forestry

TROND HOLTER SKOGSENTREPRENØR AS

Org. no. 984664125 Limited company (AS) Åsnes Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 393,000
Equity NOK 3.8m
Incorporated 2002
Share capital NOK 200,000

TROND HOLTER SKOGSENTREPRENØR AS is registered as a limited company in Åsnes, Innlandet with organisation number 984664125. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2002. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Entreprenørvirksomhet innen skogbruket, med tynningsarbeider som spesialfelt.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 393,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 393,000
Equity
NOK 3.8m
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns TROND HOLTER SKOGSENTREPRENØR AS?

TROND HOLTER
TROND HOLTER SKOGSENTREPRENØR AS
NOK 3.9m rev. · NOK 393,000 profit

TROND HOLTER SKOGSENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TROND HOLTER SKOGSENTREPRENØR AS

Who owns TROND HOLTER SKOGSENTREPRENØR AS?

TROND HOLTER is the largest registered owner, with 100.0%.

What is the revenue of TROND HOLTER SKOGSENTREPRENØR AS?

TROND HOLTER SKOGSENTREPRENØR AS had revenue of NOK 3.9m in 2025.

Who is the general manager of TROND HOLTER SKOGSENTREPRENØR AS?

Trond Holter is registered as general manager of TROND HOLTER SKOGSENTREPRENØR AS.

Where is TROND HOLTER SKOGSENTREPRENØR AS based?

TROND HOLTER SKOGSENTREPRENØR AS has its business address in Arneberg.

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.