BIZTRAC BETA
COMPANY REGISTER PROFILE
875495712 ORG. NO. 2014 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Other activities of other membership organisations

NORSK FORENING FOR BARN OG UNGES PSYKISKE HELSE (N-BUP)

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

NORSK FORENING FOR BARN OG UNGES PSYKISKE HELSE (N-BUP) is registered as a association/club/organisation in Bergen, Vestland with organisation number 875495712. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 1958.

Former names: NORSK FORENING FOR BARNE- OG UNGDOMSPSYKIATRISKE INSTITUSJONER

Who owns NORSK FORENING FOR BARN OG UNGES PSYKISKE HELSE (N-BUP)?

No shareholders are registered for NORSK FORENING FOR BARN OG UNGES PSYKISKE HELSE (N-BUP) in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about NORSK FORENING FOR BARN OG UNGES PSYKISKE HELSE (N-BUP)

Who is the general manager of NORSK FORENING FOR BARN OG UNGES PSYKISKE HELSE (N-BUP)?

Linda Helen Knudsen Flygel is registered as general manager of NORSK FORENING FOR BARN OG UNGES PSYKISKE HELSE (N-BUP).

Where is NORSK FORENING FOR BARN OG UNGES PSYKISKE HELSE (N-BUP) based?

NORSK FORENING FOR BARN OG UNGES PSYKISKE HELSE (N-BUP) has its business address in Fyllingsdalen.

Property

Business address c/o Linda Helen Knudsen Flygel Helgeplasset 26, 5148 Fyllingsdalen
Cadastral unit 4601-26/243/0/0
Building Rekkehus · 1 unit

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.