Skip to content

Phoenix Leader

Car carrier · Japan · built 2004 · AIS Class A

IMO9283875MMSI431858000Call sign7KNBLast AIS position Oct 2, 2026, 06:50 UTC

In short

Phoenix Leader (Car carrier, Japan flag) was last seen on AIS on , under way at 11 kn, near Uraga (North Pacific Ocean). 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 JP NGO (Nagoya, Aichi); its reported draught is 7.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 06:41 UTC). ISM manager: NYK SHIPMANAGEMENT PTE LTD (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Current voyage: from Kawasaki (departed Oct 2, 2026, 06:16 UTC) to JP NGO (Nagoya, Aichi)

Vessel type
Car carrier
Flag
Japan
Year built
2004
Gross tonnage
61,804
Size (length × beam)
200 m

Watch this ship

Phoenix Leader has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

We email you a link and a code. That creates a free account, no password or card, and follows Phoenix Leader.

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.

Photo of PHOENIX LEADER
Photo: Bahnfrend · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
35.2568° N, 139.7683° E
Area
North Pacific Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
11 kn
Course
157°
Heading
155°
35.2568° N, 139.7683° E
Open the full live map →

Last 30 days: 1 port call (Kawasaki).

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-up

Identity & particulars

Name
Phoenix Leader
IMO numberWhat is an IMO number?
9283875
MMSIWhat is an MMSI?
431858000
Flag
Japan
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
61,804
Length overall
199.9 m
Beam
—
Year built
2004

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.

ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 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.

DateEventSource
Left KawasakiAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at KawasakiAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at JACKSONVILLE HARBOR, FLAuthority-reportedUSACE 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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20182,944 t943 t26 days364 kg
20198,173 t2,610 t68 days335 kg
20203,448 t1,092 t30 days317 kg
20215,678 t1,792 t45 days351 kg
202210,198 t3,231 t87 days322 kg
20232,790 t882 t20 days366 kg
20246,677 t2,171 t65 days311 kg
20253,095 t982 t27 days342 kg

Technical efficiency: EEXI (14.5 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.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Kawasaki JPKWSOct 1, 2026, 06:02 UTCOct 2, 2026, 06:16 UTC24 h 13 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

PortRecordDate (UTC)BerthSource
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureSep 26, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalSep 25, 2016(date only)—USACE foreign traffic vessel entrances & clearances
JACKSONVILLE HARBOR, FLArrivalSep 21, 2016(date only)—USACE foreign traffic vessel entrances & clearances
JACKSONVILLE HARBOR, FLDepartureSep 21, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCDepartureSep 14, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalSep 13, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Boston USBOSArrivalSep 12, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Boston USBOSDepartureSep 12, 2016(date only)—USACE foreign traffic vessel entrances & clearances
NARRAGANSETT BAY, RIArrivalSep 9, 2016(date only)—USACE foreign traffic vessel entrances & clearances
NARRAGANSETT BAY, RIDepartureSep 9, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALDepartureSep 6, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALArrivalSep 5, 2016(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: November 21, 2005.

Frequently asked questions

Where is Phoenix Leader now?
Phoenix Leader (Car carrier, Japan flag) was last seen on AIS on Oct 2, 2026, 06:50 UTC, under way at 11 kn, near Uraga (North Pacific Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was JP NGO (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 06:41 UTC). This report does not confirm the ship’s current route.
What kind of ship is Phoenix Leader?
Phoenix Leader is a car carrier sailing under the flag of Japan, built in 2004 by Imabari Shipbuilding Marugame Headquarters. The vessel is 199.9 m long and has a gross tonnage of 61,804.
Who is recorded as the owner or manager of Phoenix Leader?
NYK SHIPMANAGEMENT PTE LTD is recorded as ISM manager for Phoenix Leader (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Phoenix Leader?
Voydar has no matched sanctions record displayed for Phoenix Leader 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 Phoenix Leader. 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/9283875
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using 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.

See plans