From 02:13 on 26 Aug 2026
Scheduled departures
202PeterleeGo North EastPlanned07:06Observed— 202PeterleeGo North EastPlanned07:17Observed— 202PeterleeGo North EastPlanned08:06Observed— 202PeterleeGo North EastPlanned08:17Observed— 202PeterleeGo North EastPlanned09:21Observed— 202PeterleeGo North EastPlanned09:32Observed— 202PeterleeGo North EastPlanned10:21Observed— 202PeterleeGo North EastPlanned10:32Observed— 202PeterleeGo North EastPlanned11:21Observed— 202PeterleeGo North EastPlanned11:32Observed— 202PeterleeGo North EastPlanned12:21Observed— 202PeterleeGo North EastPlanned12:32Observed— 202PeterleeGo North EastPlanned13:21Observed— 202PeterleeGo North EastPlanned13:32Observed— 202PeterleeGo North EastPlanned14:21Observed— 202PeterleeGo North EastPlanned14:32Observed— 202PeterleeGo North EastPlanned15:21Observed— 202PeterleeGo North EastPlanned15:32Observed— 202PeterleeGo North EastPlanned16:36Observed— 202PeterleeGo North EastPlanned16:47Observed— 202PeterleeGo North EastPlanned17:36Observed— 202PeterleeGo North EastPlanned17:47Observed— Scheduled and observed values are kept separate. BustimeFinder does not invent realtime departures when stop-specific observations are absent.