BIZTRAC BETA
Uoppgitt

HAUKOM HOLDING AS

Org. no. 931262521 Limited company (AS) Lillesand Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −35,000
Equity NOK 12,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

HAUKOM HOLDING AS is registered as a limited company in Lillesand, Agder with organisation number 931262521. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −35,000
Equity
NOK 12,000
Est. value
NOK 14,000

Financial health · 2025

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

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

Who owns HAUKOM HOLDING AS?

TOMMY HAUKOM
HAUKOM HOLDING AS
NOK 0 rev. · NOK −35,000 profit

HAUKOM HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HAUKOM HOLDING AS own?

HAUKOM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HAUKOM HOLDING AS

Who owns HAUKOM HOLDING AS?

TOMMY HAUKOM is the largest registered owner, with 50.0%.

What is the revenue of HAUKOM HOLDING AS?

HAUKOM HOLDING AS had revenue of NOK 0 in 2025.

Where is HAUKOM HOLDING AS based?

HAUKOM HOLDING AS has its business address in Høvåg.

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.