BIZTRAC BETA
COMPANY REGISTER PROFILE
992966335 ORG. NO. 6 SECTIONS
Active UPDATED 02.09.2026
Activities of excursion and event organisers

LOFOTEN CRUISE NETTVERK SA

Org. no. 992966335 Co-operation (SA) Vestvågøy Incorporated 2008 Active
Ownership graph ↗
Incorporated 2008

LOFOTEN CRUISE NETTVERK SA is registered as a co-operation in Vestvågøy, Nordland with organisation number 992966335. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2008. The company's stated purpose is: “Samle bedrifter, organisasjoner og offentlige institusjoner med stor interesse for utviklingen av Lofoten som cruisedestinasjon. En markedsføringsorganisasjon og samarbeidsforum for utvikling av Lofoten som en attraktiv cruisedestinasjon. Samarbeidsaktivitetene vil væer både eksterne og interne, herunder ekstern markedsføring, innsalg, produktutvikling, intern kvalitetsikring, kompetanseutbygging og lønnsomhetsstyrking.”.

Who owns LOFOTEN CRUISE NETTVERK SA?

No shareholders are registered for LOFOTEN CRUISE NETTVERK SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LOFOTEN CRUISE NETTVERK SA

Who is the general manager of LOFOTEN CRUISE NETTVERK SA?

Gillian Hockly is registered as general manager of LOFOTEN CRUISE NETTVERK SA.

Where is LOFOTEN CRUISE NETTVERK SA based?

LOFOTEN CRUISE NETTVERK SA has its business address in Leknes.

Property

Business address Storgata 8, 8370 Leknes
Cadastral unit 1860-18/268/0/0

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