BIZTRAC BETA
Production of electricity from hydropower

MOKRAFT AS

Org. no. 991509003 Limited company (AS) Levanger Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 921,000
Operating profit NOK 155,000
Equity NOK −2.3m
Incorporated 2007
Share capital NOK 700,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,3 mill kr).

MOKRAFT AS is registered as a limited company in Levanger, Trøndelag with organisation number 991509003. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2007. Registered share capital is NOK 700,000, divided into 700 shares. The company's stated purpose is: “Bygge og drive et minikraftverk for utnyttelse av vannkraft ved produksjon og omsetning av energi, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 921,000 in revenue and NOK 155,000 in operating profit.

Key figures · 2025

Revenue
NOK 921,000
Operating profit
NOK 155,000
Equity
NOK −2.3m
Est. value
NOK 922,000

Financial health · 2025

Liquidity
0.19
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-15.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MOKRAFT AS?

LØVLI HOLDING AS
MOKRAFT AS
NOK 921,000 rev. · NOK 155,000 profit

MOKRAFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MOKRAFT AS

Who owns MOKRAFT AS?

LØVLI HOLDING AS is the largest registered owner, with 72.3%.

What is the revenue of MOKRAFT AS?

MOKRAFT AS had revenue of NOK 921,000 in 2025.

Who is the general manager of MOKRAFT AS?

Bjørn Olav Løvli is registered as general manager of MOKRAFT AS.

Where is MOKRAFT AS based?

MOKRAFT AS has its business address in Markabygda.

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.