BIZTRAC BETA
Dental practice care activities

TANNLEGE RANGHILD HESLA BREIE AS

Org. no. 913257014 Limited company (AS) Lom Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 20,000
Equity NOK 823,000
Incorporated 2014
Share capital NOK 30,000

TANNLEGE RANGHILD HESLA BREIE AS is registered as a limited company in Lom, Innlandet with organisation number 913257014. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Alt innen tannhelsetjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 20,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 20,000
Equity
NOK 823,000
Est. value
NOK 642,000

Financial health · 2025

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

Who owns TANNLEGE RANGHILD HESLA BREIE AS?

RAGNHILD HESLA BREIE
TANNLEGE RANGHILD HESLA BREIE AS
NOK 2.5m rev. · NOK 20,000 profit

TANNLEGE RANGHILD HESLA BREIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNLEGE RANGHILD HESLA BREIE AS

Who owns TANNLEGE RANGHILD HESLA BREIE AS?

RAGNHILD HESLA BREIE is the largest registered owner, with 100.0%.

What is the revenue of TANNLEGE RANGHILD HESLA BREIE AS?

TANNLEGE RANGHILD HESLA BREIE AS had revenue of NOK 2.5m in 2025.

Who is the general manager of TANNLEGE RANGHILD HESLA BREIE AS?

Ragnhild Hesla Breie is registered as general manager of TANNLEGE RANGHILD HESLA BREIE AS.

Where is TANNLEGE RANGHILD HESLA BREIE AS based?

TANNLEGE RANGHILD HESLA BREIE AS has its business address in Lom.

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.