biztrac. BETA
COMPANY REGISTER PROFILE
825767622 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Dental practice care activities

KNARVIK KJEVEORTOPEDI AS

Org. no. 825767622 Limited company (AS) Alver Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 9.3m
Operating profit NOK 1.7m
Equity NOK 1.2m
Incorporated 2020
Employees 8
Share capital NOK 30,000

KNARVIK KJEVEORTOPEDI AS is registered as a limited company in Alver, Vestland with organisation number 825767622. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2020 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tannhelsetjenester innenfor spesialiteten kjeveortopedi, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.3m in revenue and NOK 1.7m in operating profit.

Former names: NYE KNARVIK KJEVEORTOPEDI AS

Key figures · 2025

Revenue
NOK 9.3m
▲ +22 %
Operating profit
NOK 1.7m
▲ +50 %
Equity
NOK 1.2m
▼ −33 %
Est. value
NOK 7.0m

Financial health · 2025

Liquidity
1.66
Good
Current assets ÷ current liabilities
Profitability
57.0%
Very good
Return on total assets
Solidity
42.6%
Very good
Equity as a share of total capital

Who owns KNARVIK KJEVEORTOPEDI AS?

KNARVIK KJEVEORTOPEDI AS
NOK 9.3m rev. · NOK 1.7m profit

KNARVIK KJEVEORTOPEDI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KNARVIK KJEVEORTOPEDI AS

Who owns KNARVIK KJEVEORTOPEDI AS?

EMSE INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of KNARVIK KJEVEORTOPEDI AS?

KNARVIK KJEVEORTOPEDI AS had revenue of NOK 9.3m in 2025.

Where is KNARVIK KJEVEORTOPEDI AS based?

KNARVIK KJEVEORTOPEDI AS has its business address in Isdalstø.

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.