BIZTRAC BETA
COMPANY REGISTER PROFILE
917909490 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Other activities of other membership organisations

STØTTEORGANISASJONEN FOR BARN I ØST-KURDISTAN/ IRAN (PERJIN SENTERET)

Org. no. 917909490 Association/club/organisation (FLI) Bergen Incorporated 2016 Active
Ownership graph ↗
Incorporated 2016

STØTTEORGANISASJONEN FOR BARN I ØST-KURDISTAN/ IRAN (PERJIN SENTERET) is registered as a association/club/organisation in Bergen, Vestland with organisation number 917909490. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 2016.

Who owns STØTTEORGANISASJONEN FOR BARN I ØST-KURDISTAN/ IRAN (PERJIN SENTERET)?

No shareholders are registered for STØTTEORGANISASJONEN FOR BARN I ØST-KURDISTAN/ IRAN (PERJIN SENTERET) in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STØTTEORGANISASJONEN FOR BARN I ØST-KURDISTAN/ IRAN (PERJIN SENTERET)

Who is the general manager of STØTTEORGANISASJONEN FOR BARN I ØST-KURDISTAN/ IRAN (PERJIN SENTERET)?

Kawa Kavian is registered as general manager of STØTTEORGANISASJONEN FOR BARN I ØST-KURDISTAN/ IRAN (PERJIN SENTERET).

Where is STØTTEORGANISASJONEN FOR BARN I ØST-KURDISTAN/ IRAN (PERJIN SENTERET) based?

STØTTEORGANISASJONEN FOR BARN I ØST-KURDISTAN/ IRAN (PERJIN SENTERET) has its business address in Ulset.

Property

Business address Myrdalskogen 1, 5118 Ulset
Cadastral unit 4601-188/99/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 24 units

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