Skip to content

ZIM BALTIMORE

Cargo ship · Liberia · built 2010 · AIS Class A

IMO9395953MMSI636018471Call signA8UE8Last AIS position Sep 30, 2026, 22:42 UTC

In short

ZIM BALTIMORE (Cargo ship, Liberia flag) was last seen on AIS on , under way at 16.2 kn, near El Bosque (Caribbean Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is KINGSTON,JM; its reported draught is 10.9 m (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 22:17 UTC).

Current voyage: from El Bosque (departed Sep 30, 2026, 21:02 UTC) to KINGSTON,JM

Vessel type
Cargo ship
Year built
2010
Gross tonnage
40,741
Size (length × beam)
259 m × 32 m
Registered owner
—

Watch this ship

ZIM BALTIMORE has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

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

Last reported position

received
Position
10.4778° N, 75.7346° W
Area
Caribbean Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
16.2 kn
Course
357°
Heading
358°
10.4778° N, 75.7346° W
Open the full live map →

Last 30 days: 1 port call (El Bosque).

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
ZIM BALTIMORE
IMO numberWhat is an IMO number?
9395953
MMSIWhat is an MMSI?
636018471
Call signWhat is a call sign?
A8UE8
Vessel type
Cargo ship
AIS ship type
Cargo (hazardous cat. A)
Gross tonnageGross tonnage vs deadweight
40,741
Length overall
259 m
Beam
32 m
Year built
2010

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.

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
Left El BosqueAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at El BosqueAIS-detectedVoydar port-call detector (AIS geofence)
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 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)

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.

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
El Bosque COEBQSep 30, 2026, 03:08 UTCSep 30, 2026, 21:02 UTC17 h 54 min

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 HKHKGArrivalMay 12, 2019, 14:48 UTCKC12Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Mar 24, 2019, 00:13 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Jan 31, 2019, 11:16 UTCTSKHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJan 7, 2019, 21:04 UTCELCHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Dec 7, 2018, 22:51 UTCTSKHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Nov 3, 2018, 18:15 UTCCCHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Oct 5, 2018, 04:59 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)May 17, 2018, 22:40 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Charleston USCHSDepartureSep 29, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVDepartureSep 29, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Charleston USCHSArrivalSep 29, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVArrivalSep 27, 2015(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: March 31, 2015.

Behaviour at sea Voydar-derived

Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.

WhenWhat we observedConfidence
Sep 30, 2026, 19:48 UTC
Draught change

Reported draught went from 12.3 m to 10.9 m while in port at El Bosque. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)

Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.

Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.

How these are computed →

Frequently asked questions

Where is ZIM BALTIMORE now?
ZIM BALTIMORE (Cargo ship, Liberia flag) was last seen on AIS on Sep 30, 2026, 22:42 UTC, under way at 16.2 kn, near El Bosque (Caribbean Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was KINGSTON,JM (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 22:17 UTC). This report does not confirm the ship’s current route.
What kind of ship is ZIM BALTIMORE?
ZIM BALTIMORE is a cargo ship sailing under the flag of Liberia, built in 2010 by HHIC Phil. The vessel is 259 m long with a beam of 32 m and has a gross tonnage of 40,741.
What sanctions and inspection records does Voydar hold for ZIM BALTIMORE?
Voydar has no matched sanctions record displayed for ZIM BALTIMORE 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 ZIM BALTIMORE. 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/9395953
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