From 02:36 on 26 Aug 2026
Scheduled departures
40SherwoodNottingham City TransportPlanned07:21Observed— 40SherwoodNottingham City TransportPlanned07:46Observed— 56ArnoldNottingham City TransportPlanned08:08Observed— 40SherwoodNottingham City TransportPlanned08:09Observed— 40SherwoodNottingham City TransportPlanned08:41Observed— 40SherwoodNottingham City TransportPlanned09:11Observed— 19SherwoodCT4NPlanned09:34Observed— 19BulwellCT4NPlanned09:36Observed— 59KillisickNottingham City TransportPlanned10:20Observed— 19SherwoodCT4NPlanned10:34Observed— 19BulwellCT4NPlanned10:36Observed— 59KillisickNottingham City TransportPlanned10:50Observed— 59KillisickNottingham City TransportPlanned11:20Observed— 19SherwoodCT4NPlanned11:34Observed— 19BulwellCT4NPlanned11:36Observed— 59KillisickNottingham City TransportPlanned11:50Observed— 59KillisickNottingham City TransportPlanned12:20Observed— 19SherwoodCT4NPlanned12:34Observed— 19BulwellCT4NPlanned12:36Observed— 19SherwoodCT4NPlanned13:34Observed— 19BulwellCT4NPlanned13:36Observed— 19SherwoodCT4NPlanned14:34Observed— 19Top ValleyCT4NPlanned14:36Observed— 40SherwoodNottingham City TransportPlanned14:41Observed— 40SherwoodNottingham City TransportPlanned15:12Observed— CCNottinghamtrentbartonPlanned15:32Observed— 40SherwoodNottingham City TransportPlanned15:42Observed— CCNottinghamtrentbartonPlanned15:47Observed— CCNottinghamtrentbartonPlanned16:02Observed— 40SherwoodNottingham City TransportPlanned16:12Observed— CCNottinghamtrentbartonPlanned16:17Observed— CCNottinghamtrentbartonPlanned16:32Observed— 58KillisickNottingham City TransportPlanned16:36Observed— 40SherwoodNottingham City TransportPlanned16:44Observed— 58KillisickNottingham City TransportPlanned16:46Observed— CCNottinghamtrentbartonPlanned16:47Observed— 58KillisickNottingham City TransportPlanned16:56Observed— CCNottinghamtrentbartonPlanned17:02Observed— 58KillisickNottingham City TransportPlanned17:06Observed— 40SherwoodNottingham City TransportPlanned17:14Observed— 58KillisickNottingham City TransportPlanned17:16Observed— CCNottinghamtrentbartonPlanned17:17Observed— 58KillisickNottingham City TransportPlanned17:26Observed— CCNottinghamtrentbartonPlanned17:32Observed— 58KillisickNottingham City TransportPlanned17:36Observed— 40SherwoodNottingham City TransportPlanned17:45Observed— 58KillisickNottingham City TransportPlanned17:46Observed— CCNottinghamtrentbartonPlanned17:47Observed— 58KillisickNottingham City TransportPlanned17:56Observed— CCEpperstonetrentbartonPlanned18:02Observed— 58KillisickNottingham City TransportPlanned18:05Observed— 40SherwoodNottingham City TransportPlanned18:15Observed— 58KillisickNottingham City TransportPlanned18:15Observed— CCNottinghamtrentbartonPlanned18:17Observed— CCNottinghamtrentbartonPlanned18:31Observed— CCNottinghamtrentbartonPlanned18:51Observed— CCNottinghamtrentbartonPlanned19:10Observed— CCNottinghamtrentbartonPlanned19:38Observed— 59KillisickNottingham City TransportPlanned19:44Observed— CCNottinghamtrentbartonPlanned20:38Observed— CCNottinghamtrentbartonPlanned21:38Observed— CCNottinghamtrentbartonPlanned22:38Observed— CCNottinghamtrentbartonPlanned23:43Observed— Scheduled and observed values are kept separate. BustimeFinder does not invent realtime departures when stop-specific observations are absent.