BIZTRAC BETA
Silviculture and other forestry activities

BEST PÅ SKOG AS

Org. no. 919717653 Limited company (AS) Åmli Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 14.1m
Operating profit NOK 2.0m
Equity NOK 3.1m
Incorporated 2017
Employees 7
Share capital NOK 400,000

BEST PÅ SKOG AS is registered as a limited company in Åmli, Agder with organisation number 919717653. The business is classified under silviculture and other forestry activities (NACE 02.100). The company was incorporated in 2017 and has 7 registered employees. Registered share capital is NOK 400,000, divided into 100 shares. The company's stated purpose is: “Skogsentreprenør, skogkulturtjenester og hva som naturlig hører inn under dette. Konsulenttjenester innen grunnerverv, skogskjøtsel og tilknytta tjenester. Selskapet kan eie aksjer/andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.1m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 14.1m
Operating profit
NOK 2.0m
Equity
NOK 3.1m
Est. value
NOK 8.4m

Financial health · 2024

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

Who owns BEST PÅ SKOG AS?

BEST PÅ SKOG INVEST AS
BEST PÅ SKOG AS
NOK 14.1m rev. · NOK 2.0m profit

BEST PÅ SKOG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BEST PÅ SKOG AS

Who owns BEST PÅ SKOG AS?

BEST PÅ SKOG INVEST AS is the largest registered owner, with 91.0%.

What is the revenue of BEST PÅ SKOG AS?

BEST PÅ SKOG AS had revenue of NOK 14.1m in 2024.

Who is the general manager of BEST PÅ SKOG AS?

Sigmund Lindtveit is registered as general manager of BEST PÅ SKOG AS.

Where is BEST PÅ SKOG AS based?

BEST PÅ SKOG AS has its business address in Åmli.

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.