Progress Ace
Car carrier · Panama · built 2003 · AIS Class A
In short
Progress Ace (Car carrier, Panama flag) was last seen on AIS on , moored, in the port of Durban. Its crew-entered AIS destination is TZ DAR (Dar es Salaam), with an ETA of Nov 23, 2026, 01:00 UTC; its reported draught is 8.6 m (voyage report via Voydar Beacon contributor stations, received Nov 18, 2026, 18:29 UTC). It arrived there on Nov 17, 2026, 22:01 UTC. ISM manager: MMS CO., LTD. (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).
- Vessel type
- Car carrier
- Flag
- Panama
- Year built
- 2003
- Gross tonnage
- 57,789
- Size (length × beam)
- 199 m × 32 m
- ISM manager
- MMS CO., LTD.
Last reported position: 29.863° S, 31.032° E · Indian Ocean · See on the map
Shipping a car on this vessel?
Follow Progress Ace and Voydar's daily email tells you when it has reached Dar es Salaam, and when it leaves or changes its destination.
What you would have been told
Following Progress Ace over the last 24 hours would have sent 1 message.
- ArrivedDurban
Detected from AIS, as of Nov 18, 2026, 18:40 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Progress Ace 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
- 29.863° S, 31.032° E
- Area
- Indian Ocean
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 233°
- Heading
- 315°
- Compass: course over ground 233°, heading 315°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 1 port call (Durban).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Progress Ace's track before the last 30 days. Voydar has recorded its port calls since July 30, 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 199 mone tick every 25 m
Beam 32 mPlan outline, to scale
- Name
- Progress Ace
- IMO numberWhat is an IMO number?
- 9267687
- MMSIWhat is an MMSI?
- 353514000
- Call signWhat is a call sign?
- HPQI
- Flag
- Panama
- Vessel type
- Car carrier
- Gross tonnageGross tonnage vs deadweight
- 57,789
- Deadweight (DWT)
- Source: Wikidata, record Q117024166. Added to Voydar on October 23, 2026. Licence: CC0 1.0.19,512 t
- Length overall
- 199 m
- Beam
- 32 m
- Year built
- 2003
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
- 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 |
|---|---|---|
| Arrived at DurbanAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left KawasakiAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KawasakiAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left KisarazuAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KisarazuAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at PortlandAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from PortlandAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at RichmondAuthority-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 | 5,418 t | 1,738 t | 51 days | 258 kg |
| 2019 | 9,618 t | 3,070 t | 91 days | 285 kg |
| 2020 | 7,222 t | 2,284 t | 64 days | 321 kg |
| 2021 | 7,954 t | 2,517 t | 78 days | 294 kg |
| 2023 | 6,180 t | 1,974 t | 46 days | 329 kg |
| 2024 | 9,905 t | 3,173 t | 80 days | 312 kg |
Technical efficiency: EEXI (14.7 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 mile53.4 g per tonne-nautical mile
- Lowest reportedHighest reported
47% 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 sailed312.2 kg per nautical mile
- Lowest reportedHighest reported
43% 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 |
|---|---|---|---|
| Durban ZADUR | Nov 17, 2026, 22:01 UTC | in port | — |
| Kawasaki JPKWS | Oct 17, 2026, 09:53 UTC | Oct 18, 2026, 06:23 UTC | 20 h 30 min |
| Kisarazu JPKZU | Oct 16, 2026, 22:40 UTC | Oct 17, 2026, 08:26 UTC | 9 h 46 min |
| Suva FJSUV | Sep 28, 2026, 18:36 UTC | Sep 30, 2026, 09:43 UTC | 39 h 7 min |
| Wellington NZWLG | Sep 21, 2026, 08:19 UTC | Sep 21, 2026, 20:19 UTC | 12 h 0 min |
| Auckland NZAKL | Sep 17, 2026, 18:09 UTC | Sep 19, 2026, 11:34 UTC | 41 h 25 min |
| Kisarazu JPKZU | Aug 28, 2026, 23:22 UTC | Aug 30, 2026, 13:25 UTC | 38 h 3 min |
| Kawasaki JPKWS | Aug 27, 2026, 05:04 UTC | Aug 28, 2026, 10:13 UTC | 29 h 9 min |
| Port Melbourne AUPOR | Jul 30, 2026, 12:30 UTC | Aug 1, 2026, 07:17 UTC | 42 h 46 min |
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 |
|---|---|---|---|---|
| Portland USPDX | Arrival | Jun 25, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Jun 25, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Richmond USRCH | Arrival | Jun 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Richmond USRCH | Departure | Jun 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Hueneme USNTD | Arrival | Jun 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Hueneme USNTD | Departure | Jun 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Diego USSAN | Arrival | Jun 21, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Diego USSAN | Departure | Jun 21, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Jun 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Jun 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| TURTLE RIVER, GA (INCLUDED IN BRUNSWICK HARBOR, GA) | Departure | Jun 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| TURTLE RIVER, GA (INCLUDED IN BRUNSWICK HARBOR, GA) | Arrival | Jun 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: April 3, 2004.
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 |
|---|---|---|
| Oct 18, 2026, 04:21 UTC | Draught change Reported draught went from 8 m to 8.5 m while in port at Kawasaki. 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 Progress Ace?
- Progress Ace is a car carrier sailing under the flag of Panama, built in 2003 by Shinkurushima Toyohashi Shipbuilding. The vessel is 199 m long with a beam of 32 m and has a gross tonnage of 57,789.
- Who is recorded as the owner or manager of Progress Ace?
- MMS CO., LTD. is recorded as ISM manager for Progress Ace (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 Progress Ace?
- Voydar has no matched sanctions record displayed for Progress Ace 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 Progress Ace. 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/9267687Cite this page
Progress Ace. Voydar (voydar.com). https://www.voydar.com/vessel/9267687-progress-ace. Retrieved November 18, 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.