BIZTRAC BETA
General medical practice activities

LEGE KINGA KEREKES AS

Org. no. 911889897 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 2.0m
Equity NOK 6.5m
Incorporated 2013
Share capital NOK 30,000

LEGE KINGA KEREKES AS is registered as a limited company in Oslo, Oslo with organisation number 911889897. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Fastlege og helsetjenester og alt hva hermed er i forbindelse, utleie av arbeidskraft, samt investeringer i eiendom og deltakelse i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.3m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK 2.0m
Equity
NOK 6.5m
Est. value
NOK 11.8m

Financial health · 2025

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

Who owns LEGE KINGA KEREKES AS?

KINGA VALERIA DAVOTINE DR KEREKES
LEGE KINGA KEREKES AS
NOK 4.3m rev. · NOK 2.0m profit

LEGE KINGA KEREKES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEGE KINGA KEREKES AS

Who owns LEGE KINGA KEREKES AS?

KINGA VALERIA DAVOTINE DR KEREKES is the largest registered owner, with 100.0%.

What is the revenue of LEGE KINGA KEREKES AS?

LEGE KINGA KEREKES AS had revenue of NOK 4.3m in 2025.

Who is the general manager of LEGE KINGA KEREKES AS?

Kinga Valeria Davotine Dr Kerekes is registered as general manager of LEGE KINGA KEREKES AS.

Where is LEGE KINGA KEREKES AS based?

LEGE KINGA KEREKES 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.