BIZTRAC BETA
Dental practice care activities

SANDELIEN HELSE AS

Org. no. 916708785 Limited company (AS) Ål Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 755,000
Equity NOK 31,000
Incorporated 2016
Share capital NOK 30,000

SANDELIEN HELSE AS is registered as a limited company in Ål, Buskerud with organisation number 916708785. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Helsetjenester, herunder å delta i andre selskap med lignende virksomhet, investere i verdipapirer og fast eiendom, samt erverv av kapitalinteresser og andeler i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 755,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 755,000
Equity
NOK 31,000
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.0%
Weak
Equity as a share of total capital

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

Who owns SANDELIEN HELSE AS?

GUNN-KJERSTI SANDELIEN
SANDELIEN HELSE AS
NOK 3.3m rev. · NOK 755,000 profit

SANDELIEN HELSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANDELIEN HELSE AS

Who owns SANDELIEN HELSE AS?

GUNN-KJERSTI SANDELIEN is the largest registered owner, with 100.0%.

What is the revenue of SANDELIEN HELSE AS?

SANDELIEN HELSE AS had revenue of NOK 3.3m in 2025.

Who is the general manager of SANDELIEN HELSE AS?

Gunn-Kjersti Sandelien is registered as general manager of SANDELIEN HELSE AS.

Where is SANDELIEN HELSE AS based?

SANDELIEN HELSE AS has its business address in Ål.

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.