From 04:53 on 26 Aug 2026
Scheduled departures
18bNottinghamCT4NPlanned06:50Observed— 18bNottinghamCT4NPlanned07:52Observed— 18bNottinghamCT4NPlanned08:58Observed— 18aNottinghamCT4NPlanned10:00Observed— 18aNottinghamCT4NPlanned11:00Observed— 18aNottinghamCT4NPlanned12:00Observed— 18aNottinghamCT4NPlanned13:00Observed— 34CNottinghamNottingham City TransportPlanned13:35Observed— 18aNottinghamCT4NPlanned14:00Observed— 34CNottinghamNottingham City TransportPlanned14:05Observed— 34CNottinghamNottingham City TransportPlanned14:35Observed— 18aNottinghamCT4NPlanned15:00Observed— 34CNottinghamNottingham City TransportPlanned15:05Observed— 34CNottinghamNottingham City TransportPlanned15:35Observed— 18aNottinghamCT4NPlanned16:00Observed— 34CNottinghamNottingham City TransportPlanned16:05Observed— 34CNottinghamNottingham City TransportPlanned16:35Observed— 18bNottinghamCT4NPlanned17:04Observed— 34CNottinghamNottingham City TransportPlanned17:05Observed— SNNottinghamtrentbartonPlanned17:32Observed— 34CNottinghamNottingham City TransportPlanned17:35Observed— SNNottinghamtrentbartonPlanned17:58Observed— 34CNottinghamNottingham City TransportPlanned18:05Observed— 18bNottinghamCT4NPlanned18:07Observed— SNNottinghamtrentbartonPlanned18:24Observed— 18NottinghamCT4NPlanned18:28Observed— 34CNottinghamNottingham City TransportPlanned18:38Observed— SNNottinghamtrentbartonPlanned18:49Observed— SNNottinghamtrentbartonPlanned19:05Observed— 34CNottinghamNottingham City TransportPlanned19:08Observed— 18bNottinghamCT4NPlanned19:17Observed— 18NottinghamCT4NPlanned19:28Observed— SNNottinghamtrentbartonPlanned19:37Observed— 34CNottinghamNottingham City TransportPlanned19:38Observed— SNNottinghamtrentbartonPlanned19:47Observed— SNNottinghamtrentbartonPlanned20:06Observed— 34CNottinghamNottingham City TransportPlanned20:08Observed— 18NottinghamCT4NPlanned20:25Observed— SNNottinghamtrentbartonPlanned20:26Observed— IGONottinghamtrentbartonPlanned20:34Observed— 34CNottinghamNottingham City TransportPlanned20:38Observed— SNNottinghamtrentbartonPlanned20:46Observed— IGONottinghamtrentbartonPlanned20:49Observed— SNNottinghamtrentbartonPlanned20:57Observed— IGONottinghamtrentbartonPlanned21:04Observed— 34CNottinghamNottingham City TransportPlanned21:08Observed— IGONottinghamtrentbartonPlanned21:19Observed— IGONottinghamtrentbartonPlanned21:34Observed— 34CNottinghamNottingham City TransportPlanned21:38Observed— SNNottinghamtrentbartonPlanned21:47Observed— IGONottinghamtrentbartonPlanned21:49Observed— IGONottinghamtrentbartonPlanned22:04Observed— 34CNottinghamNottingham City TransportPlanned22:08Observed— IGONottinghamtrentbartonPlanned22:19Observed— IGONottinghamtrentbartonPlanned22:34Observed— 34CNottinghamNottingham City TransportPlanned22:38Observed— SNNottinghamtrentbartonPlanned22:47Observed— IGONottinghamtrentbartonPlanned22:49Observed— IGONottinghamtrentbartonPlanned23:04Observed— 34CNottinghamNottingham City TransportPlanned23:08Observed— IGONottinghamtrentbartonPlanned23:19Observed— IGONottinghamtrentbartonPlanned23:34Observed— SNNottinghamtrentbartonPlanned23:47Observed— IGONottinghamtrentbartonPlanned23:49Observed— Scheduled and observed values are kept separate. BustimeFinder does not invent realtime departures when stop-specific observations are absent.