Solved

Caledonian Sleeper question



Show first post

34 replies

@Camilo. @Mukhammad 

Any update on these 2 issues? (App doesn't honour travel days in CET but uses local time, which is contrary to the conditions, and how to use the app on night trains in GB, where you are supposed to have a valid travel day for the arrival date).

@rvdborgt @Camilo. @Mukhammad See also my message above. Just got their answer. And it's also on their website, too.

Userlevel 7
Badge +9

@Camilo. @Mukhammad 

Any update on these 2 issues? (App doesn't honour travel days in CET but uses local time, which is contrary to the conditions, and how to use the app on night trains in GB, where you are supposed to have a valid travel day for the arrival date).

@rvdborgt @Camilo. @Mukhammad See also my message above. Just got their answer. And it's also on their website, too.

Thanks, must indeed be recent. That leaves us just with the issue of the app using travel days in local time instead of CET.

Userlevel 7
Badge +4

Huh. They must have changed that very recently!

If that's the case, then the OP would need to use a travel day on the 16th for the sleeper and on the 17th for the onward connections.

And the time zone quirk is irrelevant in this case, since departure from Garelochhead at 2222 local time is still the 16th in CET.

So I think in this case, a paid ticket from Garelochhead-Edinburgh is the only way to avoid using an extra travel day.

Userlevel 5
Badge +3

Hi everyone,

Related to the time zone used on the app, it respects the usage of CET according to the information here. I did my research on trains which operate at night in CET-1 and CET+1 time zones, but I couldn't find any train which goes against the CET time zone's rule.

If it's possible to find the ones which use the local times on the app, please inform me and Camilo here. We'll be able to report it if you find one.

Thank you!

Userlevel 7
Badge +9

Huh. They must have changed that very recently!

If that's the case, then the OP would need to use a travel day on the 16th for the sleeper and on the 17th for the onward connections.

And the time zone quirk is irrelevant in this case, since departure from Garelochhead at 2222 local time is still the 16th in CET.

So I think in this case, a paid ticket from Garelochhead-Edinburgh is the only way to avoid using an extra travel day.

That train does not have a passenger stop at Edinburgh, tickets to/from Edinburgh and splitting like that would not be valid on this train. It is not something I would advise someone to do.

For 16 April, splitting in Dalmuir (departure 23:05 = 0:05 CET) would be good. But indeed no tickets are sold and I suppose no reservation can be made either. Although all planners, including nationalrail.co.uk, display the journey. If passengers are not allowed to do this journey with this train, then that's an error in Caledonian Sleeper’s timetable.

Userlevel 7
Badge +9

Thank you for the search you did on your end. I definitely missed those connections.

Also note that this isn't train-specific. It will be the same for any train:

  1. in the WET zone leaving between 23:00 and 23:59.
  2. in the EET zone leaving between 0:00 and 0:59.
  3. in the TRT zone (Turkey) leaving between 0:00 and 1:59, or between 0:00 and 0:59 when CEST is in effect (probably, I didn't test this).

Thank you for adding the information about the use of time zone. I've been additionally reporting this case.

@Mukhammad any news on this timezone issue? There's still a discrepancy between the app and the conditions of use:

 

I have the same issue with London to Glasgow on the sleeper on 4th April leaving at 2350. My understanding that due to use of CET this should use a travel day of 5th April and I do not want it to use one of my two home travel days for the 4th.

Further it is not possible to elbow this in by putting Watford to Glasgow i.e. a start after midnight local time - it does not recognise this journey and anyway that leaves me paying for London to Watford which I don’t see why I should have to when this is a bug in their app.

Userlevel 5
Badge +3

Thank you for the search you did on your end. I definitely missed those connections.

Also note that this isn't train-specific. It will be the same for any train:

  1. in the WET zone leaving between 23:00 and 23:59.
  2. in the EET zone leaving between 0:00 and 0:59.
  3. in the TRT zone (Turkey) leaving between 0:00 and 1:59, or between 0:00 and 0:59 when CEST is in effect (probably, I didn't test this).

Hi Rian,

Thank you for adding the information about the use of time zone. I've been additionally reporting this case.

 

In addition to that, related to the language bug you found on the App, did you already enable the error logging function?

If yes, please send me your Device ID. I'll raise this issue to the IT dept.

 

Thank you!

Reply