Skip to content

Antares Leader

Car carrier · Japan · built 2011 · AIS Class A

IMO9539169MMSI431761000Call sign7KLJLast AIS position Sep 29, 2026, 00:30 UTC

In short

Antares Leader (Car carrier, Japan flag) was last seen on AIS on , under way at 16.6 kn, in the Java Sea. 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 ID PTB; its reported draught is 8 m (voyage report via AISstream.io global terrestrial AIS, received Sep 27, 2026, 15:04 UTC).

Current voyage: from Keppel (departed Sep 27, 2026, 01:14 UTC) to ID PTB

Vessel type
Car carrier
Flag
Japan
Year built
2011
Gross tonnage
60,284
Size (length × beam)
200 m
Registered owner
—

Watch this ship

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

Free forever. No card. A free account follows up to 5 ships and ports.

Photo of ANTARES LEADER
Photo: Farid mernissi · Licence: CC BY 4.0 · via Wikimedia Commons

Last reported position

received
Position
4.0792° S, 107.6124° E
Area
Java Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
16.6 kn
Course
345°
Heading
348°
4.0792° S, 107.6124° E
Open the full live map →

Last 30 days: 1 port call (Keppel).

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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
Antares Leader
IMO numberWhat is an IMO number?
9539169
MMSIWhat is an MMSI?
431761000
Flag
Japan
Vessel type
Car carrier
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
60,284
Length overall
200 m
Beam
—
Year built
2011

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.

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 KeppelAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at KeppelAIS-detectedVoydar port-call detector (AIS geofence)
Reported arrival at San DiegoAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at TacomaAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from TacomaAuthority-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
201811,330 t3,621 t102 days302 kg
20192,606 t832 t24 days298 kg
20203,122 t990 t32 days270 kg
20213,111 t979 t36 days295 kg
20225,187 t1,641 t45 days314 kg
20238,711 t2,780 t88 days289 kg

Technical efficiency: EIV (15.97 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
Keppel SGKEPSep 25, 2026, 02:46 UTCSep 27, 2026, 01:14 UTC46 h 28 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
San Diego USSANArrivalDec 27, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Tacoma USTIWArrivalDec 19, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Tacoma USTIWDepartureDec 19, 2016(date only)—USACE foreign traffic vessel entrances & clearances
San Diego USSANArrivalJun 28, 2016(date only)—USACE foreign traffic vessel entrances & clearances
San Diego USSANDepartureJun 28, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Port Hueneme USNTDDepartureJun 26, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Port Hueneme USNTDArrivalJun 26, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Tacoma USTIWDepartureJun 19, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Tacoma USTIWArrivalJun 19, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureMar 21, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalMar 20, 2016(date only)—USACE foreign traffic vessel entrances & clearances
JACKSONVILLE HARBOR, FLDepartureMar 14, 2016(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: August 16, 2011.

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.

WhenWhat we observedConfidence
Sep 25, 2026, 20:25 UTC
Draught change

Reported draught went from 8.9 m to 8.2 m while in port at Keppel. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)

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.

How these are computed →

Frequently asked questions

Where is Antares Leader now?
Antares Leader (Car carrier, Japan flag) was last seen on AIS on Sep 29, 2026, 00:30 UTC, under way at 16.6 kn, in the Java Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was ID PTB (voyage report via AISstream.io global terrestrial AIS, received Sep 27, 2026, 15:04 UTC). This report does not confirm the ship’s current route.
What kind of ship is Antares Leader?
Antares Leader is a car carrier sailing under the flag of Japan, built in 2011 by Mitsubishi Heavy Industries Kobe Shipyard & Machinery Works. The vessel is 200 m long and has a gross tonnage of 60,284.
What sanctions and inspection records does Voydar hold for Antares Leader?
Voydar has no matched sanctions record displayed for Antares 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 Antares 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/9539169
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