BIZTRAC BETA
Production of electricity from hydropower

LAUVSTAD KRAFTVERK AS

Org. no. 922414440 Limited company (AS) Drangedal Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 2.7m
Equity NOK 18.2m
Incorporated 2019
Share capital NOK 60,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LAUVSTAD KRAFTVERK AS is registered as a limited company in Drangedal, Telemark with organisation number 922414440. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Utbygging og drift av kraftverk i Drangedal kommune.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 2.7m in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 2.7m
Equity
NOK 18.2m
Est. value
NOK 17.6m

Financial health · 2024

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

Who owns LAUVSTAD KRAFTVERK AS?

ROCKBERG AS
LAUVSTAD KRAFTVERK AS
NOK 4.3m rev. · NOK 2.7m profit

LAUVSTAD KRAFTVERK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAUVSTAD KRAFTVERK AS

Who owns LAUVSTAD KRAFTVERK AS?

ROCKBERG AS is the largest registered owner, with 100.0%.

What is the revenue of LAUVSTAD KRAFTVERK AS?

LAUVSTAD KRAFTVERK AS had revenue of NOK 4.3m in 2024.

Who is the general manager of LAUVSTAD KRAFTVERK AS?

Ulf Mikael Wennilsjö is registered as general manager of LAUVSTAD KRAFTVERK AS.

Where is LAUVSTAD KRAFTVERK AS based?

LAUVSTAD KRAFTVERK AS has its business address in Tørdal.

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.