BIZTRAC BETA
Retail sale of information and communication equipment

JESSHEIM MULTIMEDIA AS

Org. no. 980844668 Limited company (AS) Ullensaker Incorporated 1999 Active
Ownership graph ↗
Operating profit NOK −46,000
Equity NOK 4.3m
Incorporated 1999
Share capital NOK 400,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−46k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JESSHEIM MULTIMEDIA AS is registered as a limited company in Ullensaker, Akershus with organisation number 980844668. The business is classified under retail sale of information and communication equipment (NACE 47.400). The company was incorporated in 1999. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Handelsvirksomhet innenfor elektronikk samt hva som står i forbindelse med dette og investeringer i aksjer og andeler samt forvaltning av eierinteresser i datterselskaper og andre virksomheter.”.

Key figures · 2025

Operating profit
NOK −46,000
Equity
NOK 4.3m
Est. value
NOK 9.9m

Financial health · 2025

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

Who owns JESSHEIM MULTIMEDIA AS?

LARS TODNEM
JESSHEIM MULTIMEDIA AS
· NOK −46,000 profit

JESSHEIM MULTIMEDIA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JESSHEIM MULTIMEDIA AS own?

JESSHEIM MULTIMEDIA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JESSHEIM MULTIMEDIA AS

Who owns JESSHEIM MULTIMEDIA AS?

LARS TODNEM is the largest registered owner, with 100.0%.

Where is JESSHEIM MULTIMEDIA AS based?

JESSHEIM MULTIMEDIA AS has its business address in Jessheim.

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.