Loading portcalls…

Vessel photo of WAN LI XIN HUO1658 (IMO 0)

WAN LI XIN HUO1658

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

Current Status

Where is the vessel?

WAN LI XIN HUO1658 is currently in Near Jingjiang Pt, based on AIS data received about 1h ago.

Latest AIS update: 2026-04-12 13:46:44 UTC

Current position: 32.01585° N, 120.36145° E (Near Jingjiang Pt)

Average speed (last 7 days): Loading…

Average speed (last 30 days): Loading…

Vessel profile: WAN LI XIN HUO1658 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 WAN LI XIN HUO1658 is 32.01585 lat / 120.36145 lng. Updated: 2026-04-12 13:46:44 UTC

Nearest reference points:

Near Jingjiang Pt
Near Zhangjiagang
Near Jiangyin Pt

Details:

Live Vessel WAN LI XIN HUO1658 Analytics (details, animations, etc.)

Recent AIS points (UTC):

2026-04-12 07:29:33 UTC · 32.01590, 120.36147 · SOG 0 kn · COG -1°
2026-04-12 10:08:02 UTC · 32.01585, 120.36142 · SOG 0 kn · COG -1°
2026-04-12 11:34:44 UTC · 32.01590, 120.36147 · SOG 0 kn · COG -1°
2026-04-12 13:46:44 UTC · 32.01585, 120.36145 · SOG 0 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=413770762
/topos/api/vessel/track?days=60&imo=0&mmsi=413770762
/topos/api/vessel/portcalls?days=90&imo=0&mmsi=413770762
/topos/api/vessel/news?imo=0&mmsi=413770762
/topos/api/v1/marketplace/manifest

WAN_LI_XIN_HUO1658 (413770762) last ports (portcalls and passsages)

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

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.