BIZTRAC BETA
Wholesale of other machinery and equipment

LOGISNEXT NORWAY AS

Org. no. 982711339 Limited company (AS) Nittedal Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 24.6m
Operating profit NOK 925,000
Equity NOK 5.6m
Incorporated 2000
Employees 7
Share capital NOK 2.0m

LOGISNEXT NORWAY AS is registered as a limited company in Nittedal, Akershus with organisation number 982711339. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2000 and has 7 registered employees. Registered share capital is NOK 2.0m, divided into 20000 shares. The company's stated purpose is: “Salg og service samt utleie av trucker. Selskapet plikter også å utføre annen virksomhet som har naturlig sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 24.6m in revenue and NOK 925,000 in operating profit.

Key figures · 2025

Revenue
NOK 24.6m
Operating profit
NOK 925,000
Equity
NOK 5.6m
Est. value
NOK 6.1m

Financial health · 2025

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

Who owns LOGISNEXT NORWAY AS?

MITSUBISHI LOGISNEXT EUROPE BV
LOGISNEXT NORWAY AS
NOK 24.6m rev. · NOK 925,000 profit

LOGISNEXT NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOGISNEXT NORWAY AS

Who owns LOGISNEXT NORWAY AS?

MITSUBISHI LOGISNEXT EUROPE BV is the largest registered owner, with 100.0%.

What is the revenue of LOGISNEXT NORWAY AS?

LOGISNEXT NORWAY AS had revenue of NOK 24.6m in 2025.

Who is the general manager of LOGISNEXT NORWAY AS?

Lars Baltzer Eriksen is registered as general manager of LOGISNEXT NORWAY AS.

Where is LOGISNEXT NORWAY AS based?

LOGISNEXT NORWAY AS has its business address in Hagan.

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.