BIZTRAC BETA
Dental practice care activities

TANNLEGE PARTNERE AS

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

Signals

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

TANNLEGE PARTNERE AS is registered as a limited company in Oslo, Oslo with organisation number 929536738. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive tannlege, samt annen virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −544 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −544
Equity
NOK 24,000
Est. value
NOK 55,000

Financial health · 2024

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

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

Who owns TANNLEGE PARTNERE AS?

NILA RINA MARTIN-CABUSAO
TANNLEGE PARTNERE AS
NOK 0 rev. · NOK −544 profit

TANNLEGE PARTNERE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TANNLEGE PARTNERE AS own?

TANNLEGE PARTNERE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about TANNLEGE PARTNERE AS

Who owns TANNLEGE PARTNERE AS?

NILA RINA MARTIN-CABUSAO is the largest registered owner, with 50.0%.

What is the revenue of TANNLEGE PARTNERE AS?

TANNLEGE PARTNERE AS had revenue of NOK 0 in 2024.

Where is TANNLEGE PARTNERE AS based?

TANNLEGE PARTNERE 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.