GMT Astro
Car carrier · Panama · built 1987 · AIS Class A
In short
GMT Astro (Car carrier, Panama flag) was last seen on AIS on , under way at 14.7 kn, in the port of Keppel. Its crew-entered AIS destination is EGSCN, with an ETA of Dec 6, 2026, 22:00 UTC; its reported draught is 8.9 m (voyage report via AISstream.io global terrestrial AIS, received Nov 21, 2026, 01:47 UTC). It arrived there on Nov 19, 2026, 22:51 UTC. ISM manager: DORIKO Limited (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).
- Vessel type
- Car carrier
- Flag
- Panama
- Year built
- 1987
- Gross tonnage
- 48,017
- Size (length × beam)
- 191 m × 32 m
- ISM manager
- DORIKO Limited
Last reported position: 1.4647° N, 103.1628° E · Strait of Malacca · See on the map
Shipping a car on this vessel?
Follow GMT Astro and Voydar's daily email tells you when it has arrived in port, left again, or changed its destination.
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 21, 2026, 06:44 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for GMT Astro 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: the Voydar app
Last reported position
received- Position
- 1.4647° N, 103.1628° E
- Area
- Strait of Malacca
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 14.7 kn
- Course
- 309°
- Heading
- 311°
- Compass: course over ground 309°, heading 311°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 2 port calls (Keppel and Incheon).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows GMT Astro's track before the last 30 days. Voydar has recorded its port calls since September 1, 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 190.5 mone tick every 25 m
Beam 32.3 mPlan outline, to scale
- Name
- GMT Astro
- IMO numberWhat is an IMO number?
- 8606056
- MMSIWhat is an MMSI?
- 373817000
- Call signWhat is a call sign?
- 3FKQ7
- Flag
- Panama
- Gross tonnageGross tonnage vs deadweight
- 48,017
- Deadweight (DWT)
- Source: Wikidata, record Q84253424. Added to Voydar on October 23, 2026. Licence: CC0 1.0.16,141 t
- Length overall
- 190.5 m
- Beam
- 32.3 m
- Year built
- 1987
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 2024 · reported · high confidence · retrieved Nov 16, 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 |
|---|---|---|
| Arrived at KeppelAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left IncheonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at IncheonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left IncheonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at IncheonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from San DiegoAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at San DiegoAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from San DiegoAuthority-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.
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 Sep 14, 2012衝突 · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)東京湾浦賀水道 千葉県富津市所在の第2海堡灯台から真方位191°1.1海里付近
自動車専用船OVERSEAS JOYCE貨物船SEIYO GLORY衝突Report published Jun 27, 2014
A船は、船長Aほか24人(フィリピン共和国籍21人、ロシア連邦籍3人)が乗り組み、車両3,334ユニットを積載し、船首約8.1m船尾約8.1mの喫水により、平成24年9月14日18時20分ごろ京浜港横浜第3区大黒ふ頭で水先人が乗船し、大韓民国平沢港に向かう予定で18時45分ごろ岸壁を離れ、水先人が水先をして浦賀水道航路に向かった。 水先人は、左舷船首約11°にB船を、左舷船首約44°に大型タンカーをそれぞれ視認しており、19時42分ごろ浦賀水道航路中央第6号灯浮標に並び、約12.5ノット(kn)の速力(対地速力、以下同じ。)で浦賀水道航路に入り、南東進した。 A船は、船長Aがレーダー見張りなどに、一等航海士Aが見張りに、三等航海士Aがテレグラフの操作に、操舵手Aが手動操舵にそれぞれ就き、水先人が、船橋中央のレピーター前で操船を行い、右舷船首方の水域が空き、約800mの距離になったB船の右舷
Source: 運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports). 出典:運輸安全委員会「船舶事故等調査報告書」(https://jtsb.mlit.go.jp/)。Seadar が項目を抽出・加工して作成 (Source: Japan Transport Safety Board marine accident reports; fields extracted and edited by Seadar). Licence: Public Data License 1.0 (公共データ利用規約 第1.0版, PDL1.0; compatible with CC BY 4.0).
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 | 2,841 t | 900 t | 34 days | 275 kg |
| 2023 | 2,817 t | 892 t | 36 days | 237 kg |
| 2024 | 446 t | 142 t | 6 days | 249 kg |
Technical efficiency: EIV (20.02 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 2024 sits among the ships EU MRV lists as “Vehicle carrier”. Lower is less CO₂.
- CO₂ per tonne of cargo carried one nautical mile158.32 g per tonne-nautical mile
- Lowest reportedHighest reported
89% of the 340 ships in this group reported a lower figure.
Group: lower quartile 43.93 · median 55.37 · upper quartile 79.73
- CO₂ per nautical mile sailed249.5 kg per nautical mile
- Lowest reportedHighest reported
11% of the 465 ships in this group reported a lower figure.
Group: lower quartile 291.8 · median 320.2 · upper quartile 343.2
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 |
|---|---|---|---|
| Keppel SGKEP | Nov 19, 2026, 22:51 UTC | in port | — |
| Incheon KRINC | Nov 8, 2026, 18:14 UTC | Nov 19, 2026, 18:53 UTC | 11 d 0 h |
| Incheon KRINC | Sep 1, 2026, 22:57 UTC | Sep 15, 2026, 23:28 UTC | 14 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 |
|---|---|---|---|---|
| San Diego USSAN | Departure | Sep 16, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Diego USSAN | Arrival | Sep 16, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Diego USSAN | Departure | May 4, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Diego USSAN | Arrival | May 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Hueneme USNTD | Departure | Apr 28, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Hueneme USNTD | Arrival | Apr 28, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Mar 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Arrival | Feb 28, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Hueneme USNTD | Arrival | Feb 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Hueneme USNTD | Departure | Feb 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Diego USSAN | Departure | Feb 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Diego USSAN | Arrival | Feb 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: February 8, 2002.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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 |
|---|---|---|
| Nov 11, 2026, 06:53 UTC | Draught change Reported draught went from 7.2 m to 9 m while in port at Incheon. 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
- What kind of ship is GMT Astro?
- GMT Astro is a car carrier sailing under the flag of Panama, built in 1987. The vessel is 190.5 m long with a beam of 32.3 m and has a gross tonnage of 48,017.
- Who is recorded as the owner or manager of GMT Astro?
- DORIKO Limited is recorded as ISM manager for GMT Astro (source: EU MRV (THETIS-MRV) emissions; reporting year 2024). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for GMT Astro?
- Voydar has no matched sanctions record displayed for GMT Astro 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 GMT Astro. 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
More Car carriers
Other car carriers with full Voydar profiles. A different set each day. All car carriers
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/8606056Cite this page
GMT Astro. Voydar (voydar.com). https://www.voydar.com/vessel/8606056-gmt-astro. Retrieved November 21, 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 includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.