BIZTRAC BETA
Production of electricity from hydropower

MOMRAK KRAFTLAG AS

Org. no. 992803118 Limited company (AS) Fyresdal Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 1.3m
Equity NOK 5.9m
Incorporated 2008
Share capital NOK 2.6m

MOMRAK KRAFTLAG AS is registered as a limited company in Fyresdal, Telemark with organisation number 992803118. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2008. Registered share capital is NOK 2.6m, divided into 26000 shares. The company's stated purpose is: “Bygge og drive kraftstasjoner, kjøpe og selge energi og andre naturressurser som faller naturlig. I tillegg kan en delta i andre selskap med lignende formål, eller som det ellers er naturlig å samarbeide med.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 1.3m
Equity
NOK 5.9m
Est. value
NOK 7.6m

Financial health · 2025

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

Who owns MOMRAK KRAFTLAG AS?

HANS JOHAN HAAKENSTAD
MOMRAK KRAFTLAG AS
NOK 2.1m rev. · NOK 1.3m profit

MOMRAK KRAFTLAG AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about MOMRAK KRAFTLAG AS

Who owns MOMRAK KRAFTLAG AS?

HANS JOHAN HAAKENSTAD is the largest registered owner, with 66.7%.

What is the revenue of MOMRAK KRAFTLAG AS?

MOMRAK KRAFTLAG AS had revenue of NOK 2.1m in 2025.

Who is the general manager of MOMRAK KRAFTLAG AS?

Hans Johan Haakenstad is registered as general manager of MOMRAK KRAFTLAG AS.

Where is MOMRAK KRAFTLAG AS based?

MOMRAK KRAFTLAG AS has its business address in Fyresdal.

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.