biztrac. BETA
COMPANY REGISTER PROFILE
920245137 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Dental practice care activities

FLESLAND TANNLEGESENTER AS

Org. no. 920245137 Limited company (AS) Bergen Incorporated 2017 Active
Revenue 2025 NOK 1.4m
Operating profit NOK −33,000
Equity NOK 20,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

FLESLAND TANNLEGESENTER AS is registered as a limited company in Bergen, Vestland with organisation number 920245137. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tannlegevirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK −33,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
▲ +3 %
Operating profit
NOK −33,000
▼ −7043 %
Equity
NOK 20,000
▼ −62 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
0.60
Weak
Current assets ÷ current liabilities
Profitability
-24.5%
Not satisfactory
Return on total assets
Solidity
15.1%
Weak
Equity as a share of total capital

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

Who owns FLESLAND TANNLEGESENTER AS?

FLESLAND TANNLEGESENTER AS
NOK 1.4m rev. · NOK −33,000 profit

FLESLAND TANNLEGESENTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FLESLAND TANNLEGESENTER AS

Who owns FLESLAND TANNLEGESENTER AS?

Cathrine Lorentzen is the largest registered owner, with 50.0%.

What is the revenue of FLESLAND TANNLEGESENTER AS?

FLESLAND TANNLEGESENTER AS had revenue of NOK 1.4m in 2025.

Where is FLESLAND TANNLEGESENTER AS based?

FLESLAND TANNLEGESENTER AS has its business address in Kokstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.