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

FEIRING GRUNNEIERLAG SA

Org. no. 929986261 Co-operation (SA) Eidsvoll Incorporated 1963 Active
Ownership graph ↗
Incorporated 1963

FEIRING GRUNNEIERLAG SA is registered as a co-operation in Eidsvoll, Akershus with organisation number 929986261. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 1963. The company's stated purpose is: “Å forvalte/samordne utnyttelsen av storvilt, småvilt og fiske på lagets område, med blant annet salg av jakt og fiskekort. Forvaltningen av utmarksressuresene vil også innbefatte jakt på rovdyr (ulv, gaupe, bjørn) dersom overordnede myndigheter gir tillatelse til jakt. Jakt og fiskekort kan ikke overdras. Laget skal arbeide for å utvikle utmarksproduktene som næring til landbruket, samt ivareta medlemmenes interesser i saker om naturnvern og friluftsliv. Laget skal også arbeide for å tilfredstille befolkningens rekreasjonsbehov i utmarka.”.

Who owns FEIRING GRUNNEIERLAG SA?

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

Frequently asked questions about FEIRING GRUNNEIERLAG SA

Where is FEIRING GRUNNEIERLAG SA based?

FEIRING GRUNNEIERLAG SA has its business address in Feiring.

Property

Business address c/o Håkon Flesvik Flesvikvegen 17, 2093 Feiring
Cadastral unit 3240-243/110/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.