BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

ESTMED KLINIKKEN AS

Org. no. 929676416 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −4,000
Equity NOK 17,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

ESTMED KLINIKKEN AS is registered as a limited company in Oslo, Oslo with organisation number 929676416. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Legesenter”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 17,000
Est. value
NOK 27,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.3%
Weak
Equity as a share of total capital

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

Who owns ESTMED KLINIKKEN AS?

ULLEVÅL PLASTIKKIRUGI AS
ESTMED KLINIKKEN AS
NOK 0 rev. · NOK −4,000 profit

ESTMED KLINIKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ESTMED KLINIKKEN AS

Who owns ESTMED KLINIKKEN AS?

ULLEVÅL PLASTIKKIRUGI AS is the largest registered owner, with 100.0%.

What is the revenue of ESTMED KLINIKKEN AS?

ESTMED KLINIKKEN AS had revenue of NOK 0 in 2024.

Who is the general manager of ESTMED KLINIKKEN AS?

Alex Pujari is registered as general manager of ESTMED KLINIKKEN AS.

Where is ESTMED KLINIKKEN AS based?

ESTMED KLINIKKEN 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.