Vessel photo of 'JILEYU3318' (IMO 0)

'JILEYU3318'

Vessel type: | IMO: 0 | MMSI: MMSI: 412331881
Call sign:

Current Status

Where is the vessel?

'JILEYU3318' is currently in Near LANSHAN, based on AIS data received about 89d ago.

Latest AIS update: 2026-01-11 02:10:23 UTC

Current position: 35.13574° N, 119.37558° E (Near LANSHAN)

Average speed (last 7 days): Loading…

Average speed (last 30 days): Loading…

Vessel profile: 'JILEYU3318' is a vessel with dimensions m x m.

This page combines live AIS, route history, probable destination signals, nearby traffic, and port activity for practical vessel monitoring.

The current position of vessel 'JILEYU3318' is 35.13574 lat / 119.37558 lng. Updated: 2026-01-11 02:10:23 UTC

Nearest reference points:

Near LANSHAN
Near Lanshan Pt
Near Rizhao

Details:

Live Vessel 'JILEYU3318' Analytics (details, animations, etc.)

Recent AIS points (UTC):

2026-01-11 02:10:23 UTC · 35.13574, 119.37558 · SOG 0.4 kn · COG -1°

Track of the vessel in the last 60 days

UTC: --

Start: -- Track timeline (UTC) End: --

Show names Show encountered vessels Encountered: --

Link to the map:

Find another ship

AI agent endpoints for this vessel

/topos/api/vessel/summary?imo=0&mmsi=412331881
/topos/api/vessel/track?days=60&imo=0&mmsi=412331881
/topos/api/vessel/portcalls?days=90&imo=0&mmsi=412331881
/topos/api/vessel/news?imo=0&mmsi=412331881
/topos/api/v1/marketplace/manifest

'JILEYU3318' (412331881) last ports (portcalls and passsages)

Lanshan Pt | 2025-09-14 11:40:21
Lanshan Pt | 2025-09-08 11:05:17
Lanshan Pt | 2025-09-02 14:44:43
LANSHAN | 2025-09-02 02:25:45
LANSHAN | 2025-08-28 18:11:15
LANSHAN | 2025-08-24 17:41:45
LANSHAN | 2025-08-20 17:25:26
LANSHAN | 2025-08-16 17:12:41
LANSHAN | 2025-08-12 16:46:46
LANSHAN | 2025-08-08 16:16:05
LANSHAN | 2025-08-04 16:04:26
LANSHAN | 2025-07-31 14:37:58
LANSHAN | 2025-07-27 13:53:12
LANSHAN | 2025-07-23 13:05:58
LANSHAN | 2025-07-19 12:15:45
LANSHAN | 2025-07-15 11:19:54
LANSHAN | 2025-07-11 11:09:14
LANSHAN | 2025-07-07 10:59:59
LANSHAN | 2025-07-03 10:20:53
LANSHAN | 2025-06-29 09:39:37
LANSHAN | 2025-06-25 09:14:18
LANSHAN | 2025-06-21 08:36:37
LANSHAN | 2025-06-17 08:24:11
LANSHAN | 2025-06-13 07:11:18
LANSHAN | 2025-06-09 06:48:42
LANSHAN | 2025-06-05 06:02:17
LANSHAN | 2025-06-01 05:58:42
LANSHAN | 2025-05-28 04:24:55
LANSHAN | 2025-05-24 04:09:00
LANSHAN | 2025-05-20 04:07:16
LANSHAN | 2025-05-16 03:06:05
LANSHAN | 2025-05-12 02:52:03
LANSHAN | 2025-05-08 02:34:10
LANSHAN | 2025-05-04 02:05:13
LANSHAN | 2025-04-30 01:39:36
LANSHAN | 2025-04-26 01:07:42
LANSHAN | 2025-04-22 01:05:01
LANSHAN | 2025-04-18 00:51:01
LANSHAN | 2025-04-14 00:42:33
LANSHAN | 2025-04-10 00:15:49
LANSHAN | 2025-04-05 23:27:39
LANSHAN | 2025-04-01 22:49:14
LANSHAN | 2025-03-28 21:13:30
LANSHAN | 2025-03-24 21:03:17
LANSHAN | 2025-03-20 20:29:23
LANSHAN | 2025-03-16 20:24:59
LANSHAN | 2025-03-12 19:16:13
LANSHAN | 2025-03-08 18:49:03
LANSHAN | 2025-03-04 18:15:45
LANSHAN | 2025-02-28 17:17:02
LANSHAN | 2025-02-24 16:25:57
LANSHAN | 2025-02-20 15:51:56
LANSHAN | 2025-02-16 15:42:45
LANSHAN | 2025-02-12 15:12:43
LANSHAN | 2025-02-08 14:16:18
LANSHAN | 2025-02-04 12:54:30
LANSHAN | 2025-01-31 12:54:02
LANSHAN | 2025-01-27 12:50:32
LANSHAN | 2025-01-23 12:27:00
LANSHAN | 2025-01-19 12:18:43
LANSHAN | 2025-01-15 12:13:45
LANSHAN | 2025-01-11 11:03:15
LANSHAN | 2025-01-07 10:19:35
LANSHAN | 2025-01-03 08:40:08
LANSHAN | 2024-12-30 08:20:28
LANSHAN | 2024-12-26 08:20:02
LANSHAN | 2024-12-22 06:48:32
LANSHAN | 2024-12-18 06:21:04
LANSHAN | 2024-12-14 05:23:36
LANSHAN | 2024-12-10 04:58:40
LANSHAN | 2024-12-06 04:28:06
LANSHAN | 2024-12-01 23:19:52
LANSHAN | 2024-11-27 22:09:16
LANSHAN | 2024-11-23 21:20:10
LANSHAN | 2024-11-19 20:16:12
LANSHAN | 2024-11-15 20:12:30
LANSHAN | 2024-11-11 19:06:12
LANSHAN | 2024-11-07 18:05:00
LANSHAN | 2024-11-03 17:34:16

Find ship location on the map, vessel routs, position and coordinates

info@shipinfo.net
© shipinfo.net
Shipinfo analytics and prediction platform
Privacy Policy
Cookie Policy
Terms of Use

Machine-readable discovery is available via manifest/OpenAPI/schema index. For paid interactions only, payer autonomy is supported: agent_self_assessed_fair_value, paid_interactions_only.