BIZTRAC BETA
Uoppgitt

JHK HOLDING SANDNESSJØEN AS

Org. no. 934652444 Limited company (AS) Alstahaug Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 34,000
Incorporated 2024
Share capital NOK 40,000

JHK HOLDING SANDNESSJØEN AS is registered as a limited company in Alstahaug, Nordland with organisation number 934652444. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Investering i næringsvirksomhet, herunder aksjer og andeler, samt deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 34,000
Est. value
NOK 40,000

Financial health · 2024

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

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

Who owns JHK HOLDING SANDNESSJØEN AS?

JAN-HÅKON KRISTIANSEN
JHK HOLDING SANDNESSJØEN AS
NOK 0 rev. · NOK 0 profit

JHK HOLDING SANDNESSJØEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JHK HOLDING SANDNESSJØEN AS own?

JHK HOLDING SANDNESSJØEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JHK HOLDING SANDNESSJØEN AS

Who owns JHK HOLDING SANDNESSJØEN AS?

JAN-HÅKON KRISTIANSEN is the largest registered owner, with 100.0%.

What is the revenue of JHK HOLDING SANDNESSJØEN AS?

JHK HOLDING SANDNESSJØEN AS had revenue of NOK 0 in 2024.

Where is JHK HOLDING SANDNESSJØEN AS based?

JHK HOLDING SANDNESSJØEN AS has its business address in Sandnessjøen.

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.