BIZTRAC BETA
Preventive health care activities

HALDEN HOLDING AS

Org. no. 932465698 Limited company (AS) Lier Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK −7,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

HALDEN HOLDING AS is registered as a limited company in Lier, Buskerud with organisation number 932465698. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer i selskaper og eie andre verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK −7,000

Financial health · 2025

Liquidity
0.81
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-23.2%
Weak
Equity as a share of total capital

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

Who owns HALDEN HOLDING AS?

Joakim Lybeck Halden
HALDEN HOLDING AS
NOK 0 rev. · NOK −4,000 profit

HALDEN HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HALDEN HOLDING AS own?

HALDEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HALDEN HOLDING AS

Who owns HALDEN HOLDING AS?

Joakim Lybeck Halden is the largest registered owner, with 50.0%.

What is the revenue of HALDEN HOLDING AS?

HALDEN HOLDING AS had revenue of NOK 0 in 2025.

Where is HALDEN HOLDING AS based?

HALDEN HOLDING AS has its business address in Sylling.

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.