MITSUI OCEAN SAKURA
Cruise ship · Japan · built 2010 · AIS Class A
In short
MITSUI OCEAN SAKURA (Cruise ship, Japan flag) was last seen on AIS on , under way at 17.6 kn, near Kikuma (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 HSM (Hososhima), with an ETA of Oct 4, 2026, 01:30 UTC; its reported draught is 6.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 15:21 UTC). Registered owner: Seabourn Cruise Line (source: Wikidata). It can carry up to 450 passengers (source: Wikidata).
Current voyage: from Yokohama (departed Oct 2, 2026, 08:36 UTC) to >JP HSM (Hososhima)
- Vessel type
- Cruise ship
- Flag
- Japan
- Year built
- 2010
- Gross tonnage
- 32,346
- Size (length × beam)
- 198 m × 26 m
- Registered owner
- Seabourn Cruise Line
Watch this ship
MITSUI OCEAN SAKURA 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.
We email you a link and a code. That creates a free account, no password or card, and follows MITSUI OCEAN SAKURA.
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
- 34.0694° N, 132.8127° E
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 17.6 kn
- Course
- 221°
- Heading
- 222°
Last 30 days: 3 port calls (Yokohama 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)
Try the live demo, no sign-upIdentity & particulars
- Name
- MITSUI OCEAN SAKURA
- IMO numberWhat is an IMO number?
- 9417098
- MMSIWhat is an MMSI?
- 431735000
- Call signWhat is a call sign?
- 7KVW
- Flag
- Japan
- Vessel type
- Cruise ship
- AIS ship type
- Passenger
- Gross tonnageGross tonnage vs deadweight
- 32,346
- Length overall
- 198.2 m
- Beam
- 26 m
- Year built
- 2010
- Passengers (maximum)
- Source: Wikidata, record Q6720033. Added to Voydar on September 23, 2026. Licence: CC0 1.0.450
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
- Operator
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026Holland America Line(not linked to a company record)Source: Wikidata · reported · confidence 0.6 · retrieved Jun 10, 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 TokyoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at TokyoAIS-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 |
|---|---|---|---|---|
| 2019 | 1,601 t | 510 t | 11 days | 661 kg |
| 2022 | 15,278 t | 4,800 t | 106 days | 531 kg |
| 2023 | 18,039 t | 5,695 t | 111 days | 576 kg |
| 2024 | 14,165 t | 4,467 t | 100 days | 500 kg |
| 2025 | 14,132 t | 4,446 t | 96 days | 504 kg |
Technical efficiency: EEXI (14.6 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 | Oct 1, 2026, 23:12 UTC | Oct 2, 2026, 08:36 UTC | 9 h 24 min |
| Tokyo JPTYO | Sep 29, 2026, 22:48 UTC | Sep 30, 2026, 08:12 UTC | 9 h 23 min |
| Yokohama JPYOK | Sep 26, 2026, 23:26 UTC | Sep 27, 2026, 08:42 UTC | 9 h 16 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 | Apr 4, 2026, 00:01 UTC | OT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Apr 13, 2024, 14:36 UTC | OT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Apr 20, 2019, 23:39 UTC | OT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Departure(matched by call sign) | Apr 24, 2018, 15:37 UTC | OT | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Honolulu USHNL | Departure | Jan 14, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Nawiliwili USNIJ | Arrival | Jan 14, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Honolulu USHNL | Departure | Jan 12, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Nawiliwili USNIJ | Arrival | Jan 12, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| OTHER HAWAIIAN ISLANDS AREA PORTS, HAWAII (NET) | Departure | Jan 11, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| OTHER HAWAIIAN ISLANDS AREA PORTS, HAWAII (NET) | Arrival | Jan 11, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Hilo USITO | Departure | Jan 10, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Hilo USITO | Arrival | Jan 10, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: November 16, 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.
About MITSUI OCEAN SAKURA
Seabourn Sojourn is a luxury cruise ship chartered and operated by Seabourn Cruise Line. The ship was ordered for building in the shipyard of T. Mariotti in Genoa, Italy. In 2026, ownership will transfer to Mitsui Ocean Cruises.
Summary from Wikipedia, licensed CC BY-SA.
Frequently asked questions
- Where is MITSUI OCEAN SAKURA now?
- MITSUI OCEAN SAKURA (Cruise ship, Japan flag) was last seen on AIS on Oct 4, 2026, 16:03 UTC, under way at 17.6 kn, near Kikuma (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 HSM (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 15:21 UTC). This report does not confirm the ship’s current route.
- What kind of ship is MITSUI OCEAN SAKURA?
- MITSUI OCEAN SAKURA is a cruise ship sailing under the flag of Japan, built in 2010 by T. Mariotti. The vessel is 198.2 m long with a beam of 26 m and has a gross tonnage of 32,346.
- Who is recorded as the owner or manager of MITSUI OCEAN SAKURA?
- Seabourn Cruise Line is recorded as Registered owner for MITSUI OCEAN SAKURA (source: Wikidata). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for MITSUI OCEAN SAKURA?
- Voydar has no matched sanctions record displayed for MITSUI OCEAN SAKURA 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 MITSUI OCEAN SAKURA. 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/9417098Using 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.