BIZTRAC BETA
General medical practice activities

TJP MEDICAL AS

Org. no. 936318142 Limited company (AS) Bærum Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 320,000
Operating profit NOK 124,000
Equity NOK 120,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-08-20.
  • Nylig endring 2026-06-04 Adresseendring registrert 2026-06-04.

TJP MEDICAL AS is registered as a limited company in Bærum, Akershus with organisation number 936318142. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Legepraksis og tilhørende virksomhet innen helse.”. The most recent filed accounts, for the 2025 financial year, show NOK 320,000 in revenue and NOK 124,000 in operating profit.

Key figures · 2025

Revenue
NOK 320,000
Operating profit
NOK 124,000
Equity
NOK 120,000
Est. value
NOK 500,000

Financial health · 2025

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

Who owns TJP MEDICAL AS?

TJP INVEST AS
TJP MEDICAL AS
NOK 320,000 rev. · NOK 124,000 profit

TJP MEDICAL AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TJP MEDICAL AS er morselskap for 2 datterselskaper:

Frequently asked questions about TJP MEDICAL AS

Who owns TJP MEDICAL AS?

TJP INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of TJP MEDICAL AS?

TJP MEDICAL AS had revenue of NOK 320,000 in 2025.

Who is the general manager of TJP MEDICAL AS?

Thilip Praba Prathapan is registered as general manager of TJP MEDICAL AS.

Where is TJP MEDICAL AS based?

TJP MEDICAL AS has its business address in Lysaker.

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.