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