biztrac. BETA
COMPANY REGISTER PROFILE
991429042 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Production of electricity from hydropower

SMØRKLEPP KRAFTVERK AS

Org. no. 991429042 Limited company (AS) Vinje Incorporated 2007 Active
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 2.8m
Incorporated 2007
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

SMØRKLEPP KRAFTVERK AS is registered as a limited company in Vinje, Telemark with organisation number 991429042. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon av elektrisk kraft og det som naturleg høyrer saman med slik verksemd.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
▼ −5 %
Equity
NOK 2.8m
▲ +6 %
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
43.33
Very good
Current assets ÷ current liabilities
Profitability
6.9%
Satisfactory
Return on total assets
Solidity
95.9%
Very good
Equity as a share of total capital

Who owns SMØRKLEPP KRAFTVERK AS?

SMØRKLEPP KRAFTVERK AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about SMØRKLEPP KRAFTVERK AS

Who owns SMØRKLEPP KRAFTVERK AS?

Irene Negarden is the largest registered owner, with 30.0%.

What is the revenue of SMØRKLEPP KRAFTVERK AS?

SMØRKLEPP KRAFTVERK AS had revenue of NOK 0 in 2025.

Who is the general manager of SMØRKLEPP KRAFTVERK AS?

Kjetil Negarden is registered as general manager of SMØRKLEPP KRAFTVERK AS.

Where is SMØRKLEPP KRAFTVERK AS based?

SMØRKLEPP KRAFTVERK AS has its business address in Vinje.

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.