Ruby Princess
Cruise ship · Bermuda · built 2008 · AIS Class A
In short
Ruby Princess (Cruise ship, Bermuda flag) was last seen on AIS on , under way at 12.2 kn, near Ensenada (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 MX ESE (Ensenada), with an ETA of Oct 1, 2026, 17:00 UTC; its reported draught is 8.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 12:17 UTC). Registered owner: Carnival Corporation (source: Wikidata). It can carry up to 3,080 passengers (source: Wikidata).
Current voyage: from Honolulu (departed Sep 24, 2026, 07:41 UTC) to MX ESE (Ensenada)
- Vessel type
- Cruise ship
- Flag
- Bermuda
- Year built
- 2008
- Gross tonnage
- 113,561
- Size (length × beam)
- 288 m × 50 m
- Registered owner
- Carnival Corporation
Watch this ship
Get an email when Ruby 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 Ruby 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.

Last reported position
received- Position
- 31.8041° N, 116.6959° W
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 12.2 kn
- Course
- 65°
- Heading
- 65°
Last 30 days: 1 port call (Honolulu).
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
- Ruby Princess
- IMO numberWhat is an IMO number?
- 9378462
- MMSIWhat is an MMSI?
- 310567000
- Call signWhat is a call sign?
- ZCDY2
- Flag
- Bermuda
- Vessel type
- Detailed type from WikidataCruise ship
- AIS ship type
- Passenger
- Gross tonnageGross tonnage vs deadweight
- 113,561
- Length overall
- 288 m
- Beam
- 50 m
- Year built
- 2008
- Passengers (maximum)
- Source: Wikidata, record Q1626933. Added to Voydar on September 23, 2026. Licence: CC0 1.0.3,080
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
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2024 · 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 HonoluluAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at HonoluluAIS-detected | Voydar port-call detector (AIS geofence) | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Diego, California | USCG PSIX / CGMIX inspections | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Inspection at San Francisco, California | USCG PSIX / CGMIX inspections | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Inspection at San Francisco, California | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Juneau, Alaska | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Ketchikan, Alaska | USCG PSIX / CGMIX inspections | |
| Inspection at Juneau, Alaska | USCG PSIX / CGMIX inspections | |
| Reported departure from Los AngelesAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at Los AngelesAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at Los AngelesAuthority-reported | USACE foreign traffic vessel entrances & clearances |
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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred Jul 6, 2023PassengerNTSB marine investigations (CAROL)San Francisco, CA, USA
Ruby Princess, San Francisco, CA, USA (NTSB DCA23FM040)Report published Nov 21, 2024
The National Transportation Safety Board determines that the probable cause of the contact of the cruise ship Ruby Princess with Port of San Francisco Pier 27 was the master not carrying out the approach to the dock as planned to account for the anticipated current
Source: NTSB marine investigations (CAROL). Courtesy: National Transportation Safety Board. Licence: US Government work (17 U.S.C. §105), public domain.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| May 7, 2026 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Feb 16, 2026 | Vessel InspectionPSC | San Diego, California | clean |
| Dec 12, 2025 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Dec 1, 2025 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Sep 13, 2025 | Vessel Transfer Monitor | San Francisco, California | clean |
| Sep 9, 2025 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Aug 23, 2025 | Vessel Transfer Monitor | San Francisco, California | clean |
| Aug 17, 2025 | Vessel InspectionPSC | Juneau, Alaska | clean |
| Jul 16, 2025 | Vessel InspectionPSC | Ketchikan, Alaska | clean |
| Jul 9, 2025 | Vessel Inspection | Juneau, Alaska | clean |
| Feb 6, 2025 | Vessel InspectionPSC | Honolulu, Hawaii | clean |
| Nov 27, 2024 | Vessel InspectionPSC | San Francisco, California | clean |
| Aug 23, 2024 | Vessel InspectionPSC | Juneau, Alaska | clean |
| May 10, 2024 | Vessel Inspection | Juneau, Alaska | clean |
| May 10, 2024 | Vessel Inspection | Juneau, Alaska | clean |
| Apr 23, 2024 | Vessel Inspection | Juneau, Alaska | clean |
| Mar 9, 2024 | Vessel Inspection | Juneau, Alaska | clean |
| Feb 29, 2024 | Vessel Inspection | Juneau, Alaska | clean |
| Feb 28, 2024 | Vessel InspectionPSC | Miami Beach, Florida | clean |
| Feb 21, 2024 | Vessel Inspection | Miami Beach, Florida | 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.
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 |
|---|---|---|---|---|
| 2023 | 656 t | 206 t | 2 days | 1,474 kg |
| 2024 | 552 t | 174 t | 2 days | 1,372 kg |
Technical efficiency: EEXI (9.91 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 |
|---|---|---|---|
| Honolulu USHNL | Sep 22, 2026, 17:13 UTC | Sep 24, 2026, 07:41 UTC | 38 h 28 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 |
|---|---|---|---|---|
| Los Angeles USLAX | Departure | Dec 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Dec 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Dec 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Dec 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Dec 17, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Dec 17, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Dec 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Dec 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Dec 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Dec 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Nov 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Nov 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: November 4, 2008.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
About Ruby Princess
Ruby Princess is a Crown-class cruise ship operated by Princess Cruises, a subsidiary of Carnival Corporation & plc. At 113,561 GT, the vessel is the third and last in a series of three ships, known as the Crown class, that was built with design modifications distinguishing them from their older Grand-class sister ships. Delivered in 2008 by Italian shipbuilder Fincantieri, Ruby Princess also became the ninth and final Grand-class ship to join the Princess Cruises fleet.
Summary from Wikipedia, licensed CC BY-SA.
Frequently asked questions
- Where is Ruby Princess now?
- Ruby Princess (Cruise ship, Bermuda flag) was last seen on AIS on Oct 1, 2026, 13:07 UTC, under way at 12.2 kn, near Ensenada (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 MX ESE (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 12:17 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Ruby Princess?
- Ruby Princess is a cruise ship sailing under the flag of Bermuda, built in 2008 by Fincantieri. The vessel is 288 m long with a beam of 50 m and has a gross tonnage of 113,561.
- Who is recorded as the owner or manager of Ruby Princess?
- Carnival Corporation is recorded as Registered owner for Ruby Princess (source: Wikidata). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Ruby Princess?
- Voydar has no matched sanctions record displayed for Ruby 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. Ruby 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/9378462Using 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.