vessel 413843285 IMO: 0,

callsign:
size: x

Live Vessel 413843285 Analytics (details, animations, etc.)

Live AIS position: 31.32474° N, 120.55776° E UTC. 20 nm SE of Wuxi), updated 2026-03-24 11:27:14 UTC.

Find the position of the vessel 413843285 on the map. The latter are known coordinates and path.

marine traffic ship tracker show on live map

The current position of vessel 413843285 is 31.32474 lat / 120.55776 lng. Updated: 2026-03-24 11:27:14 UTC

Details:

Last coordinates of the vessel:

UTC, 31.61625, 120.26238, course: 0, speed: 3.8
UTC, 31.49881, 120.37528, course: 0, speed: 3
UTC, 31.40656, 120.47319, course: 0, speed: 4
2026-03-24 11:27:14 UTC, 31.32474, 120.55776, course: 0, speed: 3.9

Track of the vessel in the last 28 days

Most frequent ports a vessels calls at 413843285 (413843285):

Shanghai, traffic: 23

Wusong, traffic: 22

Wu-Sung, traffic: 20

ZHAPU, traffic: 13

Taicang, traffic: 12

Zhangjiagang, traffic: 10

Nantong, traffic: 6

HUANGPU, traffic: 3

Zhapu Pt, traffic: 1

Taixing, traffic: 1

Haining, traffic: 1

Haiyan, traffic: 1

Nantong Pt, traffic: 1

Link to the map:

Find another ship

413843285 (413843285) last ports (portcalls and passsages)

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

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.