Skip to content

MO SING LENG II

Cargo ship · Hong Kong · AIS Class A

IMO1046403MMSI477997241Call signVRS6487Last AIS position Oct 6, 2026, 14:03 UTC

In short

MO SING LENG II (Cargo ship, Hong Kong flag) was last seen on AIS on , not moving, in the port of Hong Kong. Its crew-entered AIS destination is HONG KONG; its reported draught is 3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 13:55 UTC). It arrived there on Oct 6, 2026, 02:29 UTC.

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

Watch this ship

Get an email when MO SING LENG II arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

Free forever. No card. A free account follows up to 5 ships and ports.

Last reported position

received
Position
22.2958° N, 114.1303° E
Area
South China Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0 kn
Course
223°
Heading
109°
22.2958° N, 114.1303° E
Open the full live map →

Last 30 days: 9 port calls (Hong Kong and Kowloon).

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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
MO SING LENG II
IMO numberWhat is an IMO number?
1046403
MMSIWhat is an MMSI?
477997241
Call signWhat is a call sign?
VRS6487
Vessel type
Cargo ship
AIS ship type
Cargo
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
Arrived at Hong KongAIS-detectedVoydar port-call detector (AIS geofence)
Left Hong KongAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Hong KongAIS-detectedVoydar port-call detector (AIS geofence)
Left Hong KongAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Hong KongAIS-detectedVoydar port-call detector (AIS geofence)

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
Hong Kong HKHKGOct 6, 2026, 02:29 UTCin port—
Hong Kong HKHKGOct 4, 2026, 12:28 UTCOct 5, 2026, 04:58 UTC16 h 30 min
Hong Kong HKHKGOct 3, 2026, 01:24 UTCOct 3, 2026, 23:28 UTC22 h 4 min
Hong Kong HKHKGSep 30, 2026, 12:11 UTCOct 1, 2026, 04:32 UTC16 h 21 min
Hong Kong HKHKGSep 29, 2026, 02:13 UTCSep 29, 2026, 23:21 UTC21 h 9 min
Hong Kong HKHKGSep 27, 2026, 11:52 UTCSep 28, 2026, 05:13 UTC17 h 22 min
Hong Kong HKHKGSep 26, 2026, 02:04 UTCSep 26, 2026, 23:17 UTC21 h 14 min
Hong Kong HKHKGSep 24, 2026, 17:11 UTCSep 25, 2026, 05:38 UTC12 h 27 min
Kowloon HKKWNSep 12, 2026, 15:44 UTCSep 19, 2026, 22:57 UTC7 d 7 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.

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 22, 2026, 23:09 UTC
AIS gap

No AIS position received for 12 h 4 min while our receivers kept hearing other ships there (11 of 11 hours in coverage). Heard again 1 km away.

Method seadar.behaviour.ais_gap v1

High (90%)

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 MO SING LENG II now?
MO SING LENG II (Cargo ship, Hong Kong flag) was last seen on AIS on Oct 6, 2026, 14:03 UTC, not moving, in the port of Hong Kong. The crew-entered destination was HONG KONG (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 13:55 UTC). This report does not confirm the ship’s current route.
What kind of ship is MO SING LENG II?
MO SING LENG II is a cargo ship sailing under the flag of Hong Kong.
What sanctions and inspection records does Voydar hold for MO SING LENG II?
Voydar has no matched sanctions record displayed for MO SING LENG II from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels, the New Zealand Russia Sanctions Register and the French national asset-freeze register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for MO SING LENG II. 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/1046403
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