Skip to content

Asean Explorer

Other · Indonesia · built 2002 · AIS Class A

IMO9236676MMSI525018271Call signJZSYLast AIS position Sep 30, 2026, 03:46 UTC

In short

Asean Explorer (Other, Indonesia flag) was last seen on AIS on , under way at 9.8 kn, near Pulau Sambu, Riau (Strait of Malacca). 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 JPKKJ, JAPAN, with an ETA of Oct 11, 2026, 00:01 UTC; its reported draught is 7.7 m (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 03:03 UTC).

Current voyage: from Tanjong Pagar (departed Sep 22, 2026, 23:04 UTC) to JPKKJ, JAPAN

Vessel type
Other
Year built
2002
Gross tonnage
14,988
Size (length × beam)
82 m
Registered owner
—

Watch this ship

Get an email when Asean Explorer 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 Asean Explorer.

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 ASEAN EXPLORER
Photo: Photo by CEphoto, Uwe Aranas or alternatively © CEphoto, Uwe Aranas · Licence: CC BY-SA 3.0 · via Wikimedia Commons

Last reported position

received
Position
1.2109° N, 103.9011° E
Area
Strait of Malacca
StatusWhat do AIS statuses mean?
Under way using engine
Speed
9.8 kn
Course
79°
Heading
77°
1.2109° N, 103.9011° E
Open the full live map →

Last 30 days: 1 port call (Tanjong Pagar).

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
Asean Explorer
IMO numberWhat is an IMO number?
9236676
MMSIWhat is an MMSI?
525018271
Vessel type
Other
Gross tonnageGross tonnage vs deadweight
14,988
Length overall
82 m
Beam
—
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.

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 Tanjong PagarAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Tanjong PagarAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Hong KongAuthority-reportedHong 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.

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
Tanjong Pagar SGTPGSep 18, 2026, 05:58 UTCSep 22, 2026, 23:04 UTC4 d 17 h

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
Hong Kong HKHKGArrivalJan 15, 2019, 03:28 UTCKA3Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGDeparture(matched by call sign)Jan 9, 2019, 00:07 UTCNWLAHong Kong vessel arrivals & departures (incl. VTMS daily reports)

Records published by the authority named on each row. Earliest record for this ship: January 9, 2019.

Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.

Frequently asked questions

Where is Asean Explorer now?
Asean Explorer (Other, Indonesia flag) was last seen on AIS on Sep 30, 2026, 03:46 UTC, under way at 9.8 kn, near Pulau Sambu, Riau (Strait of Malacca). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was JPKKJ, JAPAN (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 03:03 UTC). This report does not confirm the ship’s current route.
What kind of ship is Asean Explorer?
Asean Explorer is a other sailing under the flag of Indonesia, built in 2002 by Jurong Shipyard. The vessel is 82 m long and has a gross tonnage of 14,988.
What sanctions and inspection records does Voydar hold for Asean Explorer?
Voydar has no matched sanctions record displayed for Asean Explorer 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 Asean Explorer. 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/9236676
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