BIZTRAC BETA
COMPANY REGISTER PROFILE
988198641 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Production of electricity from hydropower

FAGERDALEN KRAFTVERK AS

Org. no. 988198641 Limited company (AS) Vaksdal Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 983,000
Equity NOK 3.4m
Incorporated 2005
Share capital NOK 100,000

FAGERDALEN KRAFTVERK AS is registered as a limited company in Vaksdal, Vestland with organisation number 988198641. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon og salg av elektrisk kraft, samt anna verksemd som naturleg høyrer saman med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 983,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
▲ +12 %
Operating profit
NOK 983,000
▲ +21 %
Equity
NOK 3.4m
▲ +1 %
Est. value
NOK 5.0m

Financial health · 2025

Liquidity
0.86
Weak
Current assets ÷ current liabilities
Profitability
18.0%
Very good
Return on total assets
Solidity
61.5%
Very good
Equity as a share of total capital

Who owns FAGERDALEN KRAFTVERK AS?

FAGERDALEN KRAFTVERK AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about FAGERDALEN KRAFTVERK AS

Who owns FAGERDALEN KRAFTVERK AS?

EINAR HOVDA NILSEN is the largest registered owner, with 25.0%.

What is the revenue of FAGERDALEN KRAFTVERK AS?

FAGERDALEN KRAFTVERK AS had revenue of NOK 1.6m in 2025.

Who is the general manager of FAGERDALEN KRAFTVERK AS?

Einar Hovda Nilsen is registered as general manager of FAGERDALEN KRAFTVERK AS.

Where is FAGERDALEN KRAFTVERK AS based?

FAGERDALEN KRAFTVERK AS has its business address in Eidslandet.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.