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

ØVRE DIVIDAL NASJONALPARK OG DIVIDALEN LANDSKAPSVERNOMRÅDE

Org. no. 918469141 Other body corporate (ANNA) Tromsø Incorporated 2014 Active
Ownership graph ↗
Incorporated 2014

ØVRE DIVIDAL NASJONALPARK OG DIVIDALEN LANDSKAPSVERNOMRÅDE is registered as a other body corporate in Tromsø, Troms with organisation number 918469141. The business is classified under regulation of health care, education, cultural services and other social services (NACE 84.120). The company was incorporated in 2014.

Who owns ØVRE DIVIDAL NASJONALPARK OG DIVIDALEN LANDSKAPSVERNOMRÅDE?

No shareholders are registered for ØVRE DIVIDAL NASJONALPARK OG DIVIDALEN LANDSKAPSVERNOMRÅDE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ØVRE DIVIDAL NASJONALPARK OG DIVIDALEN LANDSKAPSVERNOMRÅDE

Who is the general manager of ØVRE DIVIDAL NASJONALPARK OG DIVIDALEN LANDSKAPSVERNOMRÅDE?

Kai-Ove Kristiansen is registered as general manager of ØVRE DIVIDAL NASJONALPARK OG DIVIDALEN LANDSKAPSVERNOMRÅDE.

Where is ØVRE DIVIDAL NASJONALPARK OG DIVIDALEN LANDSKAPSVERNOMRÅDE based?

ØVRE DIVIDAL NASJONALPARK OG DIVIDALEN LANDSKAPSVERNOMRÅDE has its business address in Tromsø.

Property

Business address c/o Fylkesmannen i Troms Strandvegen 13, 9007 Tromsø
Cadastral unit 5501-200/1692/0/0
Building Klinikk, legekontor/-senter/-vakt/dyresykehus · 2 units

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