BIZTRAC BETA
Dental practice care activities

RYEN TANNHELSEKLINIKK AS

Org. no. 988361615 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK −189,000
Equity NOK 337,000
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−189k kr).

RYEN TANNHELSEKLINIKK AS is registered as a limited company in Oslo, Oslo with organisation number 988361615. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tannlegevirksomhet og virksomhet som står i forbindelse med dette”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK −189,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK −189,000
Equity
NOK 337,000
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.3%
Good
Equity as a share of total capital

Who owns RYEN TANNHELSEKLINIKK AS?

TANNLEGE ÅBERG AS
RYEN TANNHELSEKLINIKK AS
NOK 2.7m rev. · NOK −189,000 profit

RYEN TANNHELSEKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RYEN TANNHELSEKLINIKK AS

Who owns RYEN TANNHELSEKLINIKK AS?

TANNLEGE ÅBERG AS is the largest registered owner, with 100.0%.

What is the revenue of RYEN TANNHELSEKLINIKK AS?

RYEN TANNHELSEKLINIKK AS had revenue of NOK 2.7m in 2025.

Who is the general manager of RYEN TANNHELSEKLINIKK AS?

Siri Beathe Åberg is registered as general manager of RYEN TANNHELSEKLINIKK AS.

Where is RYEN TANNHELSEKLINIKK AS based?

RYEN TANNHELSEKLINIKK AS has its business address in Oslo.

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.