GINGA MAYA
Chemical tanker · Singapore · built 2005 · AIS Class A
In short
GINGA MAYA (Chemical tanker, Singapore flag) was last seen on AIS on , under way at 12.3 kn, near Daesan/Seosan (Yellow Sea). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its last detected port call was at Chiba: arrived Nov 2, 2026, left Nov 3, 2026. ISM manager: Unix Line Pte Ltd (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
- Vessel type
- Chemical tanker
- Flag
- Singapore
- Year built
- 2005
- Gross tonnage
- 11,690
- Size (length × beam)
- 144 m × 25 m
- ISM manager
- Unix Line Pte Ltd
Last reported position: 37.1092° N, 126.3413° E · Yellow Sea · See on the map
Watch this ship
GINGA MAYA has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 16, 2026, 14:56 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for GINGA MAYA reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: Voydar for iPhone
Last reported position
received- Position
- 37.1092° N, 126.3413° E
- Area
- Yellow Sea
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 12.3 kn
- Course
- 216°
- Heading
- 215°
- Compass: course over ground 216°, heading 215°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 1 port call (Chiba).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows GINGA MAYA's track before the last 30 days. Voydar has recorded its port calls since June 9, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 144.1 mone tick every 25 m
Beam 25 mPlan outline, to scale
- Name
- GINGA MAYA
- IMO numberWhat is an IMO number?
- 9339351
- MMSIWhat is an MMSI?
- 563326400
- Call signWhat is a call sign?
- S6US5
- Flag
- Singapore
- AIS ship type
- Tanker (hazardous cat. B)
- Gross tonnageGross tonnage vs deadweight
- 11,690
- Length overall
- 144.1 m
- Beam
- 25 m
- 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.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · high confidence · retrieved Nov 16, 2026
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
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 ChibaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ChibaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left HoustonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HoustonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from PORT OF SOUTH LOUISIANA (LA)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at PORT OF SOUTH LOUISIANA (LA)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from Texas CityAuthority-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 |
|---|---|---|---|---|
| 2019 | 2,219 t | 708 t | 39 days | 204 kg |
| 2020 | 7,812 t | 2,469 t | 139 days | 203 kg |
| 2022 | 3,486 t | 1,109 t | 69 days | 207 kg |
| 2025 | 1,691 t | 535 t | 31 days | 253 kg |
Technical efficiency: EIV (11.27 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
Compared with ships of its type
Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “Chemical tanker”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile17.83 g per tonne-nautical mile
- Lowest reportedHighest reported
59% of the 1,489 ships in this group reported a lower figure.
Group: lower quartile 10.24 · median 15.04 · upper quartile 25.97
- CO₂ per nautical mile sailed253 kg per nautical mile
- Lowest reportedHighest reported
52% of the 1,516 ships in this group reported a lower figure.
Group: lower quartile 203.4 · median 250.2 · upper quartile 301
Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated
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 |
|---|---|---|---|
| Chiba JPCHB | Nov 2, 2026, 00:37 UTC | Nov 3, 2026, 00:06 UTC | 23 h 28 min |
| Houston USHOU | Jun 9, 2026, 01:16 UTC | Jun 13, 2026, 10:33 UTC | 4 d 9 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 |
|---|---|---|---|---|
| PORT OF SOUTH LOUISIANA (LA) | Departure | Dec 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Arrival | Dec 4, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Texas City USTXT | Departure | Dec 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Nov 25, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PASCAGOULA HARBOR, MS | Departure | Nov 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PASCAGOULA HARBOR, MS | Arrival | Nov 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Departure | Oct 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Arthur USPOA | Arrival | Oct 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Freeport USFPO | Arrival | Oct 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Freeport USFPO | Departure | Oct 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Oct 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Sep 28, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: November 3, 2005.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- What kind of ship is GINGA MAYA?
- GINGA MAYA is a chemical tanker sailing under the flag of Singapore, built in 2005 by Fukuoka Shipbuilding. The vessel is 144.1 m long with a beam of 25 m and has a gross tonnage of 11,690.
- Who is recorded as the owner or manager of GINGA MAYA?
- Unix Line Pte Ltd is recorded as ISM manager for GINGA MAYA (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 GINGA MAYA?
- Voydar has no matched sanctions record displayed for GINGA MAYA 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 GINGA MAYA. Missing records do not establish whether the ship has been detained.
Full Vessel Report
A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.
Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.
Every fact on this page stays free.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
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/9339351Cite this page
GINGA MAYA. Voydar (voydar.com). https://www.voydar.com/vessel/9339351-ginga-maya. Retrieved November 16, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
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.