BIZTRAC BETA
COMPANY REGISTER PROFILE
925316709 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Other recreational activities

BERGENE/GJONE FISKELAG SA

Org. no. 925316709 Co-operation (SA) Larvik Incorporated 2020 Active
Ownership graph ↗
Incorporated 2020

BERGENE/GJONE FISKELAG SA is registered as a co-operation in Larvik, Vestfold with organisation number 925316709. The business is classified under other recreational activities (NACE 93.292). The company was incorporated in 2020. The company's stated purpose is: “Gi rettshaverne til laksefisket medbestemmelse over sportsfiskets omfang og innvirkning på utførelse av nyttefisket i Numedalslågen. Fremme medlemmenes økonomiske interesser gjennom deres deltakelse i virksomheten. Videre skal laget få i stand en felles forvaltning av fiskeressursene, og skal i sitt arbeide tilgodese medlemmenes interesser gjennom en langsiktig ressursforvaltning. Laget skal ha ansvaret for å forvalte og følge gjeldende fiskeregler samt være kontaktleddet mellom lagets medlemmer og Numedalslågen Forvaltningslag.”.

Who owns BERGENE/GJONE FISKELAG SA?

No shareholders are registered for BERGENE/GJONE FISKELAG SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BERGENE/GJONE FISKELAG SA

Where is BERGENE/GJONE FISKELAG SA based?

BERGENE/GJONE FISKELAG SA has its business address in Kvelde.

Property

Business address c/o Geir Jespersen Hedrumveien 1183, 3282 Kvelde
Cadastral unit 3909-2076/20/0/0
Building Våninghus tomannsbolig, vertikaldelt · 1 unit

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