BIZTRAC BETA
Logging

SEM SETERSKOG AS

Org. no. 997077024 Limited company (AS) Skien Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 6,000
Operating profit NOK −15,000
Equity NOK 766,000
Incorporated 2011
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−15k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SEM SETERSKOG AS is registered as a limited company in Skien, Telemark with organisation number 997077024. The business is classified under logging (NACE 02.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Skogsdrift og alt som naturlig hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 6,000 in revenue and NOK −15,000 in operating profit.

Key figures · 2024

Revenue
NOK 6,000
Operating profit
NOK −15,000
Equity
NOK 766,000
Est. value
NOK 449,000

Financial health · 2024

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

Who owns SEM SETERSKOG AS?

FJELLVÅKEN HOLDING AS
SEM SETERSKOG AS
NOK 6,000 rev. · NOK −15,000 profit

SEM SETERSKOG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEM SETERSKOG AS

Who owns SEM SETERSKOG AS?

FJELLVÅKEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SEM SETERSKOG AS?

SEM SETERSKOG AS had revenue of NOK 6,000 in 2024.

Who is the general manager of SEM SETERSKOG AS?

Andreas Finsrud is registered as general manager of SEM SETERSKOG AS.

Where is SEM SETERSKOG AS based?

SEM SETERSKOG AS has its business address in Skien.

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.