MSC MANDY III
Container ship · Panama · built 1993 · AIS Class A
In short
MSC MANDY III (Container ship, Panama flag) was last seen on AIS on , under way at 17.1 kn, in the Baltic Sea. Its crew-entered AIS destination is RULED>LTKLJ, with an ETA of Oct 4, 2026, 03:30 UTC; its reported draught is 10.1 m (voyage report via Digitraffic marine AIS, received Oct 3, 2026, 18:15 UTC). ISM manager: MSC Shipmanagement Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- Container ship
- Flag
- Panama
- Year built
- 1993
- Gross tonnage
- —
- Size (length × beam)
- 237 m
- ISM manager
- MSC Shipmanagement Ltd
Watch this ship
Get an email when MSC MANDY III arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
We email you a link and a code. That creates a free account, no password or card, and follows MSC MANDY III.
Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.
By continuing you accept the Terms and the Privacy policy.
Last reported position
received- Position
- 56.9621° N, 20.5544° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 17.1 kn
- Course
- 184°
- Heading
- 185°
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)
Try the live demo, no sign-upIdentity & particulars
- Name
- MSC MANDY III
- IMO numberWhat is an IMO number?
- 8918966
- MMSIWhat is an MMSI?
- 354537000
- Call signWhat is a call sign?
- HPRL
- Flag
- Panama
- Vessel type
- Container ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 237 m
- Beam
- —
- Year built
- 1993
PanamaA 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 years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 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.
| Date | Event | Source |
|---|---|---|
| Reported arrival at GdyniaAuthority-reported | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) | |
| Reported departure from New YorkAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at New YorkAuthority-reported | USACE foreign traffic vessel entrances & clearances |
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 |
|---|---|---|---|---|
| 2018 | 32,546 t | 10,334 t | 196 days | 489 kg |
| 2019 | 31,670 t | 10,074 t | 240 days | 420 kg |
| 2020 | 31,191 t | 9,887 t | 213 days | 419 kg |
| 2021 | 31,610 t | 10,013 t | 198 days | 454 kg |
| 2022 | 31,717 t | 10,048 t | 226 days | 435 kg |
| 2023 | 16,033 t | 5,073 t | 110 days | 442 kg |
| 2024 | 28,931 t | 9,252 t | 217 days | 423 kg |
| 2025 | 18,899 t | 6,035 t | 119 days | 513 kg |
Technical efficiency: EEXI (13.24 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Gdynia PLGDY | Arrival | Sep 24, 2026, 19:15 UTC | Helskie I | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) |
| New York USNYC | Departure | May 7, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | May 7, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Departure | May 5, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Arrival | May 5, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Departure | May 4, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Arrival | May 3, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Departure | Apr 30, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | Apr 30, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Boston USBOS | Departure | Apr 28, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Boston USBOS | Arrival | Apr 28, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Departure | Apr 2, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: January 4, 2002.
Source: Urząd Morski w Gdyni (www.umgdy.gov.pl); processed by Seadar (times converted to UTC, IMO checksum-validated). The retrieval date is shown with the data. Licence: Polish PSI reuse (ustawa o otwartych danych), conditions: cite source, date, processing.
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 MSC MANDY III now?
- MSC MANDY III (Container ship, Panama flag) was last seen on AIS on Oct 3, 2026, 22:42 UTC, under way at 17.1 kn, in the Baltic Sea. The crew-entered destination was RULED>LTKLJ (voyage report via Digitraffic marine AIS, received Oct 3, 2026, 18:15 UTC). This report does not confirm the ship’s current route.
- What kind of ship is MSC MANDY III?
- MSC MANDY III is a container ship sailing under the flag of Panama, built in 1993 by Bremer Vulkan. The vessel is 237 m long.
- Who is recorded as the owner or manager of MSC MANDY III?
- MSC Shipmanagement Ltd is recorded as ISM manager for MSC MANDY III (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for MSC MANDY III?
- Voydar has no matched sanctions record displayed for MSC MANDY 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 MANDY III. Missing records do not establish whether the ship has been detained.
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/8918966Using 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.