From 03:29 on 26 Aug 2026
Scheduled departures
L2Assarts FarmCT4NPlanned06:17Observed— L2Assarts FarmCT4NPlanned06:47Observed— L2Assarts FarmCT4NPlanned07:47Observed— L2Assarts FarmCT4NPlanned08:17Observed— L2Assarts FarmCT4NPlanned08:47Observed— 18aNottinghamCT4NPlanned09:14Observed— L2Assarts FarmCT4NPlanned09:38Observed— 18aNottinghamCT4NPlanned10:14Observed— L2Assarts FarmCT4NPlanned10:38Observed— 18aNottinghamCT4NPlanned11:14Observed— L2Assarts FarmCT4NPlanned11:38Observed— 18aNottinghamCT4NPlanned12:14Observed— L2Assarts FarmCT4NPlanned12:38Observed— 18aNottinghamCT4NPlanned13:14Observed— L2Assarts FarmCT4NPlanned13:38Observed— 18aNottinghamCT4NPlanned14:14Observed— L2Assarts FarmCT4NPlanned14:38Observed— 18aNottinghamCT4NPlanned15:14Observed— L2Assarts FarmCT4NPlanned15:38Observed— L2Assarts FarmCT4NPlanned16:43Observed— L2Assarts FarmCT4NPlanned17:13Observed— L2Assarts FarmCT4NPlanned17:43Observed— L2Assarts FarmCT4NPlanned18:13Observed— L2Assarts FarmCT4NPlanned18:43Observed— Scheduled and observed values are kept separate. BustimeFinder does not invent realtime departures when stop-specific observations are absent.