berneyarms
Established Member
You need to look at it in detailed mode to compare with the working timetable to understand the reasons why this happened rather than the simple mode. See below.This train departed Penhelig 26m late but arrived at its destination 3 minutes early, two hours later.
Realtime Trains - 1655 Machynlleth to Pwllheli
Realtime Trains provides live realtime running information for the Great British railway network using open data.www.realtimetrains.co.uk
What other examples do you know of where the timetable padding is so extreme that this would be possible?
Realtime Trains - 2J19 1655 Machynlleth to Pwllheli
Realtime Trains provides live realtime running information for the Great British railway network using open data.
On any long single track route, where trains cross with several trains going in the opposite direction along the journey, there will always be additional time added to the standard station stop time to allow for the possibility that one of the trains may be a little late. If you didn't have that, the timetable would self-destruct over the course of the day with constant late running of services and the delays would just keep adding up.
On the Cambrian Coast line that train passed other services at Tywyn and Harlech, where there were scheduled dwells of 5.5 and 7.5 minutes respectively. In both cases the other trains were already in the stations when this train arrived, and it was able to just make quick stops instead. The rest of the savings probably arose due to not making request stops as suggested above.
This specific example is not "padding".