BIZTRAC BETA
Site preparation

JM-HOLDING AS

Org. no. 930016322 Limited company (AS) Tromsø Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 22,000
Operating profit NOK −6,000
Equity NOK 3,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

JM-HOLDING AS is registered as a limited company in Tromsø, Troms with organisation number 930016322. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i aksjer og eiendom samt annen virksomhet i tilknytning til dette. Selskapet kan ved aksjetegning eller på annen måte interessere seg i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 22,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 22,000
Operating profit
NOK −6,000
Equity
NOK 3,000
Est. value
NOK 5,000

Financial health · 2025

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

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

Who owns JM-HOLDING AS?

JØRGEN MØRCH
JM-HOLDING AS
NOK 22,000 rev. · NOK −6,000 profit

JM-HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JM-HOLDING AS own?

JM-HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JM-HOLDING AS

Who owns JM-HOLDING AS?

JØRGEN MØRCH is the largest registered owner, with 100.0%.

What is the revenue of JM-HOLDING AS?

JM-HOLDING AS had revenue of NOK 22,000 in 2025.

Where is JM-HOLDING AS based?

JM-HOLDING AS has its business address in Tromsø.

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.