Ship vs Port Time

[ViolinKate]

This is our first timing cruising Celebrity. On last cruises, the ship time moved to match the port time, but I'm reading that isn't always the case. We will be on the 2 March Celebrity Reflection and the itinerary and Cruise mapper shows up getting into port at 9am in Aruba . Since this will be a week before Daylight Savings Time, I want to make sure the ship will jump an hour to match. Scheduling a private excursion and they asked us to confirm. 

 

More confusingly, another port calendar (forget which) shows arrival at 8am. Any advice would be welcome. We arrive back in Florida to DST. 

Edited February 17 by ViolinKate

[doghog]

We always go by the ships times for arrival, all aboard and departure.  

[cruisestitch]

About 98% of the time the ship changes time to match the shore time.

[ViolinKate]

3 minutes ago, cruisestitch said:

About 98% of the time the ship changes time to match the shore time.

Thanks 👍

[mnocket]

9 minutes ago, cruisestitch said:

About 98% of the time the ship changes time to match the shore time.

For me it's been 100% of the time. 

[gold1953]

26 minutes ago, mnocket said:

For me it's been 100% of the time. 

I have had it different twice over 19 Celebrity cruises

[Liao]

1 hour ago, ViolinKate said:

This is our first timing cruising Celebrity. On last cruises, the ship time moved to match the port time, but I'm reading that isn't always the case. We will be on the 2 March Celebrity Reflection and the itinerary and Cruise mapper shows up getting into port at 9am in Aruba . Since this will be a week before Daylight Savings Time, I want to make sure the ship will jump an hour to match. Scheduling a private excursion and they asked us to confirm. 

 

More confusingly, another port calendar (forget which) shows arrival at 8am. Any advice would be welcome. We arrive back in Florida to DST. 

In my expereince, it's very rare for a conflict.  I almost always do private excursions as well and have never had a problem.

[mnocket]

30 minutes ago, gold1953 said:

I have had it different twice over 19 Celebrity cruises

I'd imagine it causes some confusion for guests who are on private tours🙃

[mahdnc]

1 hour ago, ViolinKate said:

This is our first timing cruising Celebrity. On last cruises, the ship time moved to match the port time, but I'm reading that isn't always the case. We will be on the 2 March Celebrity Reflection and the itinerary and Cruise mapper shows up getting into port at 9am in Aruba . Since this will be a week before Daylight Savings Time, I want to make sure the ship will jump an hour to match. Scheduling a private excursion and they asked us to confirm. 

 

More confusingly, another port calendar (forget which) shows arrival at 8am. Any advice would be welcome. We arrive back in Florida to DST. 

 

I agree with all the previous answers--it's very rare that the ship's clock will not match the local time.  Our most recent experience with that was during our Galapagos cruise in Nov.  The islands are one hour behind the mainland of Ecuador.  However, Xpedition, which never visits the mainland, had her clock set to mainland time during our entire 7 night Galapagos Islands cruise.

 

As far as Aruba is concerned, we have sailed there on a Celebrity ship (including Reflection) from Florida several times and the ship's clock always matched Aruba's local time.

 

One other thing, Aruba does not observe Daylight Savings Time although that should not be a factor for your cruise.

 

Reflection overnighting at Aruba, Jan 12 2019

Edited February 17 by mahdnc

[Jim_Iain]

Like mentioned above it is rare for the ship to stay on Ship's Time vs Local Time . One that comes to mind is Newfoundland which has a 1/2 hour time zone.      Really was confusing as we had a private tour so one of us kept a watch on ship time and the other land time.  

[mahasamatman]

Newfoundland and Galápagos are the only ones where we've had a difference.

[WestLakeGirl]

It’s happened in Cozumel

[gold1953]

11 minutes ago, WestLakeGirl said:

It’s happened in Cozumel

yes, experienced this one twice