BIZTRAC BETA
Rental and operating of own or leased real estate

JKM HOLDING AS

Org. no. 989105884 Limited company (AS) Stavanger Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 421,000
Operating profit NOK −897,000
Equity NOK 132.9m
Incorporated 2005
Share capital NOK 100,000

Signals

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

JKM HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 989105884. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 500 shares. The company's stated purpose is: “Investering i aksjer, andeler og eiendommer, samt rådgivningstjenester og deltakelse i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 421,000 in revenue and NOK −897,000 in operating profit.

Key figures · 2024

Revenue
NOK 421,000
Operating profit
NOK −897,000
Equity
NOK 132.9m
Est. value
NOK 564.5m

Financial health · 2024

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

Who owns JKM HOLDING AS?

JØRN SALVESEN
JKM HOLDING AS
NOK 421,000 rev. · NOK −897,000 profit

JKM HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does JKM HOLDING AS own?

JKM HOLDING AS holds stakes in 12 companies:

See the full ownership structure →

Frequently asked questions about JKM HOLDING AS

Who owns JKM HOLDING AS?

JØRN SALVESEN is the largest registered owner, with 70.0%.

What is the revenue of JKM HOLDING AS?

JKM HOLDING AS had revenue of NOK 421,000 in 2024.

Where is JKM HOLDING AS based?

JKM HOLDING AS has its business address in Stavanger.

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.