ASUKA2
Cruise ship · Japan · built 1990 · AIS Class A
In short
ASUKA2 (Cruise ship, Japan flag) was last seen on AIS on , under way at 12 kn, near Yura, Yamaguchi (North Pacific Ocean). 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 JP HKT (Hakata/Fukuoka); its reported draught is 8 m (voyage report via AISstream.io global terrestrial AIS, received Sep 29, 2026, 11:32 UTC). Registered owner: Crystal Cruises (source: Wikidata). It can carry up to 960 passengers (source: Wikidata).
Current voyage: from Yokohama (departed Sep 27, 2026, 08:46 UTC) to JP HKT (Hakata/Fukuoka)
- Vessel type
- Cruise ship
- Flag
- Japan
- Year built
- 1990
- Gross tonnage
- 50,142
- Size (length × beam)
- 241 m × 30 m
- Registered owner
- Crystal Cruises
Watch this ship
Get an email when ASUKA2 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 ASUKA2.
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
- 33.9298° N, 134.9341° E
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 12 kn
- Course
- 189°
- Heading
- 188°
Last 30 days: 2 port calls (Yokohama).
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-upUpcoming ports
Calls published by the ports themselves. ASUKA2 is matched to these schedules by name, not by IMO number, so treat each call as a possible match. Linked by name (the only passenger ship we know by that name), not by IMO number. The port publishes names only, so this may be a different ship.
| Port | Arrives | Departs | From → next |
|---|---|---|---|
| Yokohama | Oct 17, 2026, 09:00 UTC+9 | Oct 17, 2026, 17:00 | 鳥羽 → 種子島 |
| Yokohama | Oct 29, 2026, 09:00 UTC+9 | Oct 29, 2026, 17:00 | 大船渡 → 種子島 |
| Yokohama | Dec 9, 2026, 09:00 UTC+9 | Dec 10, 2026, 17:00 | 佐世保 → 横浜 |
| Yokohama | Dec 11, 2026, 09:00 UTC+9 | Dec 11, 2026, 17:00 | 横浜 → 横浜 |
| Yokohama | Dec 13, 2026, 09:00 UTC+9 | Dec 13, 2026, 17:00 | 横浜 → 横浜 |
| Yokohama | Dec 15, 2026, 09:00 UTC+9 | Dec 15, 2026, 17:00 | 横浜 → 名古屋 |
Identity & particulars
- Name
- ASUKA2
- IMO numberWhat is an IMO number?
- 8806204
- MMSIWhat is an MMSI?
- 432545000
- Call signWhat is a call sign?
- 7JBI
- Flag
- Japan
- Vessel type
- Cruise ship
- AIS ship type
- Passenger
- Gross tonnageGross tonnage vs deadweight
- 50,142
- Deadweight (DWT)
- Source: Wikidata, record Q752399. Added to Voydar on September 23, 2026. Licence: CC0 1.0.8,642 t
- Length overall
- 241 m
- Beam
- 29.6 m
- Year built
- 1990
- Passengers (maximum)
- Source: Wikidata, record Q752399. Added to Voydar on September 23, 2026. Licence: CC0 1.0.960
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.
- Registered owner
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 2026
- 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 YokohamaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at YokohamaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left YokohamaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at YokohamaAIS-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.
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 | 6,898 t | 2,196 t | 26 days | 773 kg |
| 2024 | 5,166 t | 1,646 t | 21 days | 712 kg |
| 2025 | 9,405 t | 3,013 t | 36 days | 686 kg |
Technical efficiency: EIV (126.94 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 |
|---|---|---|---|
| Yokohama JPYOK | Sep 26, 2026, 23:13 UTC | Sep 27, 2026, 08:46 UTC | 9 h 33 min |
| Yokohama JPYOK | Sep 24, 2026, 23:27 UTC | Sep 25, 2026, 08:48 UTC | 9 h 22 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 | Feb 12, 2026, 07:43 UTC | OT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Nov 26, 2019, 00:53 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival(matched by call sign) | Feb 1, 2019, 20:50 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Honolulu USHNL | Departure | Mar 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Honolulu USHNL | Arrival | Mar 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SEWARD HARBOR, AK | Departure | Jul 7, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Juneau USJNU | Arrival | Jul 7, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Juneau USJNU | Departure | Jul 3, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Juneau USJNU | Arrival | Jul 3, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Francisco USSFO | Departure | Jun 27, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Francisco USSFO | Arrival | Jun 27, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Diego USSAN | Departure | Jun 25, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: January 2, 2002.
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.
About ASUKA2
MS Asuka II (飛鳥II) is a cruise ship owned and operated by Nippon Yusen Kaisha, which operates the cruise division NYK Cruises (a.k.a. Asuka Cruise). She was originally built by the Mitsubishi Heavy Industries shipyard in Nagasaki, Japan, as Crystal Harmony for Crystal Cruises. In 2006, Crystal Harmony was transferred from the fleet of Crystal Cruises to that of Crystal's parent company, Nippon Yusen Kaisha, and entered service under her current name. As of August 2022, she was the largest cruise ship in Japan.
Summary from Wikipedia, licensed CC BY-SA.
Frequently asked questions
- Where is ASUKA2 now?
- ASUKA2 (Cruise ship, Japan flag) was last seen on AIS on Sep 29, 2026, 12:54 UTC, under way at 12 kn, near Yura, Yamaguchi (North Pacific Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was JP HKT (voyage report via AISstream.io global terrestrial AIS, received Sep 29, 2026, 11:32 UTC). This report does not confirm the ship’s current route.
- What kind of ship is ASUKA2?
- ASUKA2 is a cruise ship sailing under the flag of Japan, built in 1990 by Mitsubishi Heavy Industries Nagasaki Shipyard & Machinery. The vessel is 241 m long with a beam of 29.6 m and has a gross tonnage of 50,142.
- Who is recorded as the owner or manager of ASUKA2?
- Crystal Cruises is recorded as Registered owner for ASUKA2 (source: Wikidata). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for ASUKA2?
- Voydar has no matched sanctions record displayed for ASUKA2 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 ASUKA2. 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/8806204Using 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.