APIA CHIEF
Container ship · Singapore · built 2013 · AIS Class A
In short
APIA CHIEF (Container ship, Singapore flag) was last seen on AIS on , moored, in the port of Suva. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is FJSUV (Suva); its reported draught is 8.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 02:40 UTC). It arrived there on Oct 2, 2026, 10:46 UTC.
- Vessel type
- Container ship
- Flag
- Singapore
- Year built
- 2013
- Gross tonnage
- 25,483
- Size (length × beam)
- 199 m × 28 m
- Registered owner
- —
Watch this ship
Get an email when APIA 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 APIA 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
- 18.1318° S, 178.4244° E
- Area
- South Pacific Ocean
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 297°
- Heading
- 203°
Last 30 days: 2 port calls (Suva and Lautoka).
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
- APIA CHIEF
- IMO numberWhat is an IMO number?
- 9614529
- MMSIWhat is an MMSI?
- 563991000
- Call signWhat is a call sign?
- 9V9832
- Flag
- Singapore
- Vessel type
- Container ship
- AIS ship type
- Cargo (hazardous cat. C)
- Gross tonnageGross tonnage vs deadweight
- 25,483
- Deadweight (DWT)
- Source: Wikidata, record Q117027674. Added to Voydar on September 23, 2026. Licence: CC0 1.0.31,756 t
- Length overall
- 199 m
- Beam
- 28 m
- Year built
- 2013
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 |
|---|---|---|
| Arrived at SuvaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left LautokaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at LautokaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from SeattleAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at SeattleAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from Long BeachAuthority-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.
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 |
|---|---|---|---|
| Suva FJSUV | Oct 2, 2026, 10:46 UTC | in port | — |
| Lautoka FJLTK | Sep 30, 2026, 12:30 UTC | Oct 2, 2026, 09:02 UTC | 44 h 33 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 |
|---|---|---|---|---|
| Seattle USSEA | Departure | Dec 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Dec 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Oct 21, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Oct 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Departure | Oct 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Arrival | Oct 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| EVERETT HARBOR AND SNOHOMISH RIVER, WA | Departure | Oct 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| EVERETT HARBOR AND SNOHOMISH RIVER, WA | Arrival | Oct 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Aug 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Jul 31, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Departure | Jul 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Arrival | Jul 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: February 10, 2014.
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 2, 2026, 09:41 UTC | Draught change Reported draught went from 9.3 m to 8.5 m after leaving Lautoka. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
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 APIA CHIEF now?
- APIA CHIEF (Container ship, Singapore flag) was last seen on AIS on Oct 3, 2026, 03:01 UTC, moored, in the port of Suva. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was FJSUV (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 02:40 UTC). This report does not confirm the ship’s current route.
- What kind of ship is APIA CHIEF?
- APIA CHIEF is a container ship sailing under the flag of Singapore, built in 2013. The vessel is 199 m long with a beam of 28 m and has a gross tonnage of 25,483.
- What sanctions and inspection records does Voydar hold for APIA CHIEF?
- Voydar has no matched sanctions record displayed for APIA 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 APIA 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/9614529Using 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.