BIZTRAC BETA
Other health services

OPTIMAL HELSEKLINIKK AS

Org. no. 999079954 Limited company (AS) Ørsta Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −62,000
Equity NOK 1.8m
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−62k kr).

OPTIMAL HELSEKLINIKK AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 999079954. The business is classified under other health services (NACE 86.993). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Helse og trening og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2024

Operating profit
NOK −62,000
Equity
NOK 1.8m
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns OPTIMAL HELSEKLINIKK AS?

MARIANNE HAUGE KRIKEN
OPTIMAL HELSEKLINIKK AS
· NOK −62,000 profit

OPTIMAL HELSEKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OPTIMAL HELSEKLINIKK AS own?

OPTIMAL HELSEKLINIKK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OPTIMAL HELSEKLINIKK AS

Who owns OPTIMAL HELSEKLINIKK AS?

MARIANNE HAUGE KRIKEN is the largest registered owner, with 100.0%.

Who is the general manager of OPTIMAL HELSEKLINIKK AS?

Marianne Hauge Kriken is registered as general manager of OPTIMAL HELSEKLINIKK AS.

Where is OPTIMAL HELSEKLINIKK AS based?

OPTIMAL HELSEKLINIKK AS has its business address in Ørsta.

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.