MSC ZONDA III
Container ship · Portugal · built 2008 · AIS Class A
In short
MSC ZONDA III (Container ship, Portugal flag) was last seen on AIS on , under way at 10.9 kn, in the English Channel. Its crew-entered AIS destination is FRLEH (Le Havre), with an ETA of Oct 6, 2026, 17:00 UTC; its reported draught is 12 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 14:30 UTC). ISM manager: MSC Shipmanagement Ltd (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
Current voyage: from Doel (departed Oct 5, 2026, 13:00 UTC) to FRLEH (Le Havre)
- Vessel type
- Container ship
- Flag
- Portugal
- Year built
- 2008
- Gross tonnage
- 36,007
- Size (length × beam)
- 231 m × 32 m
- ISM manager
- MSC Shipmanagement Ltd
Watch this ship
Get an email when MSC ZONDA III reaches Le Havre, and when it 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.

Last reported position
received- Position
- 49.68° N, 0.3085° W
- Area
- English Channel
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 10.9 kn
- Course
- 181°
- Heading
- 184°
Last 30 days: 5 port calls (Doel, Le Havre, Greenock, Saltcoats, and Liverpool).
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
- MSC ZONDA III
- IMO numberWhat is an IMO number?
- 9436472
- MMSIWhat is an MMSI?
- 255802470
- Call signWhat is a call sign?
- CQOZ
- Flag
- Portugal
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 36,007
- Deadweight (DWT)
- Source: Wikidata, record Q84261711. Added to Voydar on September 23, 2026. Licence: CC0 1.0.41,973 t
- Length overall
- 231 m
- Beam
- 32.3 m
- Year built
- 2008
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.
- Operator
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Oct 5, 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 |
|---|---|---|
| Left DoelAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at DoelAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Le HavreAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Le HavreAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left GreenockAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at GreenockAIS-detected | Voydar port-call detector (AIS geofence) | |
| 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.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2025 | 5,358 t | 1,712 t | 30 days | 536 kg |
Technical efficiency: EEXI (11.73 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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Doel BEDEL | Oct 4, 2026, 06:25 UTC | Oct 5, 2026, 13:00 UTC | 30 h 35 min |
| Le Havre FRLEH | Oct 2, 2026, 12:35 UTC | Oct 3, 2026, 02:15 UTC | 13 h 40 min |
| Greenock GBGRK | Sep 28, 2026, 20:30 UTC | Sep 30, 2026, 17:57 UTC | 45 h 27 min |
| Saltcoats GBSLC | Sep 28, 2026, 00:16 UTC | Sep 28, 2026, 01:06 UTC | 51 min |
| Liverpool GBLIV | Sep 23, 2026, 21:16 UTC | Sep 25, 2026, 21:30 UTC | 2 d 0 h |
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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival(matched by call sign) | May 21, 2025, 22:31 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Mar 8, 2025, 02:30 UTC | NLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 16, 2024, 20:30 UTC | KC2 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Oct 7, 2024, 10:30 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Sep 3, 2023, 12:03 UTC | WA3 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Aug 27, 2023, 21:25 UTC | KC2 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jul 9, 2023, 14:21 UTC | KC18 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Aug 20, 2020, 19:44 UTC | KC1 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Aug 9, 2020, 08:07 UTC | WA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Nov 23, 2018, 16:37 UTC | KC18 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jun 29, 2018, 14:18 UTC | KC19 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jun 1, 2018, 23:37 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
Records published by the authority named on each row. Earliest record for this ship: November 1, 2010.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
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.
| When | What we observed | Confidence |
|---|---|---|
| Oct 5, 2026, 11:54 UTC | Draught change Reported draught went from 9.2 m to 12 m while in port at Doel. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
| Sep 30, 2026, 16:25 UTC | Draught change Reported draught went from 9 m to 9.8 m while in port at Greenock. Voydar infers the ship probably loaded 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.
Frequently asked questions
- Where is MSC ZONDA III now?
- MSC ZONDA III (Container ship, Portugal flag) was last seen on AIS on Oct 6, 2026, 14:54 UTC, under way at 10.9 kn, in the English Channel. The crew-entered destination was FRLEH (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 14:30 UTC). This report does not confirm the ship’s current route.
- What kind of ship is MSC ZONDA III?
- MSC ZONDA III is a container ship sailing under the flag of Portugal, built in 2008. The vessel is 231 m long with a beam of 32.3 m and has a gross tonnage of 36,007.
- Who is recorded as the owner or manager of MSC ZONDA III?
- MSC Shipmanagement Ltd is recorded as ISM manager for MSC ZONDA III (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 ZONDA III?
- Voydar has no matched sanctions record displayed for MSC ZONDA III 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 ZONDA III. 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/9436472Using 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.