From 01:33 on 26 Aug 2026
Scheduled departures
30 shown4SStamfordTransportConnectPlanned07:18Observed— 4SStamfordTransportConnectPlanned08:18Observed— 4SStamfordTransportConnectPlanned09:18Observed— 4PKings CliffeTransportConnectPlanned09:45Observed— 4SStamfordTransportConnectPlanned10:18Observed— 4PKings CliffeTransportConnectPlanned10:45Observed— 4SStamfordTransportConnectPlanned11:18Observed— 4SFotheringhayTransportConnectPlanned11:42Observed— 4PKings CliffeTransportConnectPlanned11:45Observed— 4SStamfordTransportConnectPlanned12:18Observed— 4SFotheringhayTransportConnectPlanned12:42Observed— 4PKings CliffeTransportConnectPlanned12:45Observed— 4SStamfordTransportConnectPlanned13:18Observed— 4SFotheringhayTransportConnectPlanned13:42Observed— 4PKings CliffeTransportConnectPlanned13:45Observed— 4SStamfordTransportConnectPlanned14:18Observed— 4SFotheringhayTransportConnectPlanned14:42Observed— 4PKings CliffeTransportConnectPlanned14:45Observed— 4SStamfordTransportConnectPlanned15:18Observed— 4SFotheringhayTransportConnectPlanned15:42Observed— 4PKings CliffeTransportConnectPlanned15:45Observed— 4SStamfordTransportConnectPlanned16:18Observed— 4SFotheringhayTransportConnectPlanned16:42Observed— 4PKings CliffeTransportConnectPlanned16:45Observed— 4SStamfordTransportConnectPlanned17:18Observed— 4SFotheringhayTransportConnectPlanned17:42Observed— 4PKings CliffeTransportConnectPlanned17:45Observed— 4SStamfordTransportConnectPlanned18:18Observed— 4SFotheringhayTransportConnectPlanned18:42Observed— 4PKings CliffeTransportConnectPlanned18:45Observed— Scheduled and observed values are kept separate. BustimeFinder does not invent realtime departures when stop-specific observations are absent.