WAN HAI 363
Cargo ship · Singapore · AIS Class A
In short
WAN HAI 363 (Cargo ship, Singapore flag) was last seen on AIS on , not moving, in the port of Bali. Its crew-entered AIS destination is TWKHH (Kaohsiung), with an ETA of Oct 6, 2026, 11:04 UTC; its reported draught is 9.2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 11:06 UTC). It arrived there on Oct 6, 2026, 03:30 UTC.
- Vessel type
- Cargo ship
- Flag
- Singapore
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- Registered owner
- —
Watch this ship
Get an email when WAN HAI 363 reaches Kaohsiung, and when it 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
- 25.164° N, 121.3901° E
- Area
- East China Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0 kn
- Course
- 322°
- Heading
- 245°
Last 30 days: 3 port calls (Bali and Tokyo).
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
- WAN HAI 363
- IMO numberWhat is an IMO number?
- 9930404
- MMSIWhat is an MMSI?
- 563190300
- Call signWhat is a call sign?
- 9V7395
- Flag
- Singapore
- Vessel type
- Cargo ship
- AIS ship type
- Cargo (hazardous cat. B)
- Gross tonnageGross tonnage vs deadweight
- —
- 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.
| Date | Event | Source |
|---|---|---|
| Arrived at BaliAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left TokyoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TokyoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BaliAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BaliAIS-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) | |
| Port State Control inspection at San Pedro, California | USCG PSIX / CGMIX inspections |
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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Mar 23, 2024 | Vessel InspectionPSC | San Pedro, California | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
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 |
|---|---|---|---|
| Bali TWBAL | Oct 6, 2026, 03:30 UTC | in port | — |
| Tokyo JPTYO | Sep 30, 2026, 12:53 UTC | Oct 1, 2026, 12:31 UTC | 23 h 38 min |
| Bali TWBAL | Sep 24, 2026, 02:00 UTC | Sep 24, 2026, 20:10 UTC | 18 h 10 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 3, 2026, 17:44 UTC | KWAICHUNG CONTR. BERTH NO. 3 (TERMINAL 3) | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jul 28, 2026, 17:18 UTC | KWAICHUNG CONTR. BERTH NO. 6 (TERMINAL 4) | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jun 28, 2026, 14:40 UTC | KC10 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jun 3, 2026, 16:55 UTC | POTOI ISLAND | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | May 2, 2026, 09:21 UTC | KC9 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Apr 2, 2026, 15:46 UTC | KC8 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Mar 27, 2026, 11:01 UTC | WAGLAND ISLAND | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Mar 9, 2026, 09:37 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jan 31, 2026, 10:50 UTC | LCS1 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Nov 12, 2024, 08:44 UTC | TSK | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jun 26, 2024, 02:32 UTC | TSK | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jun 5, 2024, 20:17 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: August 19, 2023.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Frequently asked questions
- Where is WAN HAI 363 now?
- WAN HAI 363 (Cargo ship, Singapore flag) was last seen on AIS on Oct 6, 2026, 11:35 UTC, not moving, in the port of Bali. The crew-entered destination was TWKHH (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 11:06 UTC). This report does not confirm the ship’s current route.
- What kind of ship is WAN HAI 363?
- WAN HAI 363 is a cargo ship sailing under the flag of Singapore.
- What sanctions and inspection records does Voydar hold for WAN HAI 363?
- Voydar has no matched sanctions record displayed for WAN HAI 363 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. WAN HAI 363 has 1 recorded Port State Control inspection. Detention and deficiency detail is not recorded for these inspections.
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/9930404Using 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.