BIZTRAC BETA
Dental practice care activities

KJEVEORTOPED PETTERSEN AS

Org. no. 974215098 Limited company (AS) Harstad Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 12.8m
Operating profit NOK 832,000
Equity NOK 5.6m
Incorporated 1995
Employees 6
Share capital NOK 100,000

KJEVEORTOPED PETTERSEN AS is registered as a limited company in Harstad, Troms with organisation number 974215098. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 1995 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tannlegevirksomhet og hva hermed står i forbindelse, herunder å delta i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.8m in revenue and NOK 832,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.8m
Operating profit
NOK 832,000
Equity
NOK 5.6m
Est. value
NOK 8.3m

Financial health · 2025

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

Who owns KJEVEORTOPED PETTERSEN AS?

HUGO NYGÅRD PETTERSEN
KJEVEORTOPED PETTERSEN AS
NOK 12.8m rev. · NOK 832,000 profit

KJEVEORTOPED PETTERSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJEVEORTOPED PETTERSEN AS

Who owns KJEVEORTOPED PETTERSEN AS?

HUGO NYGÅRD PETTERSEN is the largest registered owner, with 100.0%.

What is the revenue of KJEVEORTOPED PETTERSEN AS?

KJEVEORTOPED PETTERSEN AS had revenue of NOK 12.8m in 2025.

Who is the general manager of KJEVEORTOPED PETTERSEN AS?

Hugo Nygård Pettersen is registered as general manager of KJEVEORTOPED PETTERSEN AS.

Where is KJEVEORTOPED PETTERSEN AS based?

KJEVEORTOPED PETTERSEN AS has its business address in Harstad.

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.