BIZTRAC BETA
Dental practice care activities

TANNLEGE KJETIL KROGLUND AS

Org. no. 925558168 Limited company (AS) Verdal Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 8.1m
Operating profit NOK 1.5m
Equity NOK 2.1m
Incorporated 2020
Employees 6
Share capital NOK 100,000

TANNLEGE KJETIL KROGLUND AS is registered as a limited company in Verdal, Trøndelag with organisation number 925558168. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2020 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive med tannlegepraksis, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.1m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 8.1m
Operating profit
NOK 1.5m
Equity
NOK 2.1m
Est. value
NOK 7.3m

Financial health · 2024

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

Who owns TANNLEGE KJETIL KROGLUND AS?

KJETIL KROGLUND
TANNLEGE KJETIL KROGLUND AS
NOK 8.1m rev. · NOK 1.5m profit

TANNLEGE KJETIL KROGLUND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANNLEGE KJETIL KROGLUND AS

Who owns TANNLEGE KJETIL KROGLUND AS?

KJETIL KROGLUND is the largest registered owner, with 100.0%.

What is the revenue of TANNLEGE KJETIL KROGLUND AS?

TANNLEGE KJETIL KROGLUND AS had revenue of NOK 8.1m in 2024.

Who is the general manager of TANNLEGE KJETIL KROGLUND AS?

Kjetil Kroglund is registered as general manager of TANNLEGE KJETIL KROGLUND AS.

Where is TANNLEGE KJETIL KROGLUND AS based?

TANNLEGE KJETIL KROGLUND AS has its business address in Verdal.

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.