BIZTRAC BETA
Wholesale of information and communication equipment

MJØSDATA AS

Org. no. 981969634 Limited company (AS) Gjøvik Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 16.0m
Operating profit NOK 855,000
Equity NOK 5.8m
Incorporated 2000
Employees 6
Share capital NOK 488,000

MJØSDATA AS is registered as a limited company in Gjøvik, Innlandet with organisation number 981969634. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2000 and has 6 registered employees. Registered share capital is NOK 488,000, divided into 976 shares. The company's stated purpose is: “Salg og service av data-, audio-, video- og teleutstyr inklusive programvare og kurs som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 16.0m in revenue and NOK 855,000 in operating profit.

Key figures · 2025

Revenue
NOK 16.0m
Operating profit
NOK 855,000
Equity
NOK 5.8m
Est. value
NOK 5.9m

Financial health · 2025

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

Who owns MJØSDATA AS?

ROAR TVEIT
MJØSDATA AS
NOK 16.0m rev. · NOK 855,000 profit

MJØSDATA AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MJØSDATA AS own?

MJØSDATA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MJØSDATA AS

Who owns MJØSDATA AS?

ROAR TVEIT is the largest registered owner, with 50.0%.

What is the revenue of MJØSDATA AS?

MJØSDATA AS had revenue of NOK 16.0m in 2025.

Who is the general manager of MJØSDATA AS?

Geir Oddbjørn Skinstad is registered as general manager of MJØSDATA AS.

Where is MJØSDATA AS based?

MJØSDATA AS has its business address in Gjøvik.

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.