From 04:53 on 26 Aug 2026
Scheduled departures
58AKillisickNottingham City TransportPlanned05:43Observed— 53BArnoldNottingham City TransportPlanned05:58Observed— 58AKillisickNottingham City TransportPlanned06:13Observed— 53BArnoldNottingham City TransportPlanned06:28Observed— 53BArnoldNottingham City TransportPlanned06:55Observed— 53BArnoldNottingham City TransportPlanned07:18Observed— 58AKillisickNottingham City TransportPlanned07:31Observed— 53BArnoldNottingham City TransportPlanned07:38Observed— 53BArnoldNottingham City TransportPlanned08:03Observed— 58AKillisickNottingham City TransportPlanned08:06Observed— 53BArnoldNottingham City TransportPlanned08:35Observed— 53BArnoldNottingham City TransportPlanned09:08Observed— 53BArnoldNottingham City TransportPlanned09:38Observed— 54ArnoldNottingham City TransportPlanned10:36Observed— 54ArnoldNottingham City TransportPlanned11:36Observed— 54ArnoldNottingham City TransportPlanned12:36Observed— 54ArnoldNottingham City TransportPlanned13:36Observed— 54ArnoldNottingham City TransportPlanned14:36Observed— 25BArnoldNottingham City TransportPlanned14:43Observed— CCNottinghamtrentbartonPlanned15:40Observed— 54ArnoldNottingham City TransportPlanned15:41Observed— CCNottinghamtrentbartonPlanned15:55Observed— CCNottinghamtrentbartonPlanned16:10Observed— CCNottinghamtrentbartonPlanned16:25Observed— CCNottinghamtrentbartonPlanned16:40Observed— 58KillisickNottingham City TransportPlanned16:43Observed— 54ArnoldNottingham City TransportPlanned16:48Observed— 58KillisickNottingham City TransportPlanned16:53Observed— CCNottinghamtrentbartonPlanned16:55Observed— 58KillisickNottingham City TransportPlanned17:03Observed— CCNottinghamtrentbartonPlanned17:10Observed— 58KillisickNottingham City TransportPlanned17:13Observed— 58KillisickNottingham City TransportPlanned17:23Observed— CCNottinghamtrentbartonPlanned17:25Observed— 53BArnoldNottingham City TransportPlanned17:28Observed— 58KillisickNottingham City TransportPlanned17:33Observed— CCNottinghamtrentbartonPlanned17:40Observed— 58KillisickNottingham City TransportPlanned17:43Observed— 58KillisickNottingham City TransportPlanned17:53Observed— 53BArnoldNottingham City TransportPlanned17:54Observed— CCNottinghamtrentbartonPlanned17:55Observed— 58KillisickNottingham City TransportPlanned18:03Observed— CCEpperstonetrentbartonPlanned18:09Observed— 58KillisickNottingham City TransportPlanned18:11Observed— 53BArnoldNottingham City TransportPlanned18:19Observed— 58KillisickNottingham City TransportPlanned18:21Observed— CCNottinghamtrentbartonPlanned18:23Observed— CCNottinghamtrentbartonPlanned18:37Observed— 53BArnoldNottingham City TransportPlanned18:44Observed— CCNottinghamtrentbartonPlanned18:57Observed— CCNottinghamtrentbartonPlanned19:15Observed— CCNottinghamtrentbartonPlanned19:43Observed— CCNottinghamtrentbartonPlanned20:43Observed— 25BArnoldNottingham City TransportPlanned20:49Observed— 25BArnoldNottingham City TransportPlanned21:19Observed— CCNottinghamtrentbartonPlanned21:43Observed— 25BArnoldNottingham City TransportPlanned21:49Observed— CCNottinghamtrentbartonPlanned22:43Observed— CCNottinghamtrentbartonPlanned23:48Observed— Scheduled and observed values are kept separate. BustimeFinder does not invent realtime departures when stop-specific observations are absent.