Fuji Galaxy
ship · built 2010
In short
Fuji Galaxy (ship) has no AIS position on record with Voydar.
- Vessel type
- ship
- Flag
- —
- Year built
- 2010
- Gross tonnage
- 16,448
- Size (length × beam)
- 159 m × 27 m
- Registered owner
- —
Watch this ship
Fuji Galaxy has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
No AIS position on record for this vessel. Identity and particulars are 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
- Fuji Galaxy
- IMO numberWhat is an IMO number?
- 9490301
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- ship
- Gross tonnageGross tonnage vs deadweight
- 16,448
- Deadweight (DWT)
- Source: Wikidata, record Q105769484. Added to Voydar on September 23, 2026. Licence: CC0 1.0.26,199 t
- Length overall
- 159 m
- Beam
- 27.1 m
- Year built
- 2010
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 |
|---|---|---|
| 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Feb 24, 2025, 07:51 UTC | SINOPEC | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Oct 21, 2023, 13:26 UTC | SINO | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Mar 24, 2021, 15:03 UTC | SLA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Jul 18, 2019, 03:15 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Seattle USSEA | Arrival | Dec 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Dec 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Richmond USRCH | Departure | Dec 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Richmond USRCH | Arrival | Nov 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Departure | Nov 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF KALAMA, WA | Arrival | Nov 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ANACORTES HARBOR, WA | Departure | Sep 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ANACORTES HARBOR, WA | Arrival | Sep 6, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: September 4, 2010.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is Fuji Galaxy now?
- Voydar has no displayable AIS position for Fuji Galaxy in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Fuji Galaxy?
- Fuji Galaxy is a ship, built in 2010 by Shin Kurushima Dockyard. The vessel is 159 m long with a beam of 27.1 m and has a gross tonnage of 16,448.
- What sanctions and inspection records does Voydar hold for Fuji Galaxy?
- Voydar has no matched sanctions record displayed for Fuji Galaxy 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 Fuji Galaxy. 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/9490301Using 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.