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

SKOVLY VEILAG SA

Org. no. 930460095 Co-operation (SA) Fredrikstad Incorporated 2022 Active
Ownership graph ↗
Incorporated 2022

SKOVLY VEILAG SA is registered as a co-operation in Fredrikstad, Østfold with organisation number 930460095. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2022. The company's stated purpose is: “Ivareta drift og vedlikehold av veiene som ligger til veilaget. Veilaget sørger også for de plikter og ansvar et veilag har etter veglova og da særlig kap VII. Driftsansvaret omfatter planlegging, bygging, utbedring, vedlikehold og daglig drift av veiene. Veilaget skal sikre det økonomiske grunnlag for veilagets ansvar og plikter. Veilaget har som formål å sørge for at veiene er i en standard som er nødvendig for helårsdrift, utfra det rådende trafikkgrunnlag og ferdselsbehov.”.

Who owns SKOVLY VEILAG SA?

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

Frequently asked questions about SKOVLY VEILAG SA

Who is the general manager of SKOVLY VEILAG SA?

Torstein Norheim is registered as general manager of SKOVLY VEILAG SA.

Where is SKOVLY VEILAG SA based?

SKOVLY VEILAG SA has its business address in Engelsviken.

Property

Business address Skovly 15, 1628 Engelsviken
Cadastral unit 3107-112/492/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.