BIZTRAC BETA
Dental practice care activities

LAGUNEN TANNLEGE NJØSEN & ØREN AS

Org. no. 927094754 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 7.0m
Operating profit NOK 1.4m
Equity NOK 2.2m
Incorporated 2021
Share capital NOK 30,000

LAGUNEN TANNLEGE NJØSEN & ØREN AS is registered as a limited company in Bergen, Vestland with organisation number 927094754. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Tannklinikk og alt som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.0m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 7.0m
Operating profit
NOK 1.4m
Equity
NOK 2.2m
Est. value
NOK 6.8m

Financial health · 2025

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

Who owns LAGUNEN TANNLEGE NJØSEN & ØREN AS?

BERIT ANNE NJØSEN
LAGUNEN TANNLEGE NJØSEN & ØREN AS
NOK 7.0m rev. · NOK 1.4m profit

LAGUNEN TANNLEGE NJØSEN & ØREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAGUNEN TANNLEGE NJØSEN & ØREN AS

Who owns LAGUNEN TANNLEGE NJØSEN & ØREN AS?

BERIT ANNE NJØSEN is the largest registered owner, with 100.0%.

What is the revenue of LAGUNEN TANNLEGE NJØSEN & ØREN AS?

LAGUNEN TANNLEGE NJØSEN & ØREN AS had revenue of NOK 7.0m in 2025.

Who is the general manager of LAGUNEN TANNLEGE NJØSEN & ØREN AS?

Berit Anne Njøsen is registered as general manager of LAGUNEN TANNLEGE NJØSEN & ØREN AS.

Where is LAGUNEN TANNLEGE NJØSEN & ØREN AS based?

LAGUNEN TANNLEGE NJØSEN & ØREN AS has its business address in Rådal.

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.