CMA CGM SHANGHAI
Container ship · Malta · built 2005 · AIS Class A
In short
CMA CGM SHANGHAI (Container ship, Malta flag) was last seen on AIS on , under way at 14.8 kn, in the East China Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- Vessel type
- Container ship
- Flag
- Malta
- Year built
- 2005
- Gross tonnage
- 82,794
- Size (length × beam)
- 300 m
- Registered owner
- —
Watch this ship
CMA CGM SHANGHAI 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
- 26.2198° N, 120.9938° E
- Area
- East China Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 14.8 kn
- Course
- 31°
- Heading
- 28°
Voydar detected no port call in the last 30 days.
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-upIdentity & particulars
- Name
- CMA CGM SHANGHAI
- IMO numberWhat is an IMO number?
- 9295220
- MMSIWhat is an MMSI?
- 256995000
- Call signWhat is a call sign?
- 9HA6056
- Flag
- Malta
- Vessel type
- Container ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 82,794
- Length overall
- 300 m
- Beam
- —
- Year built
- 2005
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.
| Date | Event | Source |
|---|---|---|
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong 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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred Feb 6, 2024Cargo, GeneralNTSB marine investigations (CAROL)Oakland, CA, USA
President Eisenhower, Oakland, CA, USA (NTSB DCA24FM023)Report published Feb 25, 2025
The National Transportation Safety Board determines that the probable cause of the container loss aboard the containership President Eisenhower was the input of incorrect cargo weight for 39 containers when the cargo loading plan was developed by shoreside planners, resulting in the containers being loaded in overweight and reverse-stratified stacks, causing cargo-securing equipment to fail while
- Occurred Apr 28, 2021ACC · Cargo, GeneralNTSB marine investigations (CAROL)Santa Barbara, CA, USA
President Eisenhower, Santa Barbara, CA, USA (NTSB DCA21FM026)Report published May 24, 2022
The National Transportation Safety Board determines that the probable cause of the engine room fire aboard the containership President Eisenhower was a crewmember insufficiently swaging a compression fitting ferrule during the installation of fuel oil return tubing for a main engine’s cylinder, allowing an end of the tubing to disconnect and spray fuel oil onto a nearby unshielded and uninsulated
Source: NTSB marine investigations (CAROL). Courtesy: National Transportation Safety Board. Licence: US Government work (17 U.S.C. §105), public domain.
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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival(matched by call sign) | Apr 12, 2026, 06:05 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Feb 17, 2026, 03:15 UTC | LCS1 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Nov 3, 2025, 23:45 UTC | MB | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Apr 18, 2025, 09:36 UTC | LCS1 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Feb 7, 2025, 20:29 UTC | LCS1 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Oakland USOAK | Arrival | Aug 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | Aug 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Aug 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Aug 4, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | May 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | May 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | May 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: January 4, 2006.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is CMA CGM SHANGHAI now?
- CMA CGM SHANGHAI (Container ship, Malta flag) was last seen on AIS on Oct 1, 2026, 07:08 UTC, under way at 14.8 kn, in the East China Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- What kind of ship is CMA CGM SHANGHAI?
- CMA CGM SHANGHAI is a container ship sailing under the flag of Malta, built in 2005 by HD Hyundai Heavy Industries. The vessel is 300 m long and has a gross tonnage of 82,794.
- What sanctions and inspection records does Voydar hold for CMA CGM SHANGHAI?
- Voydar has no matched sanctions record displayed for CMA CGM SHANGHAI 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 CMA CGM SHANGHAI. 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/9295220Using 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.