BIZTRAC BETA
Beverage serving activities

JMC VIRKSOMHET AS

Org. no. 930813257 Limited company (AS) Horten Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 35,000
Operating profit NOK −55,000
Equity NOK 533
Incorporated 2023
Share capital NOK 30,000

Signals

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

JMC VIRKSOMHET AS is registered as a limited company in Horten, Vestfold with organisation number 930813257. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper, samt det som naturlig står i forbindelse med dette. Selskapet kan også delta i kapitalmarkedet, yte lån og garantier, samt drive konsulentvirksomhet innenfor administrasjon og ledelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 35,000 in revenue and NOK −55,000 in operating profit.

Key figures · 2025

Revenue
NOK 35,000
Operating profit
NOK −55,000
Equity
NOK 533
Est. value
NOK 25,000

Financial health · 2025

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

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

Who owns JMC VIRKSOMHET AS?

CAMZ AS
JMC VIRKSOMHET AS
NOK 35,000 rev. · NOK −55,000 profit

JMC VIRKSOMHET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JMC VIRKSOMHET AS

Who owns JMC VIRKSOMHET AS?

CAMZ AS is the largest registered owner, with 100.0%.

What is the revenue of JMC VIRKSOMHET AS?

JMC VIRKSOMHET AS had revenue of NOK 35,000 in 2025.

Where is JMC VIRKSOMHET AS based?

JMC VIRKSOMHET AS has its business address in Horten.

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.