BIZTRAC BETA
COMPANY REGISTER PROFILE
974793016 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Regulation of and contribution to more efficient operation of businesses

KVÆNANGEN KOMMUNE ETAT FOR NÆRING, UTVIKLING OG TEKNISK

Org. no. 974793016 Organisation section (ORGL) Kvænangen Incorporated 1988 Active
Ownership graph ↗
Incorporated 1988
Employees 61

KVÆNANGEN KOMMUNE ETAT FOR NÆRING, UTVIKLING OG TEKNISK is registered as a organisation section in Kvænangen, Troms with organisation number 974793016. The business is classified under regulation of and contribution to more efficient operation of businesses (NACE 84.130). The company was incorporated in 1988 and has 61 registered employees.

Former names: KVÆNANGEN KOMMUNE TEKNISK SEKTOR

Who owns KVÆNANGEN KOMMUNE ETAT FOR NÆRING, UTVIKLING OG TEKNISK?

No shareholders are registered for KVÆNANGEN KOMMUNE ETAT FOR NÆRING, UTVIKLING OG TEKNISK in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about KVÆNANGEN KOMMUNE ETAT FOR NÆRING, UTVIKLING OG TEKNISK

Who is the general manager of KVÆNANGEN KOMMUNE ETAT FOR NÆRING, UTVIKLING OG TEKNISK?

Stian Lindgård is registered as general manager of KVÆNANGEN KOMMUNE ETAT FOR NÆRING, UTVIKLING OG TEKNISK.

Where is KVÆNANGEN KOMMUNE ETAT FOR NÆRING, UTVIKLING OG TEKNISK based?

KVÆNANGEN KOMMUNE ETAT FOR NÆRING, UTVIKLING OG TEKNISK has its business address in Burfjord.

Property

Business address Rådhuset Gárgu 8, 9161 Burfjord
Cadastral unit 5546-13/119/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

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