BIZTRAC BETA
COMPANY REGISTER PROFILE
987705647 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Activities of trade unions

FELLESFORBUNDET NORDRE NORDLAND OG SØR-TROMS

Org. no. 987705647 Association/club/organisation (FLI) Saltdal Incorporated 2004 Active
Ownership graph ↗
Incorporated 2004
Employees 9

FELLESFORBUNDET NORDRE NORDLAND OG SØR-TROMS is registered as a association/club/organisation in Saltdal, Nordland with organisation number 987705647. The business is classified under activities of trade unions (NACE 94.200). The company was incorporated in 2004 and has 9 registered employees.

Former names: FELLESFORBUNDET NORDRE NORDLAND

Who owns FELLESFORBUNDET NORDRE NORDLAND OG SØR-TROMS?

No shareholders are registered for FELLESFORBUNDET NORDRE NORDLAND OG SØR-TROMS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does FELLESFORBUNDET NORDRE NORDLAND OG SØR-TROMS own?

FELLESFORBUNDET NORDRE NORDLAND OG SØR-TROMS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FELLESFORBUNDET NORDRE NORDLAND OG SØR-TROMS

Who is the general manager of FELLESFORBUNDET NORDRE NORDLAND OG SØR-TROMS?

Jon Kenneth Brekke is registered as general manager of FELLESFORBUNDET NORDRE NORDLAND OG SØR-TROMS.

Where is FELLESFORBUNDET NORDRE NORDLAND OG SØR-TROMS based?

FELLESFORBUNDET NORDRE NORDLAND OG SØR-TROMS has its business address in Rognan.

Property

Business address Strandgata 1, 8250 Rognan
Cadastral unit 1840-43/634/0/0
Building Kontor- og administrasjonsbygning, rådhus · 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.