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

NORGES JEGER- OG FISKERFORBUND SOGN OG FJORDANE

Org. no. 975682900 Association/club/organisation (FLI) Kinn Active
Ownership graph ↗

NORGES JEGER- OG FISKERFORBUND SOGN OG FJORDANE is registered as a association/club/organisation in Kinn, Vestland with organisation number 975682900. The business is classified under other activities of other membership organisations (NACE 94.992).

Former names: SOGN & FJORDANE JEGER OG FISKE- FORBUND, NORGES JEGER- OG FISKERFORBUND - SOGN OG FJORDANE

Who owns NORGES JEGER- OG FISKERFORBUND SOGN OG FJORDANE?

No shareholders are registered for NORGES JEGER- OG FISKERFORBUND SOGN OG FJORDANE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does NORGES JEGER- OG FISKERFORBUND SOGN OG FJORDANE own?

NORGES JEGER- OG FISKERFORBUND SOGN OG FJORDANE holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NORGES JEGER- OG FISKERFORBUND SOGN OG FJORDANE

Who is the general manager of NORGES JEGER- OG FISKERFORBUND SOGN OG FJORDANE?

Reidun Solberg Seim is registered as general manager of NORGES JEGER- OG FISKERFORBUND SOGN OG FJORDANE.

Where is NORGES JEGER- OG FISKERFORBUND SOGN OG FJORDANE based?

NORGES JEGER- OG FISKERFORBUND SOGN OG FJORDANE has its business address in Kinn.

Property

Business address c/o Reidun Solberg Seim St. Sunniva-vegen 4, 6912 Kinn
Cadastral unit 4602-39/4/0/0
Building Våningshus · 1 unit

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.