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