BIZTRAC BETA
Manufacture of medical and dental instruments and supplies

STAVANGER TANNTEKNIKK AS

Org. no. 921269676 Limited company (AS) Stavanger Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 331,000
Equity NOK 331,000
Incorporated 2018
Share capital NOK 30,000

STAVANGER TANNTEKNIKK AS is registered as a limited company in Stavanger, Rogaland with organisation number 921269676. The business is classified under manufacture of medical and dental instruments and supplies (NACE 32.500). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tannteknisk laboratorium som lager tannerstatninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 331,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 331,000
Equity
NOK 331,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns STAVANGER TANNTEKNIKK AS?

SIW RENEE HEGGSTAD TORSETH
STAVANGER TANNTEKNIKK AS
NOK 1.7m rev. · NOK 331,000 profit

STAVANGER TANNTEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STAVANGER TANNTEKNIKK AS

Who owns STAVANGER TANNTEKNIKK AS?

SIW RENEE HEGGSTAD TORSETH is the largest registered owner, with 100.0%.

What is the revenue of STAVANGER TANNTEKNIKK AS?

STAVANGER TANNTEKNIKK AS had revenue of NOK 1.7m in 2025.

Who is the general manager of STAVANGER TANNTEKNIKK AS?

Siw Renee Heggstad Torseth is registered as general manager of STAVANGER TANNTEKNIKK AS.

Where is STAVANGER TANNTEKNIKK AS based?

STAVANGER TANNTEKNIKK AS has its business address in Stavanger.

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.