BIZTRAC BETA
Dental practice care activities

KJÆRLIGHETSSTIEN 53 AS

Org. no. 929580400 Limited company (AS) Namsos Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −57,000
Equity NOK 3.0m
Incorporated 2022
Share capital NOK 60,000

Signals

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

KJÆRLIGHETSSTIEN 53 AS is registered as a limited company in Namsos, Trøndelag with organisation number 929580400. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2022. Registered share capital is NOK 60,000, divided into 600 shares. The company's stated purpose is: “Investering og deltakelse i andre selskap, investering i verdipapirer, investering i -og drift av eiendom og tannlegevirksomhet samt alt som står i naturlig forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −57,000
Equity
NOK 3.0m
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns KJÆRLIGHETSSTIEN 53 AS?

HANS HAUGUM
KJÆRLIGHETSSTIEN 53 AS
· NOK −57,000 profit

KJÆRLIGHETSSTIEN 53 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KJÆRLIGHETSSTIEN 53 AS own?

KJÆRLIGHETSSTIEN 53 AS holds a stake in 1 company:

See the full ownership structure →

Group structure

KJÆRLIGHETSSTIEN 53 AS er morselskap for 1 datterselskap:

Frequently asked questions about KJÆRLIGHETSSTIEN 53 AS

Who owns KJÆRLIGHETSSTIEN 53 AS?

HANS HAUGUM is the largest registered owner, with 100.0%.

Who is the general manager of KJÆRLIGHETSSTIEN 53 AS?

Hans Haugum is registered as general manager of KJÆRLIGHETSSTIEN 53 AS.

Where is KJÆRLIGHETSSTIEN 53 AS based?

KJÆRLIGHETSSTIEN 53 AS has its business address in Namsos.

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.