From 02:09 on 26 Aug 2026
Scheduled departures
U1AllestreeNotts and DerbyPlanned07:41Observed— U2AllestreeNotts and DerbyPlanned07:58Observed— U1AllestreeNotts and DerbyPlanned08:41Observed— U2AllestreeNotts and DerbyPlanned08:58Observed— U1AllestreeNotts and DerbyPlanned09:41Observed— U2AllestreeNotts and DerbyPlanned09:58Observed— U1AllestreeNotts and DerbyPlanned10:41Observed— U2AllestreeNotts and DerbyPlanned10:58Observed— U1AllestreeNotts and DerbyPlanned11:41Observed— U2AllestreeNotts and DerbyPlanned11:58Observed— U1AllestreeNotts and DerbyPlanned12:41Observed— U2AllestreeNotts and DerbyPlanned12:58Observed— U1AllestreeNotts and DerbyPlanned13:41Observed— U2AllestreeNotts and DerbyPlanned13:58Observed— U1AllestreeNotts and DerbyPlanned14:41Observed— U2AllestreeNotts and DerbyPlanned14:58Observed— U1AllestreeNotts and DerbyPlanned15:41Observed— U2AllestreeNotts and DerbyPlanned15:58Observed— U1AllestreeNotts and DerbyPlanned16:41Observed— U2AllestreeNotts and DerbyPlanned16:58Observed— U1AllestreeNotts and DerbyPlanned17:41Observed— U2AllestreeNotts and DerbyPlanned17:58Observed— Scheduled and observed values are kept separate. BustimeFinder does not invent realtime departures when stop-specific observations are absent.