BIZTRAC BETA
Uoppgitt

HALSEBØ HOLDING AS

Org. no. 928465179 Limited company (AS) Moss Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 11,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

HALSEBØ HOLDING AS is registered as a limited company in Moss, Østfold with organisation number 928465179. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Alene, eller sammen med andre, å investere i teknologiselskaper, aksjer, fast eiendom og andre kapitalvarer, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 11,000
Est. value
NOK 13,000

Financial health · 2025

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

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

Who owns HALSEBØ HOLDING AS?

SVEIN HALSEBØ DAVIDSEN
HALSEBØ HOLDING AS
NOK 0 rev. · NOK −7,000 profit

HALSEBØ HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HALSEBØ HOLDING AS own?

HALSEBØ HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HALSEBØ HOLDING AS

Who owns HALSEBØ HOLDING AS?

SVEIN HALSEBØ DAVIDSEN is the largest registered owner, with 100.0%.

What is the revenue of HALSEBØ HOLDING AS?

HALSEBØ HOLDING AS had revenue of NOK 0 in 2025.

Where is HALSEBØ HOLDING AS based?

HALSEBØ HOLDING AS has its business address in Dilling.

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.