BIZTRAC BETA
Wholesale of information and communication equipment

HITACHI VANTARA AS

Org. no. 944865764 Limited company (AS) Bærum Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 133.2m
Operating profit NOK 2.7m
Equity NOK 27.9m
Incorporated 1987
Employees 12
Share capital NOK 1.5m

HITACHI VANTARA AS is registered as a limited company in Bærum, Akershus with organisation number 944865764. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 1987 and has 12 registered employees. Registered share capital is NOK 1.5m, divided into 1500 shares. The company's stated purpose is: “Kjøp, salg og utleie av datautstyr, samt eventuell deltagelse i andre foretagende med samme eller lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 133.2m in revenue and NOK 2.7m in operating profit.

Key figures · 2025

Revenue
NOK 133.2m
Operating profit
NOK 2.7m
Equity
NOK 27.9m
Est. value
NOK 22.0m

Financial health · 2025

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.5%
Good
Equity as a share of total capital

Who owns HITACHI VANTARA AS?

HITACHI VANTARA NEDERLAND BV
HITACHI VANTARA AS
NOK 133.2m rev. · NOK 2.7m profit

HITACHI VANTARA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HITACHI VANTARA AS

Who owns HITACHI VANTARA AS?

HITACHI VANTARA NEDERLAND BV is the largest registered owner, with 100.0%.

What is the revenue of HITACHI VANTARA AS?

HITACHI VANTARA AS had revenue of NOK 133.2m in 2025.

Who is the general manager of HITACHI VANTARA AS?

Kjell Johan Sven Ahlzen is registered as general manager of HITACHI VANTARA AS.

Where is HITACHI VANTARA AS based?

HITACHI VANTARA AS has its business address in Lysaker.

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.