BIZTRAC BETA
Support services to forestry

TOM VIDAR HANSEN SKOGSDRIFT AS

Org. no. 922048770 Limited company (AS) Lier Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 7.0m
Operating profit NOK 1.6m
Equity NOK 1.6m
Incorporated 2019
Share capital NOK 100,000

TOM VIDAR HANSEN SKOGSDRIFT AS is registered as a limited company in Lier, Buskerud with organisation number 922048770. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Maskinentreprenør innen skogsdrift, samt virksomhet som hører naturlig inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.0m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 7.0m
Operating profit
NOK 1.6m
Equity
NOK 1.6m
Est. value
NOK 4.8m

Financial health · 2024

Liquidity
1.46
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.9%
Good
Equity as a share of total capital

Who owns TOM VIDAR HANSEN SKOGSDRIFT AS?

TOM VIDAR HANSEN
TOM VIDAR HANSEN SKOGSDRIFT AS
NOK 7.0m rev. · NOK 1.6m profit

TOM VIDAR HANSEN SKOGSDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOM VIDAR HANSEN SKOGSDRIFT AS

Who owns TOM VIDAR HANSEN SKOGSDRIFT AS?

TOM VIDAR HANSEN is the largest registered owner, with 100.0%.

What is the revenue of TOM VIDAR HANSEN SKOGSDRIFT AS?

TOM VIDAR HANSEN SKOGSDRIFT AS had revenue of NOK 7.0m in 2024.

Who is the general manager of TOM VIDAR HANSEN SKOGSDRIFT AS?

Tom Vidar Hansen is registered as general manager of TOM VIDAR HANSEN SKOGSDRIFT AS.

Where is TOM VIDAR HANSEN SKOGSDRIFT AS based?

TOM VIDAR HANSEN SKOGSDRIFT AS has its business address in Sylling.

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.