BIZTRAC BETA
COMPANY REGISTER PROFILE
937719043 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

HAUGSETH & EVENRUD AS

Org. no. 937719043 Limited company (AS) Stange Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 500,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-04-17.

HAUGSETH & EVENRUD AS is registered as a limited company in Stange, Innlandet with organisation number 937719043. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2026. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Aksje og eiendomsbesittelse og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”.

Who owns HAUGSETH & EVENRUD AS?

No shareholders are registered for HAUGSETH & EVENRUD AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about HAUGSETH & EVENRUD AS

Who is the general manager of HAUGSETH & EVENRUD AS?

Thomas Sørli Haugseth is registered as general manager of HAUGSETH & EVENRUD AS.

Where is HAUGSETH & EVENRUD AS based?

HAUGSETH & EVENRUD AS has its business address in Tangen.

Property

Business address Kolomoen 590, 2337 Tangen
Cadastral unit 3413-323/25/0/0
Building Annen forretningsbygning · 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.