BIZTRAC BETA
Wholesale of other machinery and equipment

MEDIA SYSTEM HOLDING AS

Org. no. 916391560 Limited company (AS) Larvik Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −18,000
Equity NOK 1.5m
Incorporated 2015
Share capital NOK 30,000

Signals

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

MEDIA SYSTEM HOLDING AS is registered as a limited company in Larvik, Vestfold with organisation number 916391560. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive investeringsvirksomhet, herunder investering i finansielle instrumenter, selskapsandeler og fast eiendom. Virksomheten skal også delta i kjøp og salg av elektroniske software/hardware produkter, samt utleie .”.

Key figures · 2025

Operating profit
NOK −18,000
Equity
NOK 1.5m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns MEDIA SYSTEM HOLDING AS?

JAN ÅGE ANDRESEN
MEDIA SYSTEM HOLDING AS
· NOK −18,000 profit

MEDIA SYSTEM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MEDIA SYSTEM HOLDING AS own?

MEDIA SYSTEM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MEDIA SYSTEM HOLDING AS

Who owns MEDIA SYSTEM HOLDING AS?

JAN ÅGE ANDRESEN is the largest registered owner, with 100.0%.

Who is the general manager of MEDIA SYSTEM HOLDING AS?

Jan Åge Andresen is registered as general manager of MEDIA SYSTEM HOLDING AS.

Where is MEDIA SYSTEM HOLDING AS based?

MEDIA SYSTEM HOLDING AS has its business address in Larvik.

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.