BIZTRAC BETA
COMPANY REGISTER PROFILE
933275000 ORG. NO. 7 SECTIONS
Compulsory dissolution UPDATED 02.09.2026
HAUGERISING INVEST AS is registered as “Compulsory dissolution” with the Brønnøysund Register Centre.
Uoppgitt

HAUGERISING INVEST AS

Org. no. 933275000 Limited company (AS) Oslo Incorporated 2024 Compulsory dissolution
Ownership graph ↗
Incorporated 2024
Share capital NOK 30,000

Signals

3 flags
  • Tvangsoppløsning Selskapet er under tvangsoppløsning.
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nylig endring 2026-06-06 Under avvikling registrert 2026-06-06.

HAUGERISING INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 933275000. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i, eie, forvalte og selge andeler i andre selskaper, samt å utøve aktiviteter som er komplementære til disse, inkludert, men ikke begrenset til, finansiell rådgivning og forvaltning.”.

Who owns HAUGERISING INVEST AS?

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

Frequently asked questions about HAUGERISING INVEST AS

Where is HAUGERISING INVEST AS based?

HAUGERISING INVEST AS has its business address in Oslo.

Property

Business address Norbygata 43, 0190 Oslo
Cadastral unit 301-230/237/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 53 units

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