BIZTRAC BETA
Dental practice care activities

STUDENTERLUNDEN TANNLEGESENTER AS

Org. no. 987462515 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 239,000
Equity NOK 1.4m
Incorporated 2004
Share capital NOK 100,000

STUDENTERLUNDEN TANNLEGESENTER AS is registered as a limited company in Oslo, Oslo with organisation number 987462515. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av allmennpraksis for tannleger.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 239,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK 239,000
Equity
NOK 1.4m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns STUDENTERLUNDEN TANNLEGESENTER AS?

THERESE LIEN SØRENSEN
STUDENTERLUNDEN TANNLEGESENTER AS
NOK 4.8m rev. · NOK 239,000 profit

STUDENTERLUNDEN TANNLEGESENTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STUDENTERLUNDEN TANNLEGESENTER AS

Who owns STUDENTERLUNDEN TANNLEGESENTER AS?

THERESE LIEN SØRENSEN is the largest registered owner, with 50.0%.

What is the revenue of STUDENTERLUNDEN TANNLEGESENTER AS?

STUDENTERLUNDEN TANNLEGESENTER AS had revenue of NOK 4.8m in 2025.

Who is the general manager of STUDENTERLUNDEN TANNLEGESENTER AS?

Ingrid Birkeland Melcher is registered as general manager of STUDENTERLUNDEN TANNLEGESENTER AS.

Where is STUDENTERLUNDEN TANNLEGESENTER AS based?

STUDENTERLUNDEN TANNLEGESENTER 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.