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

TANNLEGE BEATE KLEIVDAL AS

Org. no. 999331890 Limited company (AS) Bergen Incorporated 2013 Active
Revenue 2025 NOK 5.8m
Operating profit NOK 206,000
Equity NOK 182,000
Incorporated 2013
Share capital NOK 30,000

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

Key figures · 2025

Revenue
NOK 5.8m
▲ +11 %
Operating profit
NOK 206,000
▲ +487 %
Equity
NOK 182,000
▲ +19 %
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
25.7%
Very good
Return on total assets
Solidity
21.3%
Good
Equity as a share of total capital

Who owns TANNLEGE BEATE KLEIVDAL AS?

TANNLEGE BEATE KLEIVDAL AS
NOK 5.8m rev. · NOK 206,000 profit

TANNLEGE BEATE KLEIVDAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNLEGE BEATE KLEIVDAL AS

Who owns TANNLEGE BEATE KLEIVDAL AS?

Beate Vik Kleivdal is the largest registered owner, with 100.0%.

What is the revenue of TANNLEGE BEATE KLEIVDAL AS?

TANNLEGE BEATE KLEIVDAL AS had revenue of NOK 5.8m in 2025.

Who is the general manager of TANNLEGE BEATE KLEIVDAL AS?

Beate Vik Kleivdal is registered as general manager of TANNLEGE BEATE KLEIVDAL AS.

Where is TANNLEGE BEATE KLEIVDAL AS based?

TANNLEGE BEATE KLEIVDAL AS has its business address in Nesttun.

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.