BIZTRAC BETA
Dental practice care activities

TANNLEGE KJERSTI GJERDE AS

Org. no. 998585597 Limited company (AS) Bergen Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 58,000
Operating profit NOK −1,000
Equity NOK 4.9m
Incorporated 2012
Share capital NOK 30,000

Signals

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

TANNLEGE KJERSTI GJERDE AS is registered as a limited company in Bergen, Vestland with organisation number 998585597. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Tannlegetjenester og annet som naturlig faller sammen med dette, herunder utleie, investering i aksjer og eiendom, nettbaserte tjenester og å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 58,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 58,000
Operating profit
NOK −1,000
Equity
NOK 4.9m
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns TANNLEGE KJERSTI GJERDE AS?

KJERSTI GJERDE
TANNLEGE KJERSTI GJERDE AS
NOK 58,000 rev. · NOK −1,000 profit

TANNLEGE KJERSTI GJERDE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNLEGE KJERSTI GJERDE AS

Who owns TANNLEGE KJERSTI GJERDE AS?

KJERSTI GJERDE is the largest registered owner, with 100.0%.

What is the revenue of TANNLEGE KJERSTI GJERDE AS?

TANNLEGE KJERSTI GJERDE AS had revenue of NOK 58,000 in 2025.

Where is TANNLEGE KJERSTI GJERDE AS based?

TANNLEGE KJERSTI GJERDE 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 15.06.2026.

Report a problem

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