From 04:06 on 26 Aug 2026
Scheduled departures
L2Assarts FarmCT4NPlanned06:15Observed— L2Assarts FarmCT4NPlanned06:45Observed— L2Assarts FarmCT4NPlanned07:45Observed— L2Assarts FarmCT4NPlanned08:15Observed— L2Assarts FarmCT4NPlanned08:45Observed— 18aNottinghamCT4NPlanned09:13Observed— L2Assarts FarmCT4NPlanned09:35Observed— 18aNottinghamCT4NPlanned10:13Observed— L2Assarts FarmCT4NPlanned10:35Observed— 18aNottinghamCT4NPlanned11:13Observed— L2Assarts FarmCT4NPlanned11:35Observed— 18aNottinghamCT4NPlanned12:13Observed— L2Assarts FarmCT4NPlanned12:35Observed— 18aNottinghamCT4NPlanned13:13Observed— L2Assarts FarmCT4NPlanned13:35Observed— 18aNottinghamCT4NPlanned14:13Observed— L2Assarts FarmCT4NPlanned14:35Observed— 18aNottinghamCT4NPlanned15:13Observed— L2Assarts FarmCT4NPlanned15:35Observed— L2Assarts FarmCT4NPlanned16:41Observed— L2Assarts FarmCT4NPlanned17:11Observed— L2Assarts FarmCT4NPlanned17:41Observed— L2Assarts FarmCT4NPlanned18:11Observed— L2Assarts FarmCT4NPlanned18:41Observed— Scheduled and observed values are kept separate. BustimeFinder does not invent realtime departures when stop-specific observations are absent.