BIZTRAC BETA
Traditional, complementary and alternative medicine activities

HELSFYR KIROPRAKTORKLINIKK AS

Org. no. 913834313 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 22,000
Equity NOK 2.3m
Incorporated 2014
Share capital NOK 30,000

HELSFYR KIROPRAKTORKLINIKK AS is registered as a limited company in Oslo, Oslo with organisation number 913834313. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er kiropraktorklinikk.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 22,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 22,000
Equity
NOK 2.3m
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
7.31
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
49.5%
Very good
Equity as a share of total capital

Who owns HELSFYR KIROPRAKTORKLINIKK AS?

LISA CARMEN SPITERI
HELSFYR KIROPRAKTORKLINIKK AS
NOK 3.1m rev. · NOK 22,000 profit

HELSFYR KIROPRAKTORKLINIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HELSFYR KIROPRAKTORKLINIKK AS

Who owns HELSFYR KIROPRAKTORKLINIKK AS?

LISA CARMEN SPITERI is the largest registered owner, with 50.0%.

What is the revenue of HELSFYR KIROPRAKTORKLINIKK AS?

HELSFYR KIROPRAKTORKLINIKK AS had revenue of NOK 3.1m in 2024.

Who is the general manager of HELSFYR KIROPRAKTORKLINIKK AS?

Mikal Albert Apalvik is registered as general manager of HELSFYR KIROPRAKTORKLINIKK AS.

Where is HELSFYR KIROPRAKTORKLINIKK AS based?

HELSFYR KIROPRAKTORKLINIKK AS has its business address in Oslo.

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.