BIZTRAC BETA
Dental practice care activities

JÆRTANNLEGENE AS

Org. no. 911926695 Limited company (AS) Time Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 5.3m
Operating profit NOK 959,000
Equity NOK 1.3m
Incorporated 2013
Employees 5
Share capital NOK 100,000

JÆRTANNLEGENE AS is registered as a limited company in Time, Rogaland with organisation number 911926695. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2013 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av tannlegekontor, stille utstyr og personell til rådighet for egne tannleger, samt tannleger tilknyttet senteret. Handel, hva dermed står i forbindelse, samt deltakelse i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.3m in revenue and NOK 959,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.3m
Operating profit
NOK 959,000
Equity
NOK 1.3m
Est. value
NOK 4.7m

Financial health · 2025

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

Who owns JÆRTANNLEGENE AS?

HEIDI BØE HONNINGSVÅG
JÆRTANNLEGENE AS
NOK 5.3m rev. · NOK 959,000 profit

JÆRTANNLEGENE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JÆRTANNLEGENE AS

Who owns JÆRTANNLEGENE AS?

HEIDI BØE HONNINGSVÅG is the largest registered owner, with 100.0%.

What is the revenue of JÆRTANNLEGENE AS?

JÆRTANNLEGENE AS had revenue of NOK 5.3m in 2025.

Who is the general manager of JÆRTANNLEGENE AS?

Heidi Bøe Honningsvåg is registered as general manager of JÆRTANNLEGENE AS.

Where is JÆRTANNLEGENE AS based?

JÆRTANNLEGENE AS has its business address in Bryne.

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.