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

VÅLÅSVEGEN/JOGRANSVEGEN SA

Org. no. 917790442 Co-operation (SA) Åsnes Incorporated 2016 Active
Ownership graph ↗
Incorporated 2016

VÅLÅSVEGEN/JOGRANSVEGEN SA is registered as a co-operation in Åsnes, Innlandet with organisation number 917790442. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2016. The company's stated purpose is: “Veglaget skal bygge og vedlikeholde en skogsbilveg fra Kvernmoen til Karlstad, veg fra FV-206 til vegens endepunkt i 4-vegskryss og sideveg til endepunkt hvor denne møter skogsveg over Gjesåsberget. Veglaget har som formål å redusere andelseiernes kostnader til uttransport av tømmer og å gjøre skog i vegens nytteområde tilgjengelig for aktiv skogforvaltning.”.

Former names: VÅLÅSVEGEN SA

Who owns VÅLÅSVEGEN/JOGRANSVEGEN SA?

No shareholders are registered for VÅLÅSVEGEN/JOGRANSVEGEN SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about VÅLÅSVEGEN/JOGRANSVEGEN SA

Who is the general manager of VÅLÅSVEGEN/JOGRANSVEGEN SA?

Ole Søren Skybak is registered as general manager of VÅLÅSVEGEN/JOGRANSVEGEN SA.

Where is VÅLÅSVEGEN/JOGRANSVEGEN SA based?

VÅLÅSVEGEN/JOGRANSVEGEN SA has its business address in Gjesåsen.

Property

Business address c/o Ole Søren Skybak Kvernmoen 2, 2280 Gjesåsen
Cadastral unit 3418-50/1/0/0
Building Våningshus · 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.