BIZTRAC BETA
Dental practice care activities

TANNLEGE JOHANNESSEN HOLDING AS

Org. no. 917935319 Limited company (AS) Larvik Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 301,000
Operating profit NOK 292,000
Equity NOK 647,000
Incorporated 2016
Share capital NOK 30,000

TANNLEGE JOHANNESSEN HOLDING AS is registered as a limited company in Larvik, Vestfold with organisation number 917935319. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie og evt drive tannlegevirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 301,000 in revenue and NOK 292,000 in operating profit.

Key figures · 2025

Revenue
NOK 301,000
Operating profit
NOK 292,000
Equity
NOK 647,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns TANNLEGE JOHANNESSEN HOLDING AS?

INGRID JOHANNESSEN
TANNLEGE JOHANNESSEN HOLDING AS
NOK 301,000 rev. · NOK 292,000 profit

TANNLEGE JOHANNESSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TANNLEGE JOHANNESSEN HOLDING AS own?

TANNLEGE JOHANNESSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TANNLEGE JOHANNESSEN HOLDING AS

Who owns TANNLEGE JOHANNESSEN HOLDING AS?

INGRID JOHANNESSEN is the largest registered owner, with 100.0%.

What is the revenue of TANNLEGE JOHANNESSEN HOLDING AS?

TANNLEGE JOHANNESSEN HOLDING AS had revenue of NOK 301,000 in 2025.

Where is TANNLEGE JOHANNESSEN HOLDING AS based?

TANNLEGE JOHANNESSEN HOLDING AS has its business address in Stavern.

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.