biztrac. BETA
COMPANY REGISTER PROFILE
916896654 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Manufacture of medical and dental instruments and supplies

ORTHOLAB AS

Org. no. 916896654 Limited company (AS) Tønsberg Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 663,000
Operating profit NOK 50,000
Equity NOK 149,000
Incorporated 2016
Share capital NOK 30,000

ORTHOLAB AS is registered as a limited company in Tønsberg, Vestfold with organisation number 916896654. The business is classified under manufacture of medical and dental instruments and supplies (NACE 32.500). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Tanntekniker laboratorium, tanntekniker, å lage kjeveortopedisk utstyr, plater, funksjonelle og kjeveortopedisk oppbevarings apparater, stavaker.”. The most recent filed accounts, for the 2025 financial year, show NOK 663,000 in revenue and NOK 50,000 in operating profit.

Key figures · 2025

Revenue
NOK 663,000
▲ +27 %
Operating profit
NOK 50,000
▲ +417 %
Equity
NOK 149,000
▲ +40 %
Est. value
NOK 252,000

Financial health · 2025

Liquidity
3.14
Very good
Current assets ÷ current liabilities
Profitability
25.8%
Very good
Return on total assets
Solidity
68.8%
Very good
Equity as a share of total capital

Who owns ORTHOLAB AS?

ORTHOLAB AS
NOK 663,000 rev. · NOK 50,000 profit

ORTHOLAB AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ORTHOLAB AS

Who owns ORTHOLAB AS?

Vaida Stikle is the largest registered owner, with 60.0%.

What is the revenue of ORTHOLAB AS?

ORTHOLAB AS had revenue of NOK 663,000 in 2025.

Who is the general manager of ORTHOLAB AS?

Vaida Stikle is registered as general manager of ORTHOLAB AS.

Where is ORTHOLAB AS based?

ORTHOLAB AS has its business address in Tønsberg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.