Londoner Grand
High-speed craft · Hong Kong · built 2008 · AIS Class A
In short
Londoner Grand (High-speed craft, Hong Kong flag) was last seen on AIS on , not moving, near Hong Kong (South China Sea). Its crew-entered AIS destination is HK >MACAU, with an ETA of Oct 6, 2026, 22:05 UTC; its reported draught is 1.7 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 15:21 UTC).
Current voyage: from Yau Ma Tei (departed Oct 6, 2026, 11:42 UTC) to HK >MACAU
- Vessel type
- High-speed craft
- Flag
- Hong Kong
- Year built
- 2008
- Gross tonnage
- 700
- Size (length × beam)
- 48 m × 12 m
- Registered owner
- —
Watch this ship
Get an email when Londoner Grand 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.289° N, 114.1529° E
- Area
- South China Sea
- StatusWhat do AIS statuses mean?
- Reserved (HSC)
- Speed
- 0.1 kn
- Course
- 265°
- Heading
- 103°
Last 30 days: at least 12 port calls (Yau Ma Tei and Hong Kong).
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-upIdentity & particulars
- Name
- Londoner Grand
- IMO numberWhat is an IMO number?
- 9429663
- MMSIWhat is an MMSI?
- 477937400
- Call signWhat is a call sign?
- VRDO2
- Flag
- Hong Kong
- Vessel type
- High-speed craft
- Gross tonnageGross tonnage vs deadweight
- 700
- Deadweight (DWT)
- Source: Wikidata, record Q86060641. Added to Voydar on September 23, 2026. Licence: CC0 1.0.84 t
- Length overall
- 47.5 m
- Beam
- 11.8 m
- Year built
- 2008
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.
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
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.
| Date | Event | Source |
|---|---|---|
| Left Yau Ma TeiAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Yau Ma TeiAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Yau Ma TeiAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Yau Ma TeiAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Hong KongAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Hong KongAIS-detected | Voydar 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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Yau Ma Tei HK9YM | Oct 6, 2026, 09:58 UTC | Oct 6, 2026, 11:42 UTC | 1 h 45 min |
| Yau Ma Tei HK9YM | Oct 4, 2026, 16:36 UTC | Oct 6, 2026, 09:20 UTC | 40 h 44 min |
| Hong Kong HKHKG | Oct 4, 2026, 05:02 UTC | Oct 4, 2026, 05:40 UTC | 39 min |
| Hong Kong HKHKG | Oct 4, 2026, 02:03 UTC | Oct 4, 2026, 02:41 UTC | 38 min |
| Hong Kong HKHKG | Oct 3, 2026, 17:23 UTC | Oct 3, 2026, 23:40 UTC | 6 h 16 min |
| Hong Kong HKHKG | Oct 3, 2026, 13:06 UTC | Oct 3, 2026, 14:43 UTC | 1 h 37 min |
| Hong Kong HKHKG | Oct 3, 2026, 10:01 UTC | Oct 3, 2026, 10:48 UTC | 47 min |
| Hong Kong HKHKG | Oct 3, 2026, 07:07 UTC | Oct 3, 2026, 07:41 UTC | 34 min |
| Hong Kong HKHKG | Oct 3, 2026, 03:33 UTC | Oct 3, 2026, 04:11 UTC | 38 min |
| Hong Kong HKHKG | Oct 2, 2026, 15:25 UTC | Oct 3, 2026, 01:12 UTC | 9 h 47 min |
| Hong Kong HKHKG | Oct 2, 2026, 11:02 UTC | Oct 2, 2026, 12:39 UTC | 1 h 37 min |
| Hong Kong HKHKG | Oct 2, 2026, 04:32 UTC | Oct 2, 2026, 08:43 UTC | 4 h 12 min |
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.
Frequently asked questions
- Where is Londoner Grand now?
- Londoner Grand (High-speed craft, Hong Kong flag) was last seen on AIS on Oct 6, 2026, 15:27 UTC, not moving, near Hong Kong (South China Sea). The crew-entered destination was HK >MACAU (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 15:21 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Londoner Grand?
- Londoner Grand is a high-speed craft sailing under the flag of Hong Kong, built in 2008 by Austal. The vessel is 47.5 m long with a beam of 11.8 m and has a gross tonnage of 700.
- What sanctions and inspection records does Voydar hold for Londoner Grand?
- Voydar has no matched sanctions record displayed for Londoner Grand 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 Londoner Grand. 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/9429663Using 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.