biztrac. BETA
COMPANY REGISTER PROFILE
991428275 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Production of electricity from hydropower

GISNAFALLET KRAFTVERK AS

Org. no. 991428275 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 203,000
Equity NOK 3.3m
Incorporated 2007
Share capital NOK 1.5m

Signals

1 flags
  • Nylig endring 2026-08-25 Adresseendring registrert 2026-08-25.

GISNAFALLET KRAFTVERK AS is registered as a limited company in Oslo, Oslo with organisation number 991428275. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2007. Registered share capital is NOK 1.5m, divided into 1500 shares. The company's stated purpose is: “Utvikling, utbygging og drift av småskala vannkraftverk, herunder salg av vannkraft og alt som hermed står i forbindelse. Deltagelse i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 203,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
▼ −21 %
Operating profit
NOK 203,000
▼ −63 %
Equity
NOK 3.3m
▼ −8 %
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
1.6%
Weak
Return on total assets
Solidity
27.1%
Good
Equity as a share of total capital

Who owns GISNAFALLET KRAFTVERK AS?

GISNAFALLET KRAFTVERK AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about GISNAFALLET KRAFTVERK AS

Who owns GISNAFALLET KRAFTVERK AS?

Ingebrigt Haugset is the largest registered owner, with 58.0%.

What is the revenue of GISNAFALLET KRAFTVERK AS?

GISNAFALLET KRAFTVERK AS had revenue of NOK 1.5m in 2025.

Where is GISNAFALLET KRAFTVERK AS based?

GISNAFALLET KRAFTVERK AS has its business address in Oslo.

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

Report a problem

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