BIZTRAC BETA
Sawmilling and planing of wood

SETSKOG TRELAST AS

Org. no. 919763477 Limited company (AS) Aurskog-Høland Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK −15,000
Equity NOK 2.0m
Incorporated 2017
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−15k kr).

SETSKOG TRELAST AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 919763477. The business is classified under sawmilling and planing of wood (NACE 16.110). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Videreforedling av tømmer, vedproduksjon og salg av trematerialer og bygningsartikler og alt som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK −15,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK −15,000
Equity
NOK 2.0m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns SETSKOG TRELAST AS?

ERIK ANDRE DOUAT
SETSKOG TRELAST AS
NOK 4.2m rev. · NOK −15,000 profit

SETSKOG TRELAST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SETSKOG TRELAST AS

Who owns SETSKOG TRELAST AS?

ERIK ANDRE DOUAT is the largest registered owner, with 50.0%.

What is the revenue of SETSKOG TRELAST AS?

SETSKOG TRELAST AS had revenue of NOK 4.2m in 2024.

Who is the general manager of SETSKOG TRELAST AS?

Jan Erik Engh is registered as general manager of SETSKOG TRELAST AS.

Where is SETSKOG TRELAST AS based?

SETSKOG TRELAST AS has its business address in Setskog.

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.