BIZTRAC BETA
Manufacture of medical and dental instruments and supplies

MYSEN TANNTEKNIKK AS

Org. no. 963434839 Limited company (AS) Indre Østfold Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 85,000
Equity NOK 200,000
Incorporated 1992
Share capital NOK 100,000

MYSEN TANNTEKNIKK AS is registered as a limited company in Indre Østfold, Østfold with organisation number 963434839. The business is classified under manufacture of medical and dental instruments and supplies (NACE 32.500). The company was incorporated in 1992. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utøvelse av tjenester innen tannteknikk; kjøp, salg, import, eksport, deltagelse i andre selskap, samt hva hermed står i forbindelse. ”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 85,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 85,000
Equity
NOK 200,000
Est. value
NOK 436,000

Financial health · 2024

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

Who owns MYSEN TANNTEKNIKK AS?

RAGNAR GJERLØW ERIKSEN
MYSEN TANNTEKNIKK AS
NOK 1.8m rev. · NOK 85,000 profit

MYSEN TANNTEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MYSEN TANNTEKNIKK AS

Who owns MYSEN TANNTEKNIKK AS?

RAGNAR GJERLØW ERIKSEN is the largest registered owner, with 100.0%.

What is the revenue of MYSEN TANNTEKNIKK AS?

MYSEN TANNTEKNIKK AS had revenue of NOK 1.8m in 2025.

Who is the general manager of MYSEN TANNTEKNIKK AS?

Ragnar Gjerløw Eriksen is registered as general manager of MYSEN TANNTEKNIKK AS.

Where is MYSEN TANNTEKNIKK AS based?

MYSEN TANNTEKNIKK AS has its business address in Mysen.

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.