BIZTRAC BETA
COMPANY REGISTER PROFILE
936925294 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Other personal service activities n.e.c.

GLIMT LIFE AS

Org. no. 936925294 Limited company (AS) Oslo Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 106,000

Signals

3 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-01-08.
  • Nylig endring 2026-03-23 Aksjekapital registrert 2026-03-23.

GLIMT LIFE AS is registered as a limited company in Oslo, Oslo with organisation number 936925294. The business is classified under other personal service activities n.e.c. (NACE 96.990). The company was incorporated in 2026. Registered share capital is NOK 106,000, divided into 1063829 shares. The company's stated purpose is: “Selskapet skal inspirere folk til å utforske nye ting og dele det de kan. Selskapet skal utvikle, produsere og distribuere konsepter og produkter så folk enkelt kan utforske nye ting eller bli inspirert til å dele det de kan med andre. Selskapet skal spre læringsglede og gjøre forskjell. Selskapet kan også drive virksomhet som naturlig henger sammen med dette.”.

Who owns GLIMT LIFE AS?

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

Frequently asked questions about GLIMT LIFE AS

Where is GLIMT LIFE AS based?

GLIMT LIFE AS has its business address in Oslo.

Property

Business address Holmengrenda 41, 0771 Oslo
Cadastral unit 301-27/2180/0/0
Building Rekkehus · 3 units

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