BIZTRAC BETA
Support services to forestry

KRISTIANSEN SKOG AS

Org. no. 930902101 Limited company (AS) Åmot Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 6.0m
Operating profit NOK 516,000
Equity NOK 1.3m
Incorporated 2023
Share capital NOK 200,000

KRISTIANSEN SKOG AS is registered as a limited company in Åmot, Innlandet with organisation number 930902101. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2023. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Skogsentrepriser, anleggsvirksomhet, agentur og handel, transport, kjøp og salg av fast eiendom, produksjon og alt som står i forbindelse med dette herunder å gjøre seg interessert i virksomheter med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.0m in revenue and NOK 516,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.0m
Operating profit
NOK 516,000
Equity
NOK 1.3m
Est. value
NOK 2.5m

Financial health · 2024

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

Who owns KRISTIANSEN SKOG AS?

EMBRET KRISTIANSEN
KRISTIANSEN SKOG AS
NOK 6.0m rev. · NOK 516,000 profit

KRISTIANSEN SKOG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRISTIANSEN SKOG AS

Who owns KRISTIANSEN SKOG AS?

EMBRET KRISTIANSEN is the largest registered owner, with 100.0%.

What is the revenue of KRISTIANSEN SKOG AS?

KRISTIANSEN SKOG AS had revenue of NOK 6.0m in 2024.

Who is the general manager of KRISTIANSEN SKOG AS?

Embret Kristiansen is registered as general manager of KRISTIANSEN SKOG AS.

Where is KRISTIANSEN SKOG AS based?

KRISTIANSEN SKOG AS has its business address in Rena.

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.