BIZTRAC BETA
Dental practice care activities

TANNLEGE TONE HEIMDAL NODENES AS

Org. no. 921075049 Limited company (AS) Kristiansand Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK −208,000
Equity NOK 3.5m
Incorporated 2018
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−208k kr).

TANNLEGE TONE HEIMDAL NODENES AS is registered as a limited company in Kristiansand, Agder with organisation number 921075049. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2018. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Drive med tannlegevirksomhet, herunder delta i andre selskaper som aksjeeier eller ansvarlig deltager.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK −208,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK −208,000
Equity
NOK 3.5m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns TANNLEGE TONE HEIMDAL NODENES AS?

TONE HEIMDAL NODENES
TANNLEGE TONE HEIMDAL NODENES AS
NOK 1.0m rev. · NOK −208,000 profit

TANNLEGE TONE HEIMDAL NODENES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNLEGE TONE HEIMDAL NODENES AS

Who owns TANNLEGE TONE HEIMDAL NODENES AS?

TONE HEIMDAL NODENES is the largest registered owner, with 100.0%.

What is the revenue of TANNLEGE TONE HEIMDAL NODENES AS?

TANNLEGE TONE HEIMDAL NODENES AS had revenue of NOK 1.0m in 2025.

Where is TANNLEGE TONE HEIMDAL NODENES AS based?

TANNLEGE TONE HEIMDAL NODENES AS has its business address in Søgne.

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.