BIZTRAC BETA
Dental practice care activities

KARIUS HOLDING AS

Org. no. 994152378 Limited company (AS) Hol Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 922,000
Operating profit NOK 637,000
Equity NOK 11.5m
Incorporated 2009
Share capital NOK 30,000

KARIUS HOLDING AS is registered as a limited company in Hol, Buskerud with organisation number 994152378. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2009. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie og drive tannhelseklinikk samt levere tjenester i denne forbindelse. Videre er selskapets formål å eie, kjøpe og selge aksjer og eiendommer, samt delta i andre selskaper, og eventuell annen forretningsvirksomhet av envhert art.”. The most recent filed accounts, for the 2024 financial year, show NOK 922,000 in revenue and NOK 637,000 in operating profit.

Key figures · 2024

Revenue
NOK 922,000
Operating profit
NOK 637,000
Equity
NOK 11.5m
Est. value
NOK 10.0m

Financial health · 2024

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

Who owns KARIUS HOLDING AS?

TROND ANDERSSEN
KARIUS HOLDING AS
NOK 922,000 rev. · NOK 637,000 profit

KARIUS HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about KARIUS HOLDING AS

Who owns KARIUS HOLDING AS?

TROND ANDERSSEN is the largest registered owner, with 50.0%.

What is the revenue of KARIUS HOLDING AS?

KARIUS HOLDING AS had revenue of NOK 922,000 in 2024.

Who is the general manager of KARIUS HOLDING AS?

Trond Anderssen is registered as general manager of KARIUS HOLDING AS.

Where is KARIUS HOLDING AS based?

KARIUS HOLDING AS has its business address in Geilo.

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.