BIZTRAC BETA
COMPANY REGISTER PROFILE
986161821 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Support activities for animal production

LARDAL BEITELAG SA

Org. no. 986161821 Co-operation (SA) Larvik Incorporated 1970 Active
Ownership graph ↗
Incorporated 1970

LARDAL BEITELAG SA is registered as a co-operation in Larvik, Vestfold with organisation number 986161821. The business is classified under support activities for animal production (NACE 01.620). The company was incorporated in 1970. The company's stated purpose is: “Drive felles organisering av beitebruk i beiteområdet som er definert i § 2 i vedtektene for Lardal Beiteeierlag. Laget skal være ansvarlig for nødvendig sperregjerdehold innen beiteområdet, organisere felles slipping og sanking og iverksette tiltak som kan redusere tap av beitedyr. For øvrig skal laget påse at utøvelsen av beite skjer i henhold til bestemmelsene i bruksordningsreglene og vedtektene. Det skal tas hensyn til andre viktige næringsinteresser i området som skogbruk og jakt. Det skal videre tas hensyn til friluftsinteresser og kulturlandskapet.”.

Former names: LARDAL BEITELAG BA

Who owns LARDAL BEITELAG SA?

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

Frequently asked questions about LARDAL BEITELAG SA

Where is LARDAL BEITELAG SA based?

LARDAL BEITELAG SA has its business address in Steinsholt.

Property

Business address Sundetveien 31, 3277 Steinsholt
Cadastral unit 3909-60/18/0/0
Building Enebolig · 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.