BIZTRAC BETA
COMPANY REGISTER PROFILE
913321391 ORG. NO. 2015 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Central agencies for goods and transportation procurement

EIDSKOG TAXISENTRAL SA

Org. no. 913321391 Co-operation (SA) Eidskog Incorporated 2014 Active
Ownership graph ↗
Incorporated 2014

Signals

1 flags
  • Nylig endring 2026-04-10 Adresseendring registrert 2026-04-10.

EIDSKOG TAXISENTRAL SA is registered as a co-operation in Eidskog, Innlandet with organisation number 913321391. The business is classified under central agencies for goods and transportation procurement (NACE 52.211). The company was incorporated in 2014. The company's stated purpose is: “Drive taxisentral på et ikke økonomisk grunnlag med fordeling av felleskostnader for de løyvehavere som er tilsluttet sentralen. Foretaket har til formål å fremme medlemmenes økonomiske interesser gjennom deltakelse i virksomheten ved fellesdrift og betjening av taxitjenester fra kjent fysisk holdepunkt. Et eventuelt årlig overskudd tillegges egenkapitalen.”.

Who owns EIDSKOG TAXISENTRAL SA?

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

Frequently asked questions about EIDSKOG TAXISENTRAL SA

Who is the general manager of EIDSKOG TAXISENTRAL SA?

Uno Stenbråten is registered as general manager of EIDSKOG TAXISENTRAL SA.

Where is EIDSKOG TAXISENTRAL SA based?

EIDSKOG TAXISENTRAL SA has its business address in Skotterud.

Property

Business address Matrandvegen 50, 2230 Skotterud
Cadastral unit 3416-53/643/0/0
Building Barnehage · 3 units

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.