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 13.6 kn, in the 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 USNIJ (Nawiliwili), with an ETA of Nov 16, 2026, 17:00 UTC; its reported draught is 8.8 m (voyage report via AISstream.io global terrestrial AIS, received Nov 16, 2026, 09:52 UTC). Registered owner: Carnival Corporation (source: Wikidata). It can carry up to 3,080 passengers (source: Wikidata).
Current voyage: from Honolulu (departed Nov 16, 2026, 09:50 UTC) to USNIJ (Nawiliwili)
- Vessel type
- Cruise ship
- Flag
- Bermuda
- Year built
- 2008
- Gross tonnage
- 113,561
- Size (length × beam)
- 288 m × 50 m
- Registered owner
- Carnival Corporation

Last reported position: 21.247° N, 158.2086° W · North Pacific Ocean · See on the map
Travelling on Ruby Princess, or someone you know is?
Ruby Princess has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 17, 2026, 16:33 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Ruby Princess reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: Voydar for iPhone
In the news Press-reported
Reports that name Ruby Princess, newest first: the headline, the outlet and a link to the original. Voydar does not copy articles. A report tied to this ship by its IMO number in the text says so; a report that only prints the name is a possible match, because other ships can carry the same name.
What our data shows around Oct 18, 2026
- Ruby Princess’s last AIS position before the report: 20.6293° N, 105.4557° W (North Pacific Ocean), received Oct 18, 2026, 00:02 UTC (20 hours earlier). AIS-detected
- Before the report: left San Francisco on Oct 13, 2026.
- After the report: arrived at San Francisco on Oct 23, 2026.
See the position and 30-day track and the port calls below.
- lineadirectaportal.comOct 18, 2026Possible match
Source: GDELT DOC 2.0 news index. News index: The GDELT Project (https://www.gdeltproject.org/). Licence: GDELT terms (unrestricted use with citation).
Headlines belong to their publishers; Voydar shows the headline and links to the original.
Last reported position
received- Position
- 21.247° N, 158.2086° W
- Area
- North Pacific Ocean
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 13.6 kn
- Course
- 304°
- Heading
- 305°
- Compass: course over ground 304°, heading 305°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 4 port calls (Honolulu and San Francisco).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Ruby Princess's track before the last 30 days. Voydar has recorded its port calls since September 10, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 288 mone tick every 50 m
Beam 50 mPlan outline, to scale
- 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
- 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 October 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 · high confidence · retrieved Nov 15, 2026
- Operator
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2024 · reported · high confidence · retrieved Nov 16, 2026
- Builder
- Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
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) | |
| Left San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| 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.
Compared with ships of its type
Where this ship’s reported CO₂ intensity for 2024 sits among the ships EU MRV lists as “Passenger ship”. Lower is less CO₂.
- CO₂ per nautical mile sailed1,372.3 kg per nautical mile
- Lowest reportedHighest reported
91% of the 207 ships in this group reported a lower figure.
Group: lower quartile 495.6 · median 760.7 · upper quartile 1,085.2
Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated
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 | Nov 15, 2026, 16:23 UTC | Nov 16, 2026, 09:50 UTC | 17 h 27 min |
| San Francisco USSFO | Nov 8, 2026, 13:51 UTC | Nov 9, 2026, 01:18 UTC | 11 h 27 min |
| Honolulu USHNL | Oct 30, 2026, 16:33 UTC | Oct 31, 2026, 09:38 UTC | 17 h 5 min |
| San Francisco USSFO | Oct 23, 2026, 12:44 UTC | Oct 23, 2026, 23:54 UTC | 11 h 11 min |
| San Francisco USSFO | Oct 13, 2026, 13:09 UTC | Oct 13, 2026, 23:01 UTC | 9 h 53 min |
| San Francisco USSFO | Oct 3, 2026, 13:15 UTC | Oct 3, 2026, 23:02 UTC | 9 h 47 min |
| Honolulu USHNL | Sep 22, 2026, 17:13 UTC | Sep 24, 2026, 07:41 UTC | 38 h 28 min |
| San Francisco USSFO | Sep 17, 2026, 13:13 UTC | Sep 17, 2026, 23:19 UTC | 10 h 6 min |
| San Diego USSAN | Sep 14, 2026, 14:14 UTC | Sep 15, 2026, 04:51 UTC | 14 h 37 min |
| Los Angeles USLAX | Sep 13, 2026, 13:26 UTC | Sep 14, 2026, 03:25 UTC | 13 h 59 min |
| Avalon USAOU | Sep 12, 2026, 13:54 UTC | Sep 13, 2026, 01:24 UTC | 11 h 30 min |
| San Francisco USSFO | Sep 10, 2026, 13:48 UTC | Sep 11, 2026, 00:39 UTC | 10 h 51 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
- 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, the New Zealand Russia Sanctions Register and the French national asset-freeze 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.
Full Vessel Report
A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.
Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.
Every fact on this page stays free.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
More Cruise ships
Other cruise ships with full Voydar profiles. A different set each day. All cruise ships
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/9378462Cite this page
Ruby Princess. Voydar (voydar.com). https://www.voydar.com/vessel/9378462-ruby-princess. Retrieved November 17, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.