PSA ACHIEVE
Tug · Singapore · AIS Class A
In short
PSA ACHIEVE (Tug, Singapore flag) was last seen on AIS on , near Pulau Bukom (Strait of Malacca). Its crew-entered AIS destination is SGP (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 05:04 UTC). Its last detected port call was at Pasir Panjang: arrived Jul 2, 2026, left Jul 2, 2026.
Watch this ship
Get an email when PSA ACHIEVE 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 PSA ACHIEVE.
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.2559° N, 103.7902° E
- Area
- Strait of Malacca
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0.5 kn
- Course
- 331°
- Heading
- 288°
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
- PSA ACHIEVE
- IMO numberWhat is an IMO number?
- 1014797
- MMSIWhat is an MMSI?
- 563085720
- Call signWhat is a call sign?
- 9VEH6
- Flag
- Singapore
- Vessel type
- Tug
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
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 Pasir PanjangAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Pasir PanjangAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Pasir PanjangAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Pasir PanjangAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Pasir PanjangAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Pasir PanjangAIS-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) |
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 |
|---|---|---|---|
| Pasir Panjang SGPAP | Jul 2, 2026, 18:21 UTC | Jul 2, 2026, 19:20 UTC | 59 min |
| Pasir Panjang SGPAP | Jun 16, 2026, 09:40 UTC | Jun 16, 2026, 10:20 UTC | 40 min |
| Pasir Panjang SGPAP | Jun 16, 2026, 08:24 UTC | Jun 16, 2026, 09:10 UTC | 47 min |
| Pasir Panjang SGPAP | Jun 16, 2026, 03:29 UTC | Jun 16, 2026, 05:10 UTC | 1 h 41 min |
| Pasir Panjang SGPAP | Jun 15, 2026, 14:29 UTC | Jun 15, 2026, 15:10 UTC | 41 min |
| Pasir Panjang SGPAP | Jun 15, 2026, 08:21 UTC | Jun 15, 2026, 09:05 UTC | 44 min |
| PASIR PANJANG Terminal SGPPT | Jun 15, 2026, 00:57 UTC | Jun 15, 2026, 06:25 UTC | 5 h 27 min |
| PASIR PANJANG Terminal SGPPT | Jun 14, 2026, 20:32 UTC | Jun 15, 2026, 00:51 UTC | 4 h 19 min |
| Pasir Panjang SGPAP | Jun 14, 2026, 10:29 UTC | Jun 14, 2026, 11:54 UTC | 1 h 25 min |
| Pasir Panjang SGPAP | Jun 13, 2026, 22:42 UTC | Jun 13, 2026, 23:16 UTC | 34 min |
| Tanjong Penjuru SGTPN | Jun 13, 2026, 09:35 UTC | Jun 13, 2026, 16:27 UTC | 6 h 52 min |
| PASIR PANJANG Terminal SGPPT | Jun 13, 2026, 07:54 UTC | Jun 13, 2026, 09:35 UTC | 1 h 42 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 | Apr 15, 2025, 04:14 UTC | WA1 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
Records published by the authority named on each row. Earliest record for this ship: April 15, 2025.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Frequently asked questions
- Where is PSA ACHIEVE now?
- PSA ACHIEVE (Tug, Singapore flag) was last seen on AIS on Oct 4, 2026, 05:52 UTC, near Pulau Bukom (Strait of Malacca). The crew-entered destination was SGP (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 05:04 UTC). This report does not confirm the ship’s current route.
- What kind of ship is PSA ACHIEVE?
- PSA ACHIEVE is a tug sailing under the flag of Singapore.
- What sanctions and inspection records does Voydar hold for PSA ACHIEVE?
- Voydar has no matched sanctions record displayed for PSA ACHIEVE 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 PSA ACHIEVE. 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/1014797Using 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.