BIZTRAC BETA
Production of electricity from hydropower

KITTILSVIKEN KRAFTVERK AS

Org. no. 989736744 Limited company (AS) Flå Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 1.1m
Equity NOK 11.3m
Incorporated 2006
Share capital NOK 125,000

KITTILSVIKEN KRAFTVERK AS is registered as a limited company in Flå, Buskerud with organisation number 989736744. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2006. Registered share capital is NOK 125,000, divided into 125 shares. The company's stated purpose is: “Bygging og drift av småkraftverk i Solheimselva i Flå kommune samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 1.1m
Equity
NOK 11.3m
Est. value
NOK 10.9m

Financial health · 2024

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

Who owns KITTILSVIKEN KRAFTVERK AS?

ERLING KITTILSVIKEN
KITTILSVIKEN KRAFTVERK AS
NOK 3.0m rev. · NOK 1.1m profit

KITTILSVIKEN KRAFTVERK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KITTILSVIKEN KRAFTVERK AS

Who owns KITTILSVIKEN KRAFTVERK AS?

ERLING KITTILSVIKEN is the largest registered owner, with 80.0%.

What is the revenue of KITTILSVIKEN KRAFTVERK AS?

KITTILSVIKEN KRAFTVERK AS had revenue of NOK 3.0m in 2024.

Who is the general manager of KITTILSVIKEN KRAFTVERK AS?

Amund Kittilsviken is registered as general manager of KITTILSVIKEN KRAFTVERK AS.

Where is KITTILSVIKEN KRAFTVERK AS based?

KITTILSVIKEN KRAFTVERK AS has its business address in Flå.

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.