Network Pulse

Journey explorer

← Network Pulse

Every journey on one service on one day, a row each, as it actually ran. Almost every figure this platform publishes is one of these columns summed, so this is the view to read before writing anything down — and the one to open when somebody asks about a particular route.

Days this service did not come in whole

Every day in the last 40 for the service chosen above, with the journeys the timetable scheduled against the journeys we tracked. This section spans days, so the Date filter does not apply to it. Choose a day to see which journeys were missing and, where the evidence reaches, what became of them.

A missing journey is not a cancellation. A journey nobody tracked and a journey that did not run leave the same absence in the table above, which is why tracked matters more than lateness: a mean deviation over 30 stops of 76 describes 30 stops, and the worst-tracked journeys are usually where the reporting is weakest rather than where the buses are. Telling those two apart is what the section below is for, and it can only do it for days the live feed's own run log covered in full — from 15 September 2026. For every day before that the gap can be counted and not explained, and the page says so on the row rather than leaving a blank that reads as nought.