More ‘on-time’ train performance data came out recently.

The on-time results for each train company have now been published by Network Rail. They make interesting reading.

Quite a few train companies are achieving pretty good scores. Others have some way to go. All of this flags up interesting issues for Government and industry as the plans for railway from 2014 to 2019 take shape.

The on-time results chime much more closely with the actual passenger experience. For years the Passenger Focus National Passenger Survey has recorded somewhat lower satisfaction with performance than the industry Public Performance Measure, which measures punctuality right at the end of the journey to within five or 10 minutes.

Of course, as the train progresses, passengers experience very different things. Passengers, as we know from our research, have a much keener sense of what ‘on time’ means.

Oddly there seems to be some doubt about the accuracy of some of this newly published data. Not a statement that will instil confidence in passengers.

One comment

  1. Chris Jackson says:

    I have long felt it would be better to measure punctuality at several points along a route – particularly for long-distance trains – rather than simply relying on final arrival at the destination. I understand the Dutch rail industry uses 31 strategically-located locations across the network, particularly the major nodes. That helps to focus attention on junctions and interchanges, where punctuality is important to ensure good connections, as well as assisting in train regulation. Clearly this would require more work at the timetable planning stage in distributing recovery and pathing time accurately along a route, but that should not be impossible with modern tools and recorded train running data.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>