Skip to content

EVER COMMAND

Cargo ship · Liberia · AIS Class A

IMO9903267MMSI636021200Call sign5LCT7Last AIS position Sep 30, 2026, 21:02 UTC

In short

EVER COMMAND (Cargo ship, Liberia flag) was last seen on AIS on , under way at 15.8 kn, in the East China 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 TW KHH (Kaohsiung); its reported draught is 9.7 m (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 20:32 UTC).

Current voyage: from Bali (departed Sep 30, 2026, 18:46 UTC) to TW KHH (Kaohsiung)

Vessel type
Cargo ship
Year built
—
Gross tonnage
—
Size (length × beam)
—
Registered owner
—

Watch this ship

Get an email when EVER COMMAND 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 EVER COMMAND.

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
25.066° N, 120.851° E
Area
East China Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
15.8 kn
Course
229°
Heading
227°
25.066° N, 120.851° E
Open the full live map →

Last 30 days: 2 port calls (Bali and Incheon).

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
EVER COMMAND
IMO numberWhat is an IMO number?
9903267
MMSIWhat is an MMSI?
636021200
Call signWhat is a call sign?
5LCT7
Vessel type
Cargo ship
AIS ship type
Cargo (hazardous cat. A)
Length overall
—
Beam
—
Year built
—

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 BaliAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BaliAIS-detectedVoydar port-call detector (AIS geofence)
Left IncheonAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at IncheonAIS-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
Bali TWBALSep 30, 2026, 10:54 UTCSep 30, 2026, 18:46 UTC7 h 51 min
Incheon KRINCSep 25, 2026, 23:25 UTCSep 30, 2026, 01:49 UTC4 d 2 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 HKHKGArrivalJun 6, 2026, 12:31 UTCKC8Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)May 30, 2026, 02:17 UTCKC7Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMay 3, 2026, 10:39 UTCWA2Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Apr 25, 2026, 05:14 UTCKC10Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalApr 3, 2026, 18:33 UTCKC7Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMar 27, 2026, 17:50 UTCKWAICHUNG CONTR. BERTH NO. 8 (TERMINAL 6)Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalFeb 28, 2026, 06:11 UTCWA2Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Feb 23, 2026, 01:25 UTCKC10Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJan 25, 2026, 17:11 UTCKC8Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJan 18, 2026, 04:24 UTCKC8Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Dec 20, 2025, 05:28 UTCKC7Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Dec 12, 2025, 04:37 UTCKC10Hong Kong vessel arrivals & departures (incl. VTMS daily reports)

Records published by the authority named on each row. Earliest record for this ship: February 25, 2022.

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 30, 2026, 08:52 UTC
Draught change

Reported draught went from 9.3 m to 10 m after leaving Incheon. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)

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 EVER COMMAND now?
EVER COMMAND (Cargo ship, Liberia flag) was last seen on AIS on Sep 30, 2026, 21:02 UTC, under way at 15.8 kn, in the East China 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 TW KHH (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 20:32 UTC). This report does not confirm the ship’s current route.
What kind of ship is EVER COMMAND?
EVER COMMAND is a cargo ship sailing under the flag of Liberia.
What sanctions and inspection records does Voydar hold for EVER COMMAND?
Voydar has no matched sanctions record displayed for EVER COMMAND 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 EVER COMMAND. 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/9903267
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