BIZTRAC BETA
Logging

LYSAKER SKOG AS

Org. no. 983857647 Limited company (AS) Drammen Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 296,000
Operating profit NOK 14,000
Equity NOK 210,000
Incorporated 2001
Share capital NOK 100,000

LYSAKER SKOG AS is registered as a limited company in Drammen, Buskerud with organisation number 983857647. The business is classified under logging (NACE 02.200). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å utføre skogbruksvirksomhet, som hogst, planting, og skogskjøtsel, på en måte som er økonomisk lønnsom og bidrar til verdiskaping, samtidig som man ivaretar et bærekraftig skogbruk ved å ta hensyn til miljøverdier som biologisk mangfold, landskap, og kultur, samt deltakelse i nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 296,000 in revenue and NOK 14,000 in operating profit.

Key figures · 2025

Revenue
NOK 296,000
Operating profit
NOK 14,000
Equity
NOK 210,000
Est. value
NOK 154,000

Financial health · 2025

Liquidity
1.99
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.0%
Good
Equity as a share of total capital

Who owns LYSAKER SKOG AS?

HARALD LYSAKER
LYSAKER SKOG AS
NOK 296,000 rev. · NOK 14,000 profit

LYSAKER SKOG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LYSAKER SKOG AS

Who owns LYSAKER SKOG AS?

HARALD LYSAKER is the largest registered owner, with 50.0%.

What is the revenue of LYSAKER SKOG AS?

LYSAKER SKOG AS had revenue of NOK 296,000 in 2025.

Who is the general manager of LYSAKER SKOG AS?

Hans Christian Lysaker is registered as general manager of LYSAKER SKOG AS.

Where is LYSAKER SKOG AS based?

LYSAKER SKOG AS has its business address in Krokstadelva.

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.