BIZTRAC BETA
Uoppgitt

J.K. HAUKÅS HOLDING AS

Org. no. 989181718 Limited company (AS) Tysvær Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −39,000
Equity NOK 2.5m
Incorporated 2005
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−39k kr).

J.K. HAUKÅS HOLDING AS is registered as a limited company in Tysvær, Rogaland with organisation number 989181718. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 40,000, divided into 1683 shares. The company's stated purpose is: “Investering i aksjer, andeler, verdipapirer samt hva hermed står i forbindelse, herunder delta i andre selskap med liknende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −39,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −39,000
Equity
NOK 2.5m
Est. value
NOK 7.6m

Financial health · 2024

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

Who owns J.K. HAUKÅS HOLDING AS?

KJELL ARNE HAUKÅS
J.K. HAUKÅS HOLDING AS
NOK 0 rev. · NOK −39,000 profit

J.K. HAUKÅS HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does J.K. HAUKÅS HOLDING AS own?

J.K. HAUKÅS HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about J.K. HAUKÅS HOLDING AS

Who owns J.K. HAUKÅS HOLDING AS?

KJELL ARNE HAUKÅS is the largest registered owner, with 33.3%.

What is the revenue of J.K. HAUKÅS HOLDING AS?

J.K. HAUKÅS HOLDING AS had revenue of NOK 0 in 2024.

Where is J.K. HAUKÅS HOLDING AS based?

J.K. HAUKÅS HOLDING AS has its business address in Aksdal.

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.