BIZTRAC BETA
COMPANY REGISTER PROFILE
937595972 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Freight transport by road

VIKTORIAHAVN ANLEGG AS

Org. no. 937595972 Limited company (AS) Narvik Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 38,000

Signals

3 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-04-09.
  • Nylig endring 2026-08-28 Adresseendring registrert 2026-08-28.

VIKTORIAHAVN ANLEGG AS is registered as a limited company in Narvik, Nordland with organisation number 937595972. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2026. Registered share capital is NOK 38,000, divided into 37500 shares. The company's stated purpose is: “Tilby transport av gods på vei, inkludert, men ikke begrenset til, innenlands og internasjonal transport, logistikk- og lagerløsninger, og andre relaterte tjenester.”.

Who owns VIKTORIAHAVN ANLEGG AS?

No shareholders are registered for VIKTORIAHAVN ANLEGG AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about VIKTORIAHAVN ANLEGG AS

Who is the general manager of VIKTORIAHAVN ANLEGG AS?

Jan Åge Horrigmoe is registered as general manager of VIKTORIAHAVN ANLEGG AS.

Where is VIKTORIAHAVN ANLEGG AS based?

VIKTORIAHAVN ANLEGG AS has its business address in Bjerkvik.

Property

Business address Geisvik E6 29, 8530 Bjerkvik
Cadastral unit 1806-22/27/0/0
Building Annen lagerbygning · 1 unit

4 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.