BIZTRAC BETA
COMPANY REGISTER PROFILE
970551751 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Other real estate activities on a fee or contract basis

ØYSTRE RØN GRUNNEIGARLAG SA

Org. no. 970551751 Co-operation (SA) Vestre Slidre Incorporated 1960 Active
Ownership graph ↗
Incorporated 1960

ØYSTRE RØN GRUNNEIGARLAG SA is registered as a co-operation in Vestre Slidre, Innlandet with organisation number 970551751. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 1960. The company's stated purpose is: “Ein samansluting av eigarar av jakt og fangstrettar i Røn. Grunneigarlaget skal prøve å samle grunneigarane i bygda for i saman å fremja jakt og fangst som næring. Samanslutninga er eit samvirkeførektak med føretaksnamn Øystre Røn Grunneigarlag SA. Kvart medlem skal teikne andelar i forhold til arealet som inngår i grunneigarlaget. Medlemmene heftar ikkje overfor kreditorane for føretaket sine forpliktingar. Føretaket har vekslande medlemstal og kapital.”.

Former names: ØSTRE RØN GRUNNEIGARLAG

Who owns ØYSTRE RØN GRUNNEIGARLAG SA?

No shareholders are registered for ØYSTRE RØN GRUNNEIGARLAG SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ØYSTRE RØN GRUNNEIGARLAG SA

Where is ØYSTRE RØN GRUNNEIGARLAG SA based?

ØYSTRE RØN GRUNNEIGARLAG SA has its business address in Røn.

Property

Business address v/Helge Ødegaard Oldrumvegen 39, 2960 Røn
Cadastral unit 3452-82/1/0/0
Building Våningshus · 1 unit

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