Loading portcalls…

Vessel photo of LAGENDA SERENITY (IMO 9905980)

LAGENDA SERENITY

Vessel type: LNG Tanker | IMO: 9905980 | MMSI: MMSI: 563147300
Call sign: 9V7016

Current Status

Where is the vessel?

LAGENDA SERENITY is currently in 42 nm W of Tindalo Oil Field, based on AIS data received about 2h ago.

Latest AIS update: 2026-03-28 05:55:32 UTC

Current position: 10.92833° N, 118.19333° E (42 nm W of Tindalo Oil Field)

Average speed (last 7 days): Loading…

Average speed (last 30 days): Loading…

Vessel profile: LAGENDA SERENITY is a LNG Tanker 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 LAGENDA SERENITY is 10.92833 lat / 118.19333 lng. Updated: 2026-03-28 05:55:32 UTC

Nearest reference points:

43 nm W of Malampaya
70 nm W of Puerto Princesa
65 nm NW of Malampaya

Currently sailing under the flag of Singapore

LAGENDA SERENITY built in 2022 year

Deadweight:

45419 t

Details:

Live Vessel LAGENDA SERENITY Analytics (details, animations, etc.)

Recent AIS points (UTC):

2026-03-28 00:01:33 UTC · 9.52167, 117.31833 · SOG 17 kn · COG -1°
2026-03-28 01:31:32 UTC · 9.85833, 117.59167 · SOG 17 kn · COG -1°
2026-03-28 03:52:34 UTC · 10.38333, 118.01333 · SOG 17 kn · COG -1°
2026-03-28 05:55:32 UTC · 10.92833, 118.19333 · SOG 17 kn · COG -1°

Track of the vessel in the last 28 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=9905980&mmsi=563147300
/topos/api/vessel/track?days=60&imo=9905980&mmsi=563147300
/topos/api/vessel/portcalls?days=90&imo=9905980&mmsi=563147300
/topos/api/vessel/news?imo=9905980&mmsi=563147300
/topos/api/v1/marketplace/manifest

LAGENDA_SERENITY (563147300) last ports (portcalls and passsages)

BINTULU | 2025-09-14 11:41:22
Gonglu | 2025-09-08 08:41:16
BINTULU | 2025-09-02 02:25:01
YANGSHAN | 2025-08-26 06:11:41
BINTULU | 2025-08-18 07:02:40
Jingjiang | 2025-08-09 00:57:50
BINTULU | 2025-08-03 05:53:10
Jingjiang | 2025-07-26 01:04:09
BINTULU | 2025-07-16 02:21:03
Jingjiang | 2025-07-10 00:20:03
BINTULU | 2025-07-02 02:56:37
Jingjiang | 2025-06-25 00:01:32
BINTULU | 2025-06-04 01:37:23
Jingjiang | 2025-05-29 00:38:08
BINTULU | 2025-05-23 01:14:04
Jingjiang | 2025-05-09 23:19:01
BINTULU | 2025-04-30 05:24:21
Jingjiang | 2025-04-23 21:04:49
BINTULU | 2025-04-17 21:20:08
YANGSHAN | 2025-04-08 00:17:27
BINTULU | 2025-04-01 06:49:22
BINTULU | 2025-03-19 01:16:44
YANGSHAN | 2025-03-13 03:49:10
BINTULU | 2025-03-03 02:20:51
Jingjiang | 2025-02-24 22:13:31
BINTULU | 2025-02-17 04:29:01
WAILINGDING ISLAND | 2025-02-12 22:07:22
YANGSHAN | 2025-02-09 00:48:35
BINTULU | 2025-01-25 23:47:28
Jingjiang | 2025-01-19 03:17:40
BINTULU | 2025-01-12 01:27:18
YANGSHAN | 2025-01-05 06:52:35
BINTULU | 2024-12-28 12:40:32
Jingjiang | 2024-12-22 04:03:10
BINTULU | 2024-12-15 03:21:37
YANGSHAN | 2024-12-08 09:24:44
BINTULU | 2024-11-30 03:15:36
YANGSHAN | 2024-11-23 08:53:21
BINTULU | 2024-11-15 20:44:35
YANGSHAN | 2024-11-09 08:52:32
Jingjiang | 2024-09-23 02:15:15
Singapore | 2024-08-28 04:29:11
Jingjiang | 2024-08-21 00:22:33
Jingjiang | 2024-07-23 01:02:33
Jingjiang | 2024-07-09 01:38:55
Jingjiang | 2024-05-23 04:26:37
Jingjiang | 2024-04-22 04:13:57
Jingjiang | 2024-03-25 00:12:39
Jingjiang | 2024-02-26 01:31:04
Jingjiang | 2024-02-09 00:22:47
Jingjiang | 2024-01-23 23:31:53
Jingjiang | 2024-01-10 03:46:33
Jingjiang | 2023-12-04 04:44:59
Singapore | 2023-09-26 08:55:52
Jingjiang | 2023-09-19 01:31:42
Jingjiang | 2023-09-06 04:04:14
Jingjiang | 2023-08-21 02:07:07
Jingjiang | 2023-08-07 02:56:53
Jingjiang | 2023-07-22 02:32:28

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.