Skip to content

MSC KILIMANJARO IV

Container ship · Liberia · built 2006 · AIS Class A

IMO9318175MMSI636013001Call signA8JX3Last AIS position Oct 6, 2026, 14:15 UTC

In short

MSC KILIMANJARO IV (Container ship, Liberia flag) was last seen on AIS on , moored, in the port of Valencia. Its crew-entered AIS destination is ESVLC (Valencia); its reported draught is 10.1 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 14:29 UTC). It arrived there on Oct 5, 2026, 19:40 UTC. ISM manager: MSC Shipmanagement Ltd (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Vessel type
Container ship
Year built
2006
Gross tonnage
39,906
Size (length × beam)
261 m × 32 m

Watch this ship

Get an email when MSC KILIMANJARO IV arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

Free forever. No card. A free account follows up to 5 ships and ports.

Photo of X-Press Kilimanjaro
Photo: Wolfgang Fricke · Licence: CC BY 3.0 · via Wikimedia Commons

Last reported position

received
Position
39.438° N, 0.3289° W
Area
Mediterranean Sea
Speed
0 kn
Course
203°
Heading
203°
39.438° N, 0.3289° W
Open the full live map →

Last 30 days: 1 port call (Valencia).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
MSC KILIMANJARO IV
IMO numberWhat is an IMO number?
9318175
MMSIWhat is an MMSI?
636013001
Call signWhat is a call sign?
A8JX3
Vessel type
Container ship
AIS ship type
Cargo (hazardous cat. D)
Gross tonnageGross tonnage vs deadweight
39,906
Length overall
260.6 m
Beam
32.3 m
Year built
2006

A tag next to a value names the register that supplied it (hover or tap it for the record and date). Values without a tag come from the ship's own AIS broadcasts or from Wikidata. Position and identity are derived live from AIS.

Ownership & management

Each line shows where the fact comes from. Links backed by an identifier point to the company page.

ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Oct 5, 2026
Builder
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026

Timeline

Dated events for this ship from every source Voydar holds, newest first. Each line names its source; derived items say how they were derived.

DateEventSource
Arrived at ValenciaAIS-detectedVoydar port-call detector (AIS geofence)
Call sign changed from A8JX3 to DATAHUBAIS, seen by Voydar
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)

Owner, operator and manager changes found by comparing yearly EU MRV reports are dated to the reporting year ("during 2025"), not to a day. Port calls here are the most recent only; the full lists are further down.

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
202115,767 t5,052 t69 days557 kg
20223,610 t1,152 t21 days487 kg
202515,962 t5,116 t93 days487 kg

Technical efficiency: EEXI (13.84 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

Port calls

Two kinds of evidence, kept apart: calls Voydar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Valencia ESVLCOct 5, 2026, 19:40 UTCin port—

Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrival(matched by call sign)Oct 23, 2023, 13:37 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalOct 22, 2023, 21:20 UTCNCPBSHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Sep 28, 2023, 01:47 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Sep 13, 2023, 08:45 UTCTSKHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Aug 23, 2023, 03:31 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Aug 7, 2023, 13:05 UTCTSKHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJul 13, 2023, 09:37 UTCKC10Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJun 2, 2023, 06:51 UTCELCHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)May 1, 2023, 01:26 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMar 3, 2023, 21:40 UTCNCPBWHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Feb 16, 2023, 23:08 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Jan 6, 2023, 01:36 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)

Records published by the authority named on each row. Earliest record for this ship: January 3, 2007.

Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.

Frequently asked questions

Where is MSC KILIMANJARO IV now?
MSC KILIMANJARO IV (Container ship, Liberia flag) was last seen on AIS on Oct 6, 2026, 14:15 UTC, moored, in the port of Valencia. The crew-entered destination was ESVLC (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 14:29 UTC). This report does not confirm the ship’s current route.
What kind of ship is MSC KILIMANJARO IV?
MSC KILIMANJARO IV is a container ship sailing under the flag of Liberia, built in 2006 by Dalian Shipbuilding Industry Company. The vessel is 260.6 m long with a beam of 32.3 m and has a gross tonnage of 39,906.
Who is recorded as the owner or manager of MSC KILIMANJARO IV?
MSC Shipmanagement Ltd is recorded as ISM manager for MSC KILIMANJARO IV (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for MSC KILIMANJARO IV?
Voydar has no matched sanctions record displayed for MSC KILIMANJARO IV from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels, the New Zealand Russia Sanctions Register and the French national asset-freeze register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for MSC KILIMANJARO IV. Missing records do not establish whether the ship has been detained.

Use this data

This page is also available as JSON, free, with the source and licence of every section. Sections whose sources do not permit redistribution are listed as withheld.

GET /api/v1/vessels/9318175
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using this data in code?

Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro adds internal business use; API plans add building the data into your own products.

See plans