Gatwick Express branded cancellations [19 Feb] and timetable history

[infobleep]

Due to a points failure north of Haywards Heath station in the up direction, fewer trains can run.

Gatwick Express branded trains from Brighton to London Victoria are cancelled between Brighton and Gatwick Airport.

Some are showing as cancelled but earlier others are just not showing at all. When I looked up the 20:39 from Brighton on timetables.trainsplit.com it said Last schedule change 16/08/2023.

Surely if it wasn't showing on the live deapture board, there should be a more recent date for the scheduled change.

It's worth adding that earlier it had cancelled against Brighton and Haywards Heath but now it just shows cancelled against Brighton.

The web page can be found at https://timetables.trainsplit.com/times.aspx?uid=P15908&date=20240219.

It may all be working as intended and it is just that I do not understand how the timetable history works in terms of updates to it.



The first screenshot shows Brighton and Haywards Heath cancelled and the second screenshot shows just Brighton. The last scheduled change is 16/08/2023.

Currently, the journey planner shows no cancellation as can be seen in the screenshot below.

 

[OscarH]

The "history" element only applies to daily timetable updates rather than realtime on-the-day data, and I think this is what the schedule change date will refer to.

My suspicion is they've messed up the cancellation in the realtime system (I've seen GTR do some.. questionable things recently). It does seem odd it differs from NRE, and the stop becoming uncancelled is odd, but could be a data issue

 

[infobleep]

The "history" element only applies to daily timetable updates rather than realtime on-the-day data, and I think this is what the schedule change date will refer to.

My suspicion is they've messed up the cancellation in the realtime system (I've seen GTR do some.. questionable things recently). It does seem odd it differs from NRE, and the stop becoming uncancelled is odd, but could be a data issue

Thanks for explaining that. I like to understand these things. I thought it applied to all changes including on the day.

The train actually ran, although late due to a train in front being late for some reason not given. The previous train was from Littlehampton and lost the time along on the coast. So it wasn't Haywards Heath related disruption.

 

[paul1609]

The Haywards Heath issue was damage to equipment caused during the weekend engineering works which as a result overran. It was temporarily repaired with 1 platform oou.
The Littlehampton train was on time departing LA and arriving at West Worthing but 15 down leaving Worthing for reasons unknown.

 

[infobleep]

The Haywards Heath issue was damage to equipment caused during the weekend engineering works which as a result overran. It was temporarily repaired with 1 platform oou.
The Littlehampton train was on time departing LA and arriving at West Worthing but 15 down leaving Worthing for reasons unknown.

Well I'd like to think someone knew but they didn't tell the public via National Rail Enquiries. That is often but not always the case I find.