Skip to content

Ym Instruction

Cargo ship · Liberia · built 2007 · AIS Class A

IMO9331086MMSI636013118Call signA8KS6Last AIS position Sep 28, 2026, 02:37 UTC

In short

Ym Instruction (Cargo ship, Liberia flag) was last seen on AIS on , under way at 12.2 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 last detected port call was at Jurong: arrived Sep 23, 2026, left Sep 24, 2026.

Vessel type
Cargo ship
Year built
2007
Gross tonnage
16,488
Size (length × beam)
173 m × 27 m
Registered owner
—

Watch this ship

Get an email when Ym Instruction 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 Ym Instruction.

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
1.2031° N, 103.8971° E
Area
Strait of Malacca
StatusWhat do AIS statuses mean?
Under way using engine
Speed
12.2 kn
Course
62°
Heading
62°
1.2031° N, 103.8971° E
Open the full live map →

Last 30 days: 1 port call (Jurong).

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
Ym Instruction
IMO numberWhat is an IMO number?
9331086
MMSIWhat is an MMSI?
636013118
Call signWhat is a call sign?
A8KS6
Vessel type
Cargo ship
AIS ship type
Cargo (hazardous cat. C)
Gross tonnageGross tonnage vs deadweight
16,488
Length overall
172.7 m
Beam
27.3 m
Year built
2007

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.

DateEventSource
Left JurongAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at JurongAIS-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)
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)
Reported arrival at 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
Jurong SGJURSep 23, 2026, 22:01 UTCSep 24, 2026, 17:14 UTC19 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
Hong Kong HKHKGArrivalSep 11, 2026, 02:09 UTCKWAICHUNG CONTR. BERTH NO. 12 (TERMINAL 8)Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Sep 6, 2026, 03:57 UTCKWAICHUNG CONTR. BERTH NO.18 (TERMINAL9)Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalAug 14, 2026, 07:06 UTCKWAICHUNG CONTR. BERTH NO. 6 (TERMINAL 4)Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalAug 8, 2026, 11:16 UTCKWAICHUNG CONTR. BERTH NO.20 (TERMINAL 9)Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Jul 18, 2026, 08:02 UTCKC8Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Jul 9, 2026, 04:34 UTCKC1Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Jun 15, 2026, 23:36 UTCKC14Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJun 8, 2026, 23:39 UTCKWAICHUNG CONTR. BERTH NO.17 (TERMINAL 9)Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMay 18, 2026, 13:25 UTCKC12Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)May 12, 2026, 04:31 UTCKC18Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Apr 21, 2026, 08:07 UTCKC11Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Apr 16, 2026, 05:03 UTCKC17Hong Kong vessel arrivals & departures (incl. VTMS daily reports)

Records published by the authority named on each row. Earliest record for this ship: May 27, 2007.

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

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 24, 2026, 17:07 UTC
Draught change

Reported draught went from 9.3 m to 8.3 m while in port at Jurong. 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 Ym Instruction now?
Ym Instruction (Cargo ship, Liberia flag) was last seen on AIS on Sep 28, 2026, 02:37 UTC, under way at 12.2 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.
What kind of ship is Ym Instruction?
Ym Instruction is a cargo ship sailing under the flag of Liberia, built in 2007. The vessel is 172.7 m long with a beam of 27.3 m and has a gross tonnage of 16,488.
What sanctions and inspection records does Voydar hold for Ym Instruction?
Voydar has no matched sanctions record displayed for Ym Instruction 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 Ym Instruction. 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/9331086
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