BIZTRAC BETA
Manufacture of medical and dental instruments and supplies

ORTOTEKET AS

Org. no. 919471867 Limited company (AS) Kongsberg Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 6.8m
Operating profit NOK 391,000
Equity NOK 3.6m
Incorporated 2017
Employees 6
Share capital NOK 100,000

ORTOTEKET AS is registered as a limited company in Kongsberg, Buskerud with organisation number 919471867. The business is classified under manufacture of medical and dental instruments and supplies (NACE 32.500). The company was incorporated in 2017 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 50000 shares. The company's stated purpose is: “Å drive produksjon, formidling, utvikling og salg av ortopediske hjelpemidler, samt alt hva som står i forbindelse med dette, enten direkte eller gjennom deltakelse i andre selskaper”. The most recent filed accounts, for the 2025 financial year, show NOK 6.8m in revenue and NOK 391,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.8m
Operating profit
NOK 391,000
Equity
NOK 3.6m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns ORTOTEKET AS?

FAMZE HOLDING AS
ORTOTEKET AS
NOK 6.8m rev. · NOK 391,000 profit

ORTOTEKET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ORTOTEKET AS

Who owns ORTOTEKET AS?

FAMZE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ORTOTEKET AS?

ORTOTEKET AS had revenue of NOK 6.8m in 2025.

Who is the general manager of ORTOTEKET AS?

Linda Marie Zahl Eriksson is registered as general manager of ORTOTEKET AS.

Where is ORTOTEKET AS based?

ORTOTEKET AS has its business address in Kongsberg.

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.