BIZTRAC BETA
Physiotherapy activities

ØYERKLINIKKEN AS

Org. no. 912249808 Limited company (AS) Lillehammer Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 26,000
Equity NOK 518,000
Incorporated 2013
Share capital NOK 30,000

ØYERKLINIKKEN AS is registered as a limited company in Lillehammer, Innlandet with organisation number 912249808. The business is classified under physiotherapy activities (NACE 86.950). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive osteopati og fysioterapibehandling, medisinsk trening, samt drive kurs og veiledningskompetanse innen helse, trening, idrett og arbeid. Gjelder også dertil tilhørende salg av varer og tjenester. Gjelder også deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 26,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 26,000
Equity
NOK 518,000
Est. value
NOK 492,000

Financial health · 2025

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

Who owns ØYERKLINIKKEN AS?

PEHKI 750 HOLDING AS
ØYERKLINIKKEN AS
NOK 1.4m rev. · NOK 26,000 profit

ØYERKLINIKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØYERKLINIKKEN AS

Who owns ØYERKLINIKKEN AS?

PEHKI 750 HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ØYERKLINIKKEN AS?

ØYERKLINIKKEN AS had revenue of NOK 1.4m in 2025.

Who is the general manager of ØYERKLINIKKEN AS?

Kari Svelstad Kittelsen is registered as general manager of ØYERKLINIKKEN AS.

Where is ØYERKLINIKKEN AS based?

ØYERKLINIKKEN AS has its business address in Lillehammer.

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.