BIZTRAC BETA
Dental practice care activities

TANNLEGE HOFF PETERSEN AS

Org. no. 941545149 Limited company (AS) Vefsn Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 15.6m
Operating profit NOK 75,000
Equity NOK 2.0m
Incorporated 1986
Employees 8
Share capital NOK 100,000

TANNLEGE HOFF PETERSEN AS is registered as a limited company in Vefsn, Nordland with organisation number 941545149. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 1986 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drive tannlegevirksomhet, innleie og utleie av tannlegeutstyr og eie og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.6m in revenue and NOK 75,000 in operating profit.

Key figures · 2025

Revenue
NOK 15.6m
Operating profit
NOK 75,000
Equity
NOK 2.0m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns TANNLEGE HOFF PETERSEN AS?

AGNELL HOLDING AS
TANNLEGE HOFF PETERSEN AS
NOK 15.6m rev. · NOK 75,000 profit

TANNLEGE HOFF PETERSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNLEGE HOFF PETERSEN AS

Who owns TANNLEGE HOFF PETERSEN AS?

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

What is the revenue of TANNLEGE HOFF PETERSEN AS?

TANNLEGE HOFF PETERSEN AS had revenue of NOK 15.6m in 2025.

Who is the general manager of TANNLEGE HOFF PETERSEN AS?

Olav Hoff Petersen is registered as general manager of TANNLEGE HOFF PETERSEN AS.

Where is TANNLEGE HOFF PETERSEN AS based?

TANNLEGE HOFF PETERSEN AS has its business address in Mosjøen.

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.