biztrac. BETA
COMPANY REGISTER PROFILE
976941179 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Support services to forestry

STRUKSNÆS SKOG AS

Org. no. 976941179 Limited company (AS) Nordre Land Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 17.6m
Operating profit NOK 3.1m
Equity NOK 14.6m
Incorporated 1996
Employees 8
Share capital NOK 200,000

STRUKSNÆS SKOG AS is registered as a limited company in Nordre Land, Innlandet with organisation number 976941179. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 1996 and has 8 registered employees. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet og transport.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.6m in revenue and NOK 3.1m in operating profit.

Key figures · 2025

Revenue
NOK 17.6m
▲ +26 %
Operating profit
NOK 3.1m
▲ +218 %
Equity
NOK 14.6m
▲ +18 %
Est. value
NOK 15.5m

Financial health · 2025

Liquidity
3.11
Very good
Current assets ÷ current liabilities
Profitability
14.8%
Good
Return on total assets
Solidity
65.7%
Very good
Equity as a share of total capital

Who owns STRUKSNÆS SKOG AS?

STRUKSNÆS SKOG AS
NOK 17.6m rev. · NOK 3.1m profit

STRUKSNÆS SKOG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STRUKSNÆS SKOG AS er morselskap for 1 datterselskap:

Frequently asked questions about STRUKSNÆS SKOG AS

Who owns STRUKSNÆS SKOG AS?

VIKEN SKOG SA is the largest registered owner, with 100.0%.

What is the revenue of STRUKSNÆS SKOG AS?

STRUKSNÆS SKOG AS had revenue of NOK 17.6m in 2025.

Who is the general manager of STRUKSNÆS SKOG AS?

Dag Nydal is registered as general manager of STRUKSNÆS SKOG AS.

Where is STRUKSNÆS SKOG AS based?

STRUKSNÆS SKOG AS has its business address in Dokka.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.