BIZTRAC BETA
COMPANY REGISTER PROFILE
915454496 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Hunting, trapping and related service activities

TOBØL OG STANGNES GRUNNEIERLAG SA

Org. no. 915454496 Co-operation (SA) Eidskog Incorporated 1995 Active
Ownership graph ↗
Incorporated 1995

TOBØL OG STANGNES GRUNNEIERLAG SA is registered as a co-operation in Eidskog, Innlandet with organisation number 915454496. The business is classified under hunting, trapping and related service activities (NACE 01.700). The company was incorporated in 1995. The company's stated purpose is: “Forhandle med elgjaktlaget om leiepris for hele området. Administrere salg av jaktkort for rådyr og småvilt (herunder også andejakt). Drive aktiv viltpleie. Organisere jaktoppsyn. Ta vare på gamle kulturminner, som merking av nedlagte boplasser, stier osv. Arrangere noe for sosialt samvær, skogvandring o.l.”.

Who owns TOBØL OG STANGNES GRUNNEIERLAG SA?

No shareholders are registered for TOBØL OG STANGNES GRUNNEIERLAG SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about TOBØL OG STANGNES GRUNNEIERLAG SA

Who is the general manager of TOBØL OG STANGNES GRUNNEIERLAG SA?

Torgrim Grani Finsrud is registered as general manager of TOBØL OG STANGNES GRUNNEIERLAG SA.

Where is TOBØL OG STANGNES GRUNNEIERLAG SA based?

TOBØL OG STANGNES GRUNNEIERLAG SA has its business address in Tobøl.

Property

Business address c/o Torgrim Finserud Vestmarkavegen 629, 2232 Tobøl
Cadastral unit 3416-15/23/0/0
Building Våningshus · 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.