BIZTRAC BETA
Service activities incidental to water transportation

NARVIK BULKTERMINAL AS

Org. no. 919496827 Limited company (AS) Narvik Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 77.0m
Operating profit NOK 7.1m
Equity NOK 25.4m
Incorporated 2017
Employees 16
Share capital NOK 3.0m

NARVIK BULKTERMINAL AS is registered as a limited company in Narvik, Nordland with organisation number 919496827. The business is classified under service activities incidental to water transportation (NACE 52.220). The company was incorporated in 2017 and has 16 registered employees. Registered share capital is NOK 3.0m, divided into 30000 shares. The company's stated purpose is: “Drift av kommunalt havne- og kaianlegg, samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 77.0m in revenue and NOK 7.1m in operating profit.

Key figures · 2024

Revenue
NOK 77.0m
Operating profit
NOK 7.1m
Equity
NOK 25.4m
Est. value
NOK 36.1m

Financial health · 2024

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

Who owns NARVIK BULKTERMINAL AS?

NARVIK HAVN KF
NARVIK BULKTERMINAL AS
NOK 77.0m rev. · NOK 7.1m profit

NARVIK BULKTERMINAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NARVIK BULKTERMINAL AS

Who owns NARVIK BULKTERMINAL AS?

NARVIK HAVN KF is the largest registered owner, with 100.0%.

What is the revenue of NARVIK BULKTERMINAL AS?

NARVIK BULKTERMINAL AS had revenue of NOK 77.0m in 2024.

Who is the general manager of NARVIK BULKTERMINAL AS?

Rolf Inge André Gundersen is registered as general manager of NARVIK BULKTERMINAL AS.

Where is NARVIK BULKTERMINAL AS based?

NARVIK BULKTERMINAL AS has its business address in Narvik.

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.