BIZTRAC BETA
COMPANY REGISTER PROFILE
974789787 ORG. NO. 9 SECTIONS
Active UPDATED 02.09.2026
Regulation of health care, education, cultural services and other social services

KVÆNANGEN KOMMUNE ETAT FOR OPPVEKST OG KULTUR

Org. no. 974789787 Organisation section (ORGL) Kvænangen Incorporated 1969 Active
Ownership graph ↗
Incorporated 1969
Employees 75

KVÆNANGEN KOMMUNE ETAT FOR OPPVEKST OG KULTUR is registered as a organisation section in Kvænangen, Troms with organisation number 974789787. The business is classified under regulation of health care, education, cultural services and other social services (NACE 84.120). The company was incorporated in 1969 and has 75 registered employees.

Former names: KVÆNANGEN KOMMUNE SEKTOR FOR OPPVEKST OG OMSORG, KVÆNANGEN KOMMUNE SEKTOR FOR OPPVEKST OG KULTUR

Who owns KVÆNANGEN KOMMUNE ETAT FOR OPPVEKST OG KULTUR?

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

Frequently asked questions about KVÆNANGEN KOMMUNE ETAT FOR OPPVEKST OG KULTUR

Who is the general manager of KVÆNANGEN KOMMUNE ETAT FOR OPPVEKST OG KULTUR?

Stian Lindgård is registered as general manager of KVÆNANGEN KOMMUNE ETAT FOR OPPVEKST OG KULTUR.

Where is KVÆNANGEN KOMMUNE ETAT FOR OPPVEKST OG KULTUR based?

KVÆNANGEN KOMMUNE ETAT FOR OPPVEKST OG KULTUR 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.