BIZTRAC BETA
COMPANY REGISTER PROFILE
938093636 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Traditional, complementary and alternative medicine activities

NEMUS ÅLGÅRD INVEST AS

Org. no. 938093636 Limited company (AS) Ullensaker Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 408,000

Signals

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

NEMUS ÅLGÅRD INVEST AS is registered as a limited company in Ullensaker, Akershus with organisation number 938093636. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2026. Registered share capital is NOK 408,000, divided into 40817 shares. The company's stated purpose is: “Investere i klinikker som tilbyr tjenester som: kiropraktorbehandling, fysioterapi og / eller dertil nærliggende helsetjenester innenfor de definerte områder Helsegruppen Nemus til enhver tid tilbyr i markedet, herunder salg av helserelaterte produkter og annen virksomhet som naturlig faller inn under dette.”.

Who owns NEMUS ÅLGÅRD INVEST AS?

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

Frequently asked questions about NEMUS ÅLGÅRD INVEST AS

Where is NEMUS ÅLGÅRD INVEST AS based?

NEMUS ÅLGÅRD INVEST AS has its business address in Jessheim.

Property

Business address Kvernlivegen 1E, 2066 Jessheim
Cadastral unit 3209-135/877/0/0
Building Enebolig · 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.