COSCO Hong Kong
Container ship · United Kingdom · built 2002 · AIS Class A
In short
COSCO Hong Kong (Container ship, United Kingdom flag) was last seen on AIS on , moored, in the port of Port Melbourne. Its crew-entered AIS destination is AUSYD>>AUMEL, with an ETA of Oct 5, 2026, 17:15 UTC; its reported draught is 11.2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 12:52 UTC). It arrived there on Oct 5, 2026, 21:24 UTC.
- Vessel type
- Container ship
- Flag
- United Kingdom
- Year built
- 2002
- Gross tonnage
- 65,531
- Size (length × beam)
- 280 m
- Registered owner
- —
Watch this ship
Get an email when COSCO Hong Kong 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
- 37.8163° S, 144.9126° E
- Area
- Indian Ocean
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 166°
- Heading
- 181°
Last 30 days: 4 port calls (Port Melbourne, Brighton-Le-Sands, Ha Kwai Chung, and Yau Ma Tei).
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
- COSCO Hong Kong
- IMO numberWhat is an IMO number?
- 9227778
- MMSIWhat is an MMSI?
- 235068029
- Call signWhat is a call sign?
- 2BOW2
- Flag
- United Kingdom
- AIS ship type
- Cargo (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- 65,531
- Length overall
- 280 m
- Beam
- —
- Year built
- 2002
United KingdomA 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.
| Date | Event | Source |
|---|---|---|
| Arrived at Port MelbourneAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Brighton-Le-SandsAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Brighton-Le-SandsAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Ha Kwai ChungAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Ha Kwai ChungAIS-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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred Mar 6, 2011merchant-vessel-100-gross-tons-or-over · fishing-vesselUK MAIB investigation reports (index)East China Sea
Collision between container vessel Cosco Hongkong and fish transportation vessel Zhe Ling Yu Yun 135 with loss of 11 livesReport published Feb 29, 2016
Location: East China Sea.
Source: UK MAIB investigation reports (index). Contains public sector information licensed under the Open Government Licence v3.0. Licence: Open Government Licence v3.0.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 7,501 t | 2,404 t | 40 days | 567 kg |
Technical efficiency: EIV (16.73 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
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 |
|---|---|---|---|
| Port Melbourne AUPOR | Oct 5, 2026, 21:24 UTC | in port | — |
| Brighton-Le-Sands AUBSA | Sep 27, 2026, 02:15 UTC | Sep 29, 2026, 19:48 UTC | 2 d 17 h |
| Ha Kwai Chung HKHKC | Sep 14, 2026, 03:53 UTC | Sep 27, 2026, 02:15 UTC | 12 d 22 h |
| Yau Ma Tei HK9YM | Sep 12, 2026, 23:03 UTC | Sep 14, 2026, 03:53 UTC | 28 h 50 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 | Sep 12, 2026, 23:19 UTC | KWAI CHUNG CONTAINER TERMINAL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Aug 2, 2026, 14:52 UTC | KWAICHUNG CONTR. BERTH NO. 11 (TERMINAL 8) | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jun 28, 2026, 00:21 UTC | KC11 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | May 21, 2026, 06:49 UTC | KC11 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Apr 13, 2026, 05:22 UTC | KC11 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Mar 8, 2026, 02:21 UTC | KC13 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Departure(matched by call sign) | Jan 21, 2026, 19:02 UTC | KC11 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Dec 13, 2025, 22:59 UTC | KC13 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Nov 4, 2025, 19:04 UTC | KC12 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Sep 21, 2025, 02:07 UTC | KC | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Aug 18, 2025, 01:21 UTC | KC13 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jul 14, 2025, 07:58 UTC | KC13 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
Records published by the authority named on each row. Earliest record for this ship: March 15, 2006.
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 29, 2026, 18:49 UTC | Draught change Reported draught went from 12.8 m to 11.2 m while in port at Brighton-Le-Sands. 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 COSCO Hong Kong now?
- COSCO Hong Kong (Container ship, United Kingdom flag) was last seen on AIS on Oct 6, 2026, 13:25 UTC, moored, in the port of Port Melbourne. The crew-entered destination was AUSYD>>AUMEL (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 12:52 UTC). This report does not confirm the ship’s current route.
- What kind of ship is COSCO Hong Kong?
- COSCO Hong Kong is a container ship sailing under the flag of United Kingdom, built in 2002. The vessel is 280 m long and has a gross tonnage of 65,531.
- What sanctions and inspection records does Voydar hold for COSCO Hong Kong?
- Voydar has no matched sanctions record displayed for COSCO Hong Kong 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 COSCO Hong Kong. Missing records do not establish whether the ship has been detained.
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9227778Using 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.