BIZTRAC BETA
Dental practice care activities

TANNLEGE EDVIN GRÅDAL AS

Org. no. 977075114 Limited company (AS) Røros Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 681,000
Equity NOK 15.9m
Incorporated 1997
Share capital NOK 30,000

TANNLEGE EDVIN GRÅDAL AS is registered as a limited company in Røros, Trøndelag with organisation number 977075114. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 1997. Registered share capital is NOK 30,000, divided into 250 shares. The company's stated purpose is: “Tannlegevirksomhet, handel/agenturvirksomhet, konsulentvirksomhet samt alt som står i forbindelse hermed, herunder eiendomsdrift og deltakelse i andre selskap. ”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 681,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 681,000
Equity
NOK 15.9m
Est. value
NOK 13.0m

Financial health · 2025

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

Who owns TANNLEGE EDVIN GRÅDAL AS?

EDVIN GRÅDAL
TANNLEGE EDVIN GRÅDAL AS
NOK 2.2m rev. · NOK 681,000 profit

TANNLEGE EDVIN GRÅDAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNLEGE EDVIN GRÅDAL AS

Who owns TANNLEGE EDVIN GRÅDAL AS?

EDVIN GRÅDAL is the largest registered owner, with 100.0%.

What is the revenue of TANNLEGE EDVIN GRÅDAL AS?

TANNLEGE EDVIN GRÅDAL AS had revenue of NOK 2.2m in 2025.

Who is the general manager of TANNLEGE EDVIN GRÅDAL AS?

Edvin Grådal is registered as general manager of TANNLEGE EDVIN GRÅDAL AS.

Where is TANNLEGE EDVIN GRÅDAL AS based?

TANNLEGE EDVIN GRÅDAL AS has its business address in Røros.

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.