From 02:13 on 26 Aug 2026
Scheduled departures
18StaplefordCT4NPlanned06:05Observed— 18StaplefordCT4NPlanned06:26Observed— 18StaplefordCT4NPlanned07:26Observed— 18StaplefordCT4NPlanned08:21Observed— 18StaplefordCT4NPlanned09:31Observed— 18StaplefordCT4NPlanned10:31Observed— 18StaplefordCT4NPlanned11:31Observed— 18StaplefordCT4NPlanned12:31Observed— 18StaplefordCT4NPlanned13:31Observed— 18StaplefordCT4NPlanned14:31Observed— 18StaplefordCT4NPlanned15:31Observed— 18StaplefordCT4NPlanned16:31Observed— 18StaplefordNottingham City TransportPlanned16:31Observed— 18XStaplefordCT4NPlanned16:40Observed— 18StaplefordCT4NPlanned17:31Observed— 18StaplefordNottingham City TransportPlanned17:31Observed— 18XStaplefordCT4NPlanned17:40Observed— 18StaplefordCT4NPlanned18:31Observed— 18StaplefordNottingham City TransportPlanned18:31Observed— 18XStaplefordCT4NPlanned18:40Observed— 18StaplefordNottingham City TransportPlanned19:25Observed— 18StaplefordCT4NPlanned19:31Observed— 18StaplefordCT4NPlanned20:13Observed— 18StaplefordNottingham City TransportPlanned20:20Observed— Scheduled and observed values are kept separate. BustimeFinder does not invent realtime departures when stop-specific observations are absent.