Port Phillip
General cargo ship · Singapore · built 2008 · AIS Class A
In short
Port Phillip (General cargo ship, Singapore flag) was last seen on AIS on , at anchor, near Seattle (North Pacific Ocean). Its crew-entered AIS destination is US SEA (Seattle); its reported draught is 5.9 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 18:40 UTC).
- Vessel type
- General cargo ship
- Flag
- Singapore
- Year built
- 2008
- Gross tonnage
- 20,987
- Size (length × beam)
- 180 m × 28 m
- Registered owner
- —
Watch this ship
Get an email when Port Phillip reaches Seattle, and when it 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 Port Phillip.
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
- 47.5969° N, 122.3674° W
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- At anchor
- Speed
- 0 kn
- Course
- 94°
- Heading
- 216°
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
- Port Phillip
- IMO numberWhat is an IMO number?
- 9377975
- MMSIWhat is an MMSI?
- 563326500
- Call signWhat is a call sign?
- S6UV5
- Flag
- Singapore
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 20,987
- Deadweight (DWT)
- Source: Wikidata, record Q84256726. Added to Voydar on September 23, 2026. Licence: CC0 1.0.33,171 t
- Length overall
- 179.9 m
- Beam
- 28.4 m
- Year built
- 2008
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 |
|---|---|---|
| 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 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.
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 |
|---|---|---|---|---|
| 2019 | 2,122 t | 674 t | 53 days | 176 kg |
| 2020 | 4,442 t | 1,423 t | 80 days | 239 kg |
| 2022 | 9,794 t | 3,106 t | 142 days | 261 kg |
Technical efficiency: EIV (6.8 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
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 | Jun 15, 2024, 05:12 UTC | SWLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jun 6, 2023, 20:17 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Long Beach USLGB | Departure | Jan 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Jan 16, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Jan 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Jan 8, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Coos Bay USCOB | Departure | Dec 22, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Coos Bay USCOB | Arrival | Dec 12, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Dec 9, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Nov 21, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Feb 28, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Feb 20, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: May 20, 2009.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
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 1, 2026, 11:02 UTC | Draught change Reported draught went from 10.5 m to 7.6 m while in port at Seattle. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
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 Port Phillip now?
- Port Phillip (General cargo ship, Singapore flag) was last seen on AIS on Oct 4, 2026, 18:55 UTC, at anchor, near Seattle (North Pacific Ocean). The crew-entered destination was US SEA (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 18:40 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Port Phillip?
- Port Phillip is a general cargo ship sailing under the flag of Singapore, built in 2008. The vessel is 179.9 m long with a beam of 28.4 m and has a gross tonnage of 20,987.
- What sanctions and inspection records does Voydar hold for Port Phillip?
- Voydar has no matched sanctions record displayed for Port Phillip 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 Port Phillip. 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/9377975Using 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.