Skip to content

Diamond Princess

Cruise ship · Bermuda · built 2004 · AIS Class A

IMO9228198MMSI310866000Call signZCHI3Last AIS position Oct 1, 2026, 20:32 UTC

In short

Diamond Princess (Cruise ship, Bermuda flag) was last seen on AIS on , under way at 13.5 kn, near Atsumi (North Pacific Ocean). Its crew-entered AIS destination is JP TOB (Toba), with an ETA of Oct 1, 2026, 20:00 UTC; its reported draught is 8.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 12:42 UTC). Registered owner: Carnival Corporation (source: Wikidata). It can carry up to 2,670 passengers (source: Wikidata).

Current voyage: from Yokohama (departed Oct 1, 2026, 06:27 UTC) to JP TOB (Toba)

Vessel type
Cruise ship
Year built
2004
Gross tonnage
115,906
Size (length × beam)
290 m × 38 m
Registered owner
Carnival Corporation

Watch this ship

Get an email when Diamond Princess 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 Diamond Princess.

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.

Photo of DIAMOND PRINCESS
Photo: Barrylb · Licence: Public domain · via Wikimedia Commons

Last reported position

received
Position
34.5612° N, 137.0105° E
Area
North Pacific Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
13.5 kn
Course
315°
Heading
315°
34.5612° N, 137.0105° E
Open the full live map →

Last 30 days: 2 port calls (Yokohama and Keelung (Chilung)).

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-up

Upcoming ports

Calls published by the ports themselves. DIAMOND PRINCESS 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.

PortArrivesDepartsFrom → next
YokohamaOct 10, 2026, 06:30 UTC+9Oct 10, 2026, 15:00長崎 → 秋田
YokohamaOct 19, 2026, 06:30 UTC+9Oct 19, 2026, 15:00長崎 → 長崎
YokohamaOct 28, 2026, 06:30 UTC+9Oct 28, 2026, 15:00清水 → 函館
YokohamaNov 11, 2026, 06:30 UTC+9Nov 11, 2026, 15:00御前崎 → 青森
YokohamaNov 25, 2026, 06:30 UTC+9Nov 25, 2026, 15:00清水 → 鹿児島

出典:横浜市港湾局「横浜港客船入港情報」 Retrieved October 1, 2026.

Identity & particulars

Name
Diamond Princess
IMO numberWhat is an IMO number?
9228198
MMSIWhat is an MMSI?
310866000
Call signWhat is a call sign?
ZCHI3
AIS ship type
Passenger
Gross tonnageGross tonnage vs deadweight
115,906
Length overall
290 m
Beam
37.5 m
Year built
2004

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, 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.

DateEventSource
Left YokohamaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at YokohamaAIS-detectedVoydar port-call detector (AIS geofence)
Left Keelung (Chilung)AIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Keelung (Chilung)AIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Inspection at FPO, Armed Forces PacificUSCG PSIX / CGMIX inspections
Port State Control inspection at San Pedro, CaliforniaUSCG PSIX / CGMIX inspections
Port State Control inspection at Juneau, AlaskaUSCG PSIX / CGMIX inspections
Inspection at WASHINGTON, District of ColumbiaUSCG PSIX / CGMIX inspections
Inspection at WASHINGTON, District of ColumbiaUSCG PSIX / CGMIX inspections
Inspection at WASHINGTON, District of ColumbiaUSCG PSIX / CGMIX inspections
Inspection at WASHINGTON, District of ColumbiaUSCG PSIX / CGMIX inspections
Inspection at WASHINGTON, District of ColumbiaUSCG PSIX / CGMIX inspections
Inspection at WASHINGTON, District of ColumbiaUSCG PSIX / CGMIX inspections
Port State Control inspection at Juneau, AlaskaUSCG 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

50
Inspections
not recorded
Detentions
0
Deficiencies
DateTypePortFindings
Mar 3, 2023BoardingFPO, Armed Forces Pacificclean
Nov 9, 2022Vessel InspectionPSCSan Pedro, Californiaclean
Sep 16, 2013Vessel InspectionPSCJuneau, Alaskaclean
Aug 29, 2013Incident InvestigationWASHINGTON, District of Columbiaclean
Aug 12, 2013Incident InvestigationWASHINGTON, District of Columbiaclean
Jul 22, 2013Incident InvestigationWASHINGTON, District of Columbiaclean
Jun 27, 2013Incident InvestigationWASHINGTON, District of Columbiaclean
Jun 3, 2013Incident InvestigationWASHINGTON, District of Columbiaclean
May 23, 2013Incident InvestigationWASHINGTON, District of Columbiaclean
May 22, 2013Vessel InspectionPSCJuneau, Alaskaclean
May 18, 2013Vessel InspectionPSCJBER, Alaskaclean
Sep 12, 2012Vessel InspectionJuneau, Alaskaclean
Sep 10, 2012Incident InvestigationWASHINGTON, District of Columbiaclean
Sep 9, 2012Incident InvestigationWASHINGTON, District of Columbiaclean
Aug 8, 2012Incident InvestigationWASHINGTON, District of Columbiaclean
Jul 19, 2012Vessel InspectionPSCJuneau, Alaskaclean
Jul 11, 2012Incident InvestigationWASHINGTON, District of Columbiaclean
Jul 4, 2012Incident InvestigationWASHINGTON, District of Columbiaclean
Jun 28, 2012Incident InvestigationWASHINGTON, District of Columbiaclean
Jun 20, 2012Incident InvestigationWASHINGTON, District of Columbiaclean

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

PortArrivedDepartedTime in port
Yokohama JPYOKSep 30, 2026, 21:16 UTCOct 1, 2026, 06:27 UTC9 h 12 min
Keelung (Chilung) TWKELSep 25, 2026, 22:29 UTCSep 26, 2026, 10:48 UTC12 h 19 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

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrivalFeb 16, 2026, 21:07 UTCKTCTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Dec 1, 2025, 23:01 UTCKTCTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalMar 6, 2025, 19:35 UTCKTCTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Sep 10, 2024, 22:57 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Mar 10, 2024, 00:08 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Dec 7, 2023, 22:51 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Jan 24, 2020, 22:43 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalJan 11, 2020, 22:59 UTCKTCTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrivalDec 29, 2019, 22:49 UTCKTCTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Oct 23, 2019, 23:06 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Feb 6, 2019, 22:44 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKGArrival(matched by call sign)Dec 13, 2018, 22:45 UTCWLHong Kong vessel arrivals & departures (incl. VTMS daily reports)

Records published by the authority named on each row. Earliest record for this ship: March 10, 2004.

Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.

About Diamond Princess

Diamond Princess is a British-registered cruise ship owned and operated by Princess Cruises. She began operation in March 2004 and primarily cruises in Asia during the northern hemisphere summer and Australia during the southern hemisphere summer. She is a subclassed Grand-class ship, which is also known as a Gem-class ship. Diamond Princess and her sister ship, Sapphire Princess, are the widest subclass of Grand-class ships, as they have a 37.5-metre (123 ft 0 in) beam, while all other Grand-class ships have a beam of 36 metres (118 ft 1 in). Diamond Princess and Sapphire Princess were both built in Nagasaki, Japan, by Mitsubishi Industries. There have been two notable outbreaks of infectious disease on the ship – an outbreak of gastroenteritis caused by norovirus in 2016 and an outbreak of COVID-19 caused by SARS-CoV-2 in 2020.

Summary from Wikipedia, licensed CC BY-SA.

Frequently asked questions

Where is Diamond Princess now?
Diamond Princess (Cruise ship, Bermuda flag) was last seen on AIS on Oct 1, 2026, 20:32 UTC, under way at 13.5 kn, near Atsumi (North Pacific Ocean). The crew-entered destination was JP TOB (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 12:42 UTC). This report does not confirm the ship’s current route.
What kind of ship is Diamond Princess?
Diamond Princess is a cruise ship sailing under the flag of Bermuda, built in 2004 by Mitsubishi Heavy Industries. The vessel is 290 m long with a beam of 37.5 m and has a gross tonnage of 115,906.
Who is recorded as the owner or manager of Diamond Princess?
Carnival Corporation is recorded as Registered owner for Diamond Princess (source: Wikidata). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Diamond Princess?
Voydar has no matched sanctions record displayed for Diamond Princess from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. Diamond Princess has 50 recorded Port State Control inspections. 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/9228198
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using 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.

See plans