BIZTRAC BETA
Dental practice care activities

TANNLEGE VAADAL AS

Org. no. 980915271 Limited company (AS) Hamar Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −748,000
Equity NOK 8.3m
Incorporated 1999
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−748k kr).

TANNLEGE VAADAL AS is registered as a limited company in Hamar, Innlandet with organisation number 980915271. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tannlegevirksomhet og annen økonomisk virksomhet, samt virksomhet som naturlig står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −748,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −748,000
Equity
NOK 8.3m
Est. value
NOK 19.1m

Financial health · 2024

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

Who owns TANNLEGE VAADAL AS?

BØRGE HANS VAADAL
TANNLEGE VAADAL AS
NOK 1.1m rev. · NOK −748,000 profit

TANNLEGE VAADAL AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TANNLEGE VAADAL AS

Who owns TANNLEGE VAADAL AS?

BØRGE HANS VAADAL is the largest registered owner, with 80.0%.

What is the revenue of TANNLEGE VAADAL AS?

TANNLEGE VAADAL AS had revenue of NOK 1.1m in 2024.

Who is the general manager of TANNLEGE VAADAL AS?

Børge Hans Vaadal is registered as general manager of TANNLEGE VAADAL AS.

Where is TANNLEGE VAADAL AS based?

TANNLEGE VAADAL AS has its business address in Hamar.

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.