BIZTRAC BETA
General medical practice activities

DENTALESTETIC AS

Org. no. 916860315 Limited company (AS) Lørenskog Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 264,000
Equity NOK −1.6m
Incorporated 2016
Share capital NOK 1.0m

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,6 mill kr).

DENTALESTETIC AS is registered as a limited company in Lørenskog, Akershus with organisation number 916860315. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2016. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Drive lege, tannlege og hudpleie tjenester og det som hører til. Det skal i tillegg være utleie av næringseiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 264,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 264,000
Equity
NOK −1.6m
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
0.79
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-339.0%
Weak
Equity as a share of total capital

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

Who owns DENTALESTETIC AS?

RAKHEE MALHOTRA
DENTALESTETIC AS
NOK 1.3m rev. · NOK 264,000 profit

DENTALESTETIC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DENTALESTETIC AS

Who owns DENTALESTETIC AS?

RAKHEE MALHOTRA is the largest registered owner, with 100.0%.

What is the revenue of DENTALESTETIC AS?

DENTALESTETIC AS had revenue of NOK 1.3m in 2025.

Who is the general manager of DENTALESTETIC AS?

Ira Malhotra is registered as general manager of DENTALESTETIC AS.

Where is DENTALESTETIC AS based?

DENTALESTETIC AS has its business address in Lørenskog.

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.