BIZTRAC BETA
General medical practice activities

PROMEDICUS DRIFT AS

Org. no. 926675176 Limited company (AS) Lillestrøm Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 7.9m
Operating profit NOK 3.4m
Equity NOK 262,000
Incorporated 2021
Share capital NOK 30,000

PROMEDICUS DRIFT AS is registered as a limited company in Lillestrøm, Akershus with organisation number 926675176. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Legepraksis og helsetjenester formidling av slike tjenester samt forretningsdrift av enhvert art, kjøp, salg av aksjer og verdipapirer, fast eiendom innen- og utenlands, samt hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.9m in revenue and NOK 3.4m in operating profit.

Key figures · 2024

Revenue
NOK 7.9m
Operating profit
NOK 3.4m
Equity
NOK 262,000
Est. value
NOK 11.0m

Financial health · 2024

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

Who owns PROMEDICUS DRIFT AS?

PROMEDICUS AS
PROMEDICUS DRIFT AS
NOK 7.9m rev. · NOK 3.4m profit

PROMEDICUS DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROMEDICUS DRIFT AS

Who owns PROMEDICUS DRIFT AS?

PROMEDICUS AS is the largest registered owner, with 100.0%.

What is the revenue of PROMEDICUS DRIFT AS?

PROMEDICUS DRIFT AS had revenue of NOK 7.9m in 2024.

Who is the general manager of PROMEDICUS DRIFT AS?

Julita Karpinska is registered as general manager of PROMEDICUS DRIFT AS.

Where is PROMEDICUS DRIFT AS based?

PROMEDICUS DRIFT AS has its business address in Lillestrøm.

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.