HUA HANG 6
Cargo ship · Hong Kong · built 2007 · AIS Class A
In short
HUA HANG 6 (Cargo ship, Hong Kong flag) was last seen on AIS on , under way at 12.8 kn, in the East China Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is XIAMEN; its reported draught is 6.2 m (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 21:50 UTC). Its last detected port call was at Keelung (Chilung): arrived Sep 26, 2026, left Sep 26, 2026.
- Vessel type
- Cargo ship
- Flag
- Hong Kong
- Year built
- 2007
- Gross tonnage
- 7,545
- Size (length × beam)
- 130 m
- Registered owner
- —
Watch this ship
Get an email when HUA HANG 6 arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
We email you a link and a code. That creates a free account, no password or card, and follows HUA HANG 6.
Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.
By continuing you accept the Terms and the Privacy policy.

Last reported position
received- Position
- 25.1666° N, 120.9722° E
- Area
- East China Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 12.8 kn
- Course
- 250°
- Heading
- 248°
Last 30 days: 2 port calls (Keelung (Chilung)).
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)
Try the live demo, no sign-upIdentity & particulars
- Name
- HUA HANG 6
- IMO numberWhat is an IMO number?
- 9339040
- MMSIWhat is an MMSI?
- 477057900
- Call signWhat is a call sign?
- VRQV7
- Flag
- Hong Kong
- Vessel type
- Cargo ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 7,545
- Length overall
- 129.6 m
- Beam
- —
- Year built
- 2007
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 Keelung (Chilung)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Keelung (Chilung)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Keelung (Chilung)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Keelung (Chilung)AIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
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 |
|---|---|---|---|
| Keelung (Chilung) TWKEL | Sep 26, 2026, 05:46 UTC | Sep 26, 2026, 22:13 UTC | 16 h 26 min |
| Keelung (Chilung) TWKEL | Sep 22, 2026, 18:51 UTC | Sep 23, 2026, 15:00 UTC | 20 h 9 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival(matched by call sign) | Jun 3, 2019, 01:09 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 7, 2018, 14:04 UTC | SWLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Nov 22, 2018, 03:08 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Nov 7, 2018, 03:18 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | May 15, 2018, 01:25 UTC | PT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
Records published by the authority named on each row. Earliest record for this ship: May 15, 2018.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
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.
| When | What we observed | Confidence |
|---|---|---|
| Sep 26, 2026, 21:51 UTC | Draught change Reported draught went from 7.5 m to 6.2 m while in port at Keelung (Chilung). Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 23, 2026, 14:40 UTC | Draught change Reported draught went from 7.6 m to 6.3 m while in port at Keelung (Chilung). Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
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.
Frequently asked questions
- Where is HUA HANG 6 now?
- HUA HANG 6 (Cargo ship, Hong Kong flag) was last seen on AIS on Sep 27, 2026, 01:20 UTC, under way at 12.8 kn, in the East China Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was XIAMEN (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 21:50 UTC). This report does not confirm the ship’s current route.
- What kind of ship is HUA HANG 6?
- HUA HANG 6 is a cargo ship sailing under the flag of Hong Kong, built in 2007 by Fujian Mawei Shipbuilding. The vessel is 129.6 m long and has a gross tonnage of 7,545.
- What sanctions and inspection records does Voydar hold for HUA HANG 6?
- Voydar has no matched sanctions record displayed for HUA HANG 6 from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for HUA HANG 6. 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/9339040Using 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.