APL Pusan
Container ship · Singapore · built 2002 · AIS Class A
In short
APL Pusan (Container ship, Singapore flag) was last seen on AIS on , under way at 10.4 kn, in the Java Sea. Its crew-entered AIS destination is CNNSA>>IDJKT, with an ETA of Oct 2, 2026, 14:00 UTC; its reported draught is 10.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 18:38 UTC).
- Vessel type
- Container ship
- Flag
- Singapore
- Year built
- 2002
- Gross tonnage
- 25,305
- Size (length × beam)
- 207 m × 30 m
- Registered owner
- —
Watch this ship
Get an email when APL Pusan 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 APL Pusan.
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
- 3.6581° S, 107.5038° E
- Area
- Java Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 10.4 kn
- Course
- 166°
- Heading
- 162°
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
- APL Pusan
- IMO numberWhat is an IMO number?
- 9234123
- MMSIWhat is an MMSI?
- 564619000
- Call signWhat is a call sign?
- S6HU5
- Flag
- Singapore
- Vessel type
- Container ship
- AIS ship type
- Cargo (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- 25,305
- Deadweight (DWT)
- Source: Wikidata, record Q84266014. Added to Voydar on September 23, 2026. Licence: CC0 1.0.34,122 t
- Length overall
- 207.4 m
- Beam
- 29.8 m
- Year built
- 2002
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.
- Operator
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026CMA CGM(not linked to a company record)Source: Wikidata · reported · confidence 0.6 · retrieved Jun 10, 2026
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
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 |
|---|---|---|
| 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.
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 Oct 15, 2019衝突 · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)神奈川県横須賀市横須賀港北東方沖の浦賀水道航路 第2海堡灯台から真方位317°1.3海里付近
コンテナ船APL PUSAN貨物船晶徳丸衝突Report published Mar 25, 2021
コンテナ船APL PUSANは、船長ほか22人が乗り組み、水先人の水先により京浜港横浜第2区に向け、また、貨物船晶徳丸は、船長及び航海士ほか2人が乗り組み、京浜港横浜区Y1錨地に向け、両船共に浦賀水道航路を北西進中、令和元年10月15日04時22分ごろ、同航路内において、両船が衝突し、その後、APL PUSANが灯浮標に衝突した。 APL PUSANは、左舷船首部外板の凹損等を生じ、晶徳丸は、船首部ブルワークの圧壊等を生じ、また、灯浮標は、防護枠の曲損等を生じたが、両船共に死傷者はいなかった。
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).
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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | May 24, 2025, 15:16 UTC | KC10 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | May 1, 2025, 07:34 UTC | KWAICHUNG CONTR. BERTH NO. 9 (TERMINAL 7) | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Apr 9, 2025, 13:06 UTC | KC6 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Mar 4, 2025, 21:38 UTC | KC7 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Feb 2, 2025, 06:56 UTC | KC12 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jan 3, 2025, 00:34 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 8, 2024, 16:16 UTC | KC9 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Nov 17, 2024, 07:05 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Oct 29, 2024, 18:26 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Oct 5, 2024, 18:38 UTC | WA2 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Sep 14, 2024, 15:42 UTC | KC10 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Aug 24, 2024, 16:33 UTC | KC7 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
Records published by the authority named on each row. Earliest record for this ship: January 5, 2003.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Frequently asked questions
- Where is APL Pusan now?
- APL Pusan (Container ship, Singapore flag) was last seen on AIS on Oct 1, 2026, 20:58 UTC, under way at 10.4 kn, in the Java Sea. The crew-entered destination was CNNSA>>IDJKT (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 18:38 UTC). This report does not confirm the ship’s current route.
- What kind of ship is APL Pusan?
- APL Pusan is a container ship sailing under the flag of Singapore, built in 2002 by Meyer Wismar. The vessel is 207.4 m long with a beam of 29.8 m and has a gross tonnage of 25,305.
- What sanctions and inspection records does Voydar hold for APL Pusan?
- Voydar has no matched sanctions record displayed for APL Pusan from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for APL Pusan. 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/9234123Using 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.