BIZTRAC BETA
COMPANY REGISTER PROFILE
937779127 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Water collection, treatment and supply

ANGRE HYTTESERVICE AS

Org. no. 937779127 Limited company (AS) Seljord Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 30,000

Signals

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

ANGRE HYTTESERVICE AS is registered as a limited company in Seljord, Telemark with organisation number 937779127. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å eie og drifte vann- og avløpsanlegg med tilhørende ledninger og tekniske installasjoner og annet som hører naturlig sammen med dette, samt levere brøytetjenester, ved og andre etterspurte varer og tjenester.”.

Who owns ANGRE HYTTESERVICE AS?

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

Frequently asked questions about ANGRE HYTTESERVICE AS

Who is the general manager of ANGRE HYTTESERVICE AS?

Johan Angre is registered as general manager of ANGRE HYTTESERVICE AS.

Where is ANGRE HYTTESERVICE AS based?

ANGRE HYTTESERVICE AS has its business address in Flatdal.

Property

Business address Sundbøhaugvegen 3, 3841 Flatdal
Cadastral unit 4022-63/125/0/0
Building Annen industribygning · 1 unit

6 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.