MYNY
Container ship · Liberia · built 2002 · AIS Class A
In short
MYNY (Container ship, Liberia flag) was last seen on AIS on , under way at 6.5 kn, in the Bay of Bengal. 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 INMAA (Chennai (ex Madras)); its reported draught is 14.2 m (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 17:27 UTC).
- Vessel type
- Container ship
- Flag
- Liberia
- Year built
- 2002
- Gross tonnage
- 75,201
- Size (length × beam)
- 300 m
- Registered owner
- —
Watch this ship
Get an email when MYNY 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 MYNY.
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
- 13.1229° N, 80.3248° E
- Area
- Bay of Bengal
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 6.5 kn
- Course
- 251°
- Heading
- 249°
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
- MYNY
- IMO numberWhat is an IMO number?
- 9229336
- MMSIWhat is an MMSI?
- 636019759
- Call signWhat is a call sign?
- D5WA4
- Flag
- Liberia
- Vessel type
- Container ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 75,201
- Length overall
- 299.8 m
- Beam
- —
- Year built
- 2002
LiberiaA 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 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 |
|---|---|---|---|---|
| 2021 | 12,151 t | 3,875 t | 41 days | 728 kg |
| 2022 | 29,509 t | 9,418 t | 115 days | 698 kg |
| 2023 | 10,079 t | 3,201 t | 45 days | 731 kg |
Technical efficiency: EEXI (11.61 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 |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Jun 16, 2026, 02:34 UTC | WA2 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Apr 11, 2026, 05:08 UTC | SOUTH EAST LAMMA ANCHORAGE | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Feb 3, 2026, 19:46 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Dec 2, 2025, 11:45 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Oct 5, 2025, 11:56 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Aug 6, 2025, 03:44 UTC | SWLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Oakland USOAK | Departure | Mar 31, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | Mar 31, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Mar 29, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Mar 26, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | Feb 17, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | Feb 17, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: November 17, 2002.
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 MYNY now?
- MYNY (Container ship, Liberia flag) was last seen on AIS on Sep 30, 2026, 17:38 UTC, under way at 6.5 kn, in the Bay of Bengal. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was INMAA (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 17:27 UTC). This report does not confirm the ship’s current route.
- What kind of ship is MYNY?
- MYNY is a container ship sailing under the flag of Liberia, built in 2002 by Samsung Heavy Industries. The vessel is 299.8 m long and has a gross tonnage of 75,201.
- What sanctions and inspection records does Voydar hold for MYNY?
- Voydar has no matched sanctions record displayed for MYNY 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 MYNY. Missing records do not establish whether the ship has been detained.
Sister ships
Likely sister ships: built by Samsung Heavy Industries, same type, gross tonnage within 2.5% and length within 1.5% of this ship's.
- MSC CATHERINE VIIMO 9229300Container ship · built 2001 · 75,201 GT
- GSL CHRISTENIMO 9229324Container ship · built 2002 · 75,201 GT
- GSL NICOLETTAIMO 9229348Container ship · built 2002 · 75,201 GT
- MSC LEO VIIMO 9229312Container ship · built 2002 · 75,201 GT
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/9229336Using 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.