BIZTRAC BETA
Production of electricity from hydropower

SØRSIDA KRAFT AS

Org. no. 990317135 Limited company (AS) Inderøy Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 434,000
Operating profit NOK 96,000
Equity NOK −1.5m
Incorporated 2006
Share capital NOK 730,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,5 mill kr).

SØRSIDA KRAFT AS is registered as a limited company in Inderøy, Trøndelag with organisation number 990317135. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2006. Registered share capital is NOK 730,000, divided into 100 shares. The company's stated purpose is: “Produksjon av kraft og det som naturlig hører med. ”. The most recent filed accounts, for the 2024 financial year, show NOK 434,000 in revenue and NOK 96,000 in operating profit.

Key figures · 2024

Revenue
NOK 434,000
Operating profit
NOK 96,000
Equity
NOK −1.5m
Est. value
NOK 569,000

Financial health · 2024

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

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

Who owns SØRSIDA KRAFT AS?

KARL JOHAN FURUNES
SØRSIDA KRAFT AS
NOK 434,000 rev. · NOK 96,000 profit

SØRSIDA KRAFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SØRSIDA KRAFT AS

Who owns SØRSIDA KRAFT AS?

KARL JOHAN FURUNES is the largest registered owner, with 50.0%.

What is the revenue of SØRSIDA KRAFT AS?

SØRSIDA KRAFT AS had revenue of NOK 434,000 in 2024.

Who is the general manager of SØRSIDA KRAFT AS?

Eivind Karlsen is registered as general manager of SØRSIDA KRAFT AS.

Where is SØRSIDA KRAFT AS based?

SØRSIDA KRAFT AS has its business address in Mosvik.

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.