BIZTRAC BETA
Production of electricity from hydropower

TRAUDALEN KRAFTVERK AS

Org. no. 997011902 Limited company (AS) Gloppen Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 482,000
Equity NOK 1.0m
Incorporated 2011
Share capital NOK 1.6m

TRAUDALEN KRAFTVERK AS is registered as a limited company in Gloppen, Vestland with organisation number 997011902. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2011. Registered share capital is NOK 1.6m, divided into 1600000 shares. The company's stated purpose is: “Utvikle, skaffe konsesjon for og bygge, eige og drive kraftverk i Traudalselva i Gloppen kommune, samt anna verksemd som naturleg fell innunder dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 482,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 482,000
Equity
NOK 1.0m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns TRAUDALEN KRAFTVERK AS?

BJØRN ERIK RYGG LUNDE
TRAUDALEN KRAFTVERK AS
NOK 1.7m rev. · NOK 482,000 profit

TRAUDALEN KRAFTVERK AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about TRAUDALEN KRAFTVERK AS

Who owns TRAUDALEN KRAFTVERK AS?

BJØRN ERIK RYGG LUNDE is the largest registered owner, with 8.4%.

What is the revenue of TRAUDALEN KRAFTVERK AS?

TRAUDALEN KRAFTVERK AS had revenue of NOK 1.7m in 2025.

Who is the general manager of TRAUDALEN KRAFTVERK AS?

Eirik Alf Rygg is registered as general manager of TRAUDALEN KRAFTVERK AS.

Where is TRAUDALEN KRAFTVERK AS based?

TRAUDALEN KRAFTVERK AS has its business address in Sandane.

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.