ERASMUS CHIEF
Cargo ship · Panama · built 2009 · AIS Class A
In short
ERASMUS CHIEF (Cargo ship, Panama flag) was last seen on AIS on , under way at 11 kn, near Pulau Sebarok (Strait of Malacca). Its last detected port call was at Jakarta, Java: arrived Sep 30, 2026, left Oct 2, 2026.
- Vessel type
- Cargo ship
- Flag
- Panama
- Year built
- 2009
- Gross tonnage
- 17,068
- Size (length × beam)
- 180 m × 25 m
- Registered owner
- —
Watch this ship
Get an email when ERASMUS CHIEF 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 ERASMUS CHIEF.
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
- 1.1684° N, 103.7869° E
- Area
- Strait of Malacca
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 11 kn
- Course
- 252°
- Heading
- 249°
Last 30 days: 1 port call (Jakarta, Java).
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
- ERASMUS CHIEF
- IMO numberWhat is an IMO number?
- 9449857
- MMSIWhat is an MMSI?
- 352004606
- Call signWhat is a call sign?
- 3E6889
- Flag
- Panama
- Vessel type
- Cargo ship
- AIS ship type
- Cargo (hazardous cat. D)
- Gross tonnageGross tonnage vs deadweight
- 17,068
- Deadweight (DWT)
- Source: Wikidata, record Q84261726. Added to Voydar on September 23, 2026. Licence: CC0 1.0.21,192 t
- Length overall
- 180.4 m
- Beam
- 25.3 m
- Year built
- 2009
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.
No owner, operator or manager is recorded for this vessel yet.
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 Jakarta, JavaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Jakarta, JavaAIS-detected | Voydar port-call detector (AIS geofence) | |
| 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) | |
| 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.
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 |
|---|---|---|---|
| Jakarta, Java IDJKT | Sep 30, 2026, 23:28 UTC | Oct 2, 2026, 21:56 UTC | 46 h 28 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 |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | May 29, 2025, 19:52 UTC | SWLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Feb 7, 2025, 08:16 UTC | KC3 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jan 31, 2025, 03:02 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jan 25, 2025, 07:20 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jan 17, 2025, 06:06 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jan 11, 2025, 09:37 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jan 2, 2025, 19:31 UTC | KC17 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 21, 2024, 17:46 UTC | KC18 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 15, 2024, 18:50 UTC | KC6 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Nov 30, 2024, 09:20 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Oct 17, 2024, 11:30 UTC | YLD | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
Records published by the authority named on each row. Earliest record for this ship: October 17, 2024.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
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 1, 2026, 12:00 UTC | Draught change Reported draught went from 8.9 m to 9.6 m while in port at Jakarta, Java. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 30, 2026, 23:32 UTC | Draught change Reported draught went from 8.1 m to 8.9 m while in port at Jakarta, Java. 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
- Where is ERASMUS CHIEF now?
- ERASMUS CHIEF (Cargo ship, Panama flag) was last seen on AIS on Oct 3, 2026, 17:13 UTC, under way at 11 kn, near Pulau Sebarok (Strait of Malacca).
- What kind of ship is ERASMUS CHIEF?
- ERASMUS CHIEF is a cargo ship sailing under the flag of Panama, built in 2009. The vessel is 180.4 m long with a beam of 25.3 m and has a gross tonnage of 17,068.
- What sanctions and inspection records does Voydar hold for ERASMUS CHIEF?
- Voydar has no matched sanctions record displayed for ERASMUS CHIEF 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 ERASMUS CHIEF. Missing records do not establish whether the ship has been detained.
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/9449857Using 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.