BIZTRAC BETA
Manufacture of medical and dental instruments and supplies

ARTSCAN DENTAL AS

Org. no. 915177042 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK −14,000
Equity NOK 12,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

ARTSCAN DENTAL AS is registered as a limited company in Bærum, Akershus with organisation number 915177042. The business is classified under manufacture of medical and dental instruments and supplies (NACE 32.500). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tannhelsetjeneste og tannteknisk laboratoriedrift.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK −14,000
Equity
NOK 12,000
Est. value
NOK 892,000

Financial health · 2025

Liquidity
1.97
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.6%
Weak
Equity as a share of total capital

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

Who owns ARTSCAN DENTAL AS?

FREDRIK EITZEN
ARTSCAN DENTAL AS
NOK 1.9m rev. · NOK −14,000 profit

ARTSCAN DENTAL AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARTSCAN DENTAL AS

Who owns ARTSCAN DENTAL AS?

FREDRIK EITZEN is the largest registered owner, with 80.0%.

What is the revenue of ARTSCAN DENTAL AS?

ARTSCAN DENTAL AS had revenue of NOK 1.9m in 2025.

Who is the general manager of ARTSCAN DENTAL AS?

Fredrik Eitzen is registered as general manager of ARTSCAN DENTAL AS.

Where is ARTSCAN DENTAL AS based?

ARTSCAN DENTAL AS has its business address in Jar.

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.