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