(23 Sep 2025, 8:23 pm)DaveFromUpNorth wrote Looking at 701 service alone at touchdown Hylton road Candlish Road  for today....
It's important to use a single stretch as opposed to a dual stretch to monitor data due to Bustimes deleting and replacing data but as it only goes one way it is better to measure Hylton Road John Candlish Road as a point... 
Schedule 1217  actual 1223 (6m late)
Schedule 1247 actual 1330 (43m late)
Schedule 1347 actual 1401 (21m late)
Schedule 1417 actual 1435. (18m late)
Schedule 1447 actual 1453 ( 6m late)
Schedule 1532 actual 1545 (15m late)
Schedule 1602 actual 1625 (25m late) 
Looking at this and the time of year I am gonna defend City Travel - I do not think they are struggling 
IT IS Fresher month for students so increased loadings until they understand other travel patterns and remember every person asking do you go here can add 20seconds per loading per passenger at least but Looking at the points 
there is good layover to get the service back in order 
I think it is down to passenger loadings as opposed to bus issues when you look closely at the data

From what I can see at least from looking at bustimes, trips were generally running in the region of 10-15 mins late for the most part with the odd one racking up a bit more. Don't believe any were in the region of 40+ mins late, from what I can see, the trip wasn't changed on the ticket machine on some journeys, so it would show as 43 mins late rather than in the region of 10-15 mins as it will show the more recent ping which would be the second round trip when the machine should've been changed.

As to why it was delayed, no idea, can only assume the usual caveats: traffic, passenger loadings, the timetable being a bit tight to stick to, maybe?