BIZTRAC BETA
General medical practice activities

ØYER HELSE KLINIKK AS

Org. no. 922570787 Limited company (AS) Lillehammer Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 885,000
Operating profit NOK 192,000
Equity NOK 60,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-11 Adresseendring registrert 2026-07-11.

ØYER HELSE KLINIKK AS is registered as a limited company in Lillehammer, Innlandet with organisation number 922570787. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Fastlegearbeid.”. The most recent filed accounts, for the 2024 financial year, show NOK 885,000 in revenue and NOK 192,000 in operating profit.

Key figures · 2024

Revenue
NOK 885,000
Operating profit
NOK 192,000
Equity
NOK 60,000
Est. value
NOK 715,000

Financial health · 2024

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ØYER HELSE KLINIKK AS?

QUANG UY BACH
ØYER HELSE KLINIKK AS
NOK 885,000 rev. · NOK 192,000 profit

ØYER HELSE KLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØYER HELSE KLINIKK AS

Who owns ØYER HELSE KLINIKK AS?

QUANG UY BACH is the largest registered owner, with 100.0%.

What is the revenue of ØYER HELSE KLINIKK AS?

ØYER HELSE KLINIKK AS had revenue of NOK 885,000 in 2024.

Who is the general manager of ØYER HELSE KLINIKK AS?

Quang Uy Bach is registered as general manager of ØYER HELSE KLINIKK AS.

Where is ØYER HELSE KLINIKK AS based?

ØYER HELSE KLINIKK 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.