BIZTRAC BETA
Manufacture of medical and dental instruments and supplies

ORTOPEDITEKNIKK AS

Org. no. 930614785 Limited company (AS) Oslo Incorporated 1979 Active
Ownership graph ↗
Revenue 2024 NOK 371.3m
Operating profit NOK 27.0m
Equity NOK 92.1m
Incorporated 1979
Employees 189
Share capital NOK 500,000

ORTOPEDITEKNIKK AS is registered as a limited company in Oslo, Oslo with organisation number 930614785. The business is classified under manufacture of medical and dental instruments and supplies (NACE 32.500). The company was incorporated in 1979 and has 189 registered employees. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Utvikle, produsere og omsette ortopediske hjelpe- midler, samt hva som hermed står i forbindelse, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 371.3m in revenue and NOK 27.0m in operating profit.

Key figures · 2024

Revenue
NOK 371.3m
Operating profit
NOK 27.0m
Equity
NOK 92.1m
Est. value
NOK 158.5m

Financial health · 2025

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

Who owns ORTOPEDITEKNIKK AS?

FRODE AAMODT
ORTOPEDITEKNIKK AS
NOK 371.3m rev. · NOK 27.0m profit

ORTOPEDITEKNIKK AS has 11 registered shareholders:

All shareholders and roles →

Frequently asked questions about ORTOPEDITEKNIKK AS

Who owns ORTOPEDITEKNIKK AS?

FRODE AAMODT is the largest registered owner, with 23.8%.

What is the revenue of ORTOPEDITEKNIKK AS?

ORTOPEDITEKNIKK AS had revenue of NOK 371.3m in 2024.

Who is the general manager of ORTOPEDITEKNIKK AS?

Åsa Roth is registered as general manager of ORTOPEDITEKNIKK AS.

Where is ORTOPEDITEKNIKK AS based?

ORTOPEDITEKNIKK AS has its business address in Oslo.

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.