BIZTRAC BETA
COMPANY REGISTER PROFILE
926687964 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Dental practice care activities

TANNLEGE KIRSTI KRISTOFFERSEN AS

Org. no. 926687964 Limited company (AS) Kristiansund Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK −33,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−33k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

TANNLEGE KIRSTI KRISTOFFERSEN AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 926687964. 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 100 shares. The company's stated purpose is: “Tannhelsetjenester.”.

Key figures · 2025

Operating profit
NOK −13,000
Equity
NOK −33,000

Financial health · 2025

Liquidity
0.19
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-435.1%
Weak
Equity as a share of total capital

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

Who owns TANNLEGE KIRSTI KRISTOFFERSEN AS?

Kirsti Kristoffersen
TANNLEGE KIRSTI KRISTOFFERSEN AS
· NOK −13,000 profit

TANNLEGE KIRSTI KRISTOFFERSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNLEGE KIRSTI KRISTOFFERSEN AS

Who owns TANNLEGE KIRSTI KRISTOFFERSEN AS?

Kirsti Kristoffersen is the largest registered owner, with 100.0%.

Who is the general manager of TANNLEGE KIRSTI KRISTOFFERSEN AS?

Kirsti Kristoffersen is registered as general manager of TANNLEGE KIRSTI KRISTOFFERSEN AS.

Where is TANNLEGE KIRSTI KRISTOFFERSEN AS based?

TANNLEGE KIRSTI KRISTOFFERSEN AS has its business address in Kristiansund N.

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.