BIZTRAC BETA
LIFTHRASIR AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Rental and leasing of other machinery, equipment and tangible goods n.e.c.

LIFTHRASIR AS

Org. no. 835715892 Limited company (AS) Sandefjord Incorporated 2025 In liquidation
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nylig endring 2026-06-16 Avregistrert registrert 2026-06-16.

LIFTHRASIR AS is registered as a limited company in Sandefjord, Vestfold with organisation number 835715892. The business is classified under rental and leasing of other machinery, equipment and tangible goods n.e.c. (NACE 77.390). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å utvikle, eie og drive virksomhet innen forebyggende helse- og velvære­tjenester, herunder hyperbar oksygen­behandling (HBOT), fotobiomodulering og infrarød varme-/saunaterapi, sekvensiell kompresjons­behandling, hurtig biomarkør- og laboratorietesting, samt salg av kosttilskudd, medisinsk-teknisk utstyr, helse- og velvære­produkter. Videre kan selskapet drive forskning, utvikling, rådgivning, undervisning, franchising, import, eksport, markedsføring og annen virksomhet som naturlig henger sammen med ovennevnte. Selskapet kan delta i andre foretak, investeringer eller samarbeids­prosjekter som fremmerformålet.”.

Who owns LIFTHRASIR AS?

ALEXANDER BURMO
LIFTHRASIR AS

LIFTHRASIR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIFTHRASIR AS

Who owns LIFTHRASIR AS?

ALEXANDER BURMO is the largest registered owner, with 100.0%.

Where is LIFTHRASIR AS based?

LIFTHRASIR AS has its business address in Sandefjord.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.