biztrac. BETA
COMPANY REGISTER PROFILE
919763477 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Sawmilling and planing of wood

SETSKOG TRELAST AS

Org. no. 919763477 Limited company (AS) Aurskog-Høland Incorporated 2017 Active
Revenue 2025 NOK 3.7m
Operating profit NOK 168,000
Equity NOK 2.1m
Incorporated 2017
Share capital NOK 100,000

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 2025 financial year, show NOK 3.7m in revenue and NOK 168,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
▼ −13 %
Operating profit
NOK 168,000
▲ +1243 %
Equity
NOK 2.1m
▲ +5 %
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
2.92
Very good
Current assets ÷ current liabilities
Profitability
4.4%
Weak
Return on total assets
Solidity
49.9%
Very good
Equity as a share of total capital

Who owns SETSKOG TRELAST AS?

SETSKOG TRELAST AS
NOK 3.7m rev. · NOK 168,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?

Jan Erik Engh is the largest registered owner, with 50.0%.

What is the revenue of SETSKOG TRELAST AS?

SETSKOG TRELAST AS had revenue of NOK 3.7m in 2025.

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 03.10.2026.

Report a problem

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