BIZTRAC BETA
Dental practice care activities

STORO STORSENTER TANNKLINIKK AS

Org. no. 925046582 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 8.2m
Operating profit NOK 547,000
Equity NOK −741,000
Incorporated 2020
Employees 13
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−741k kr).

STORO STORSENTER TANNKLINIKK AS is registered as a limited company in Oslo, Oslo with organisation number 925046582. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2020 and has 13 registered employees. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Tannhelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.2m in revenue and NOK 547,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.2m
Operating profit
NOK 547,000
Equity
NOK −741,000
Est. value
NOK 2.9m

Financial health · 2024

Liquidity
3.45
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-22.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STORO STORSENTER TANNKLINIKK AS?

ELISABETH TYRI FAGERBERG
STORO STORSENTER TANNKLINIKK AS
NOK 8.2m rev. · NOK 547,000 profit

STORO STORSENTER TANNKLINIKK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about STORO STORSENTER TANNKLINIKK AS

Who owns STORO STORSENTER TANNKLINIKK AS?

ELISABETH TYRI FAGERBERG is the largest registered owner, with 51.0%.

What is the revenue of STORO STORSENTER TANNKLINIKK AS?

STORO STORSENTER TANNKLINIKK AS had revenue of NOK 8.2m in 2024.

Where is STORO STORSENTER TANNKLINIKK AS based?

STORO STORSENTER TANNKLINIKK 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.