BIZTRAC BETA
Manufacture of medical and dental instruments and supplies

TANNDESIGN SØR AS

Org. no. 993419052 Limited company (AS) Kristiansand Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 8.8m
Operating profit NOK 2.2m
Equity NOK 2.1m
Incorporated 2008
Employees 5
Share capital NOK 100,000

TANNDESIGN SØR AS is registered as a limited company in Kristiansand, Agder with organisation number 993419052. The business is classified under manufacture of medical and dental instruments and supplies (NACE 32.500). The company was incorporated in 2008 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet er tannteknikk, samt investere i aksjer, fond og andre verdipapirer, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.8m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 8.8m
Operating profit
NOK 2.2m
Equity
NOK 2.1m
Est. value
NOK 7.8m

Financial health · 2025

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.7%
Good
Equity as a share of total capital

Who owns TANNDESIGN SØR AS?

PREBEN SKÅRMO LARSEN
TANNDESIGN SØR AS
NOK 8.8m rev. · NOK 2.2m profit

TANNDESIGN SØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TANNDESIGN SØR AS

Who owns TANNDESIGN SØR AS?

PREBEN SKÅRMO LARSEN is the largest registered owner, with 80.0%.

What is the revenue of TANNDESIGN SØR AS?

TANNDESIGN SØR AS had revenue of NOK 8.8m in 2025.

Who is the general manager of TANNDESIGN SØR AS?

Preben Skårmo Larsen is registered as general manager of TANNDESIGN SØR AS.

Where is TANNDESIGN SØR AS based?

TANNDESIGN SØR AS has its business address in Kristiansand S.

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.