BIZTRAC BETA
COMPANY REGISTER PROFILE
970422528 ORG. NO. 12 SECTIONS
Active UPDATED 02.09.2026
Education at universities

UNIVERSITETET I TROMSØ - NORGES ARKTISKE UNIVERSITET

Org. no. 970422528 Organisation section (ORGL) Tromsø Active
Ownership graph ↗
Employees 4923

UNIVERSITETET I TROMSØ - NORGES ARKTISKE UNIVERSITET is registered as a organisation section in Tromsø, Troms with organisation number 970422528. The business is classified under education at universities (NACE 85.401). The company has 4923 registered employees.

Former names: UNIVERSITETET I TROMSØ SENTRALADM, UNIVERSITETET I TROMSØ

Who owns UNIVERSITETET I TROMSØ - NORGES ARKTISKE UNIVERSITET?

No shareholders are registered for UNIVERSITETET I TROMSØ - NORGES ARKTISKE UNIVERSITET in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does UNIVERSITETET I TROMSØ - NORGES ARKTISKE UNIVERSITET own?

UNIVERSITETET I TROMSØ - NORGES ARKTISKE UNIVERSITET holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about UNIVERSITETET I TROMSØ - NORGES ARKTISKE UNIVERSITET

Who is the general manager of UNIVERSITETET I TROMSØ - NORGES ARKTISKE UNIVERSITET?

Jørgen Fossland is registered as general manager of UNIVERSITETET I TROMSØ - NORGES ARKTISKE UNIVERSITET.

Where is UNIVERSITETET I TROMSØ - NORGES ARKTISKE UNIVERSITET based?

UNIVERSITETET I TROMSØ - NORGES ARKTISKE UNIVERSITET has its business address in Tromsø.

Property

Business address Hansine Hansens veg 18, 9019 Tromsø
Cadastral unit 5501-119/3570/0/0

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