BIZTRAC BETA
COMPANY REGISTER PROFILE
937318928 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Production of electricity from hydropower

LOFOTEN VANNKRAFTANLEGG AS

Org. no. 937318928 Limited company (AS) Vågan Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 4.7m

Signals

3 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-12-22.
  • Nylig endring 2026-07-14 Aksjekapital registrert 2026-07-14.

LOFOTEN VANNKRAFTANLEGG AS is registered as a limited company in Vågan, Nordland with organisation number 937318928. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2025. Registered share capital is NOK 4.7m, divided into 3000 shares. The company's stated purpose is: “Produksjon, kjøp og salg av elektrisk energi og annet som naturlig står i forbindelse med dette, herunder deltakelse i andre selskaper.”.

Former names: NFH 251291 AS

Who owns LOFOTEN VANNKRAFTANLEGG AS?

LOFOTEN VANNKRAFTANLEGG AS

LOFOTEN VANNKRAFTANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOFOTEN VANNKRAFTANLEGG AS

Who owns LOFOTEN VANNKRAFTANLEGG AS?

NORWEGIAN VENTURES AS is the largest registered owner, with 100.0%.

Where is LOFOTEN VANNKRAFTANLEGG AS based?

LOFOTEN VANNKRAFTANLEGG AS has its business address in Svolvær.

Property

Business address c/o Lofotkraft AS Vorsetøyveien 31, 8300 Svolvær
Cadastral unit 1865-18/2238/0/0
Building Annen kontorbygning · 1 unit

9 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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