BIZTRAC BETA
Dental practice care activities

SANGENUTEN HOLDING AS

Org. no. 933896641 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 2.1m
Incorporated 2024
Share capital NOK 40,000

Signals

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

SANGENUTEN HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 933896641. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2024. Registered share capital is NOK 40,000, divided into 10000 shares. The company's stated purpose is: “Investeringer, aksjer og verdipapirer, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 2.1m
Est. value
NOK 11.3m

Financial health · 2025

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

Who owns SANGENUTEN HOLDING AS?

KRISTIN AARVOLD HOFLAND
SANGENUTEN HOLDING AS
NOK 0 rev. · NOK −10,000 profit

SANGENUTEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SANGENUTEN HOLDING AS own?

SANGENUTEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SANGENUTEN HOLDING AS

Who owns SANGENUTEN HOLDING AS?

KRISTIN AARVOLD HOFLAND is the largest registered owner, with 100.0%.

What is the revenue of SANGENUTEN HOLDING AS?

SANGENUTEN HOLDING AS had revenue of NOK 0 in 2025.

Where is SANGENUTEN HOLDING AS based?

SANGENUTEN HOLDING AS has its business address in Snarøya.

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.