From 05:50 on 26 Aug 2026
Scheduled departures
51NLouthTransportConnectPlanned07:20Observed— 51NLouthTransportConnectPlanned08:20Observed— 51NCherry ParkTransportConnectPlanned09:10Observed— 51NLouthTransportConnectPlanned09:20Observed— 51NCherry ParkTransportConnectPlanned10:10Observed— 51NLouthTransportConnectPlanned10:20Observed— 51NCherry ParkTransportConnectPlanned11:10Observed— 51NLouthTransportConnectPlanned11:20Observed— 51NCherry ParkTransportConnectPlanned12:20Observed— 51NLouthTransportConnectPlanned13:00Observed— 51NCherry ParkTransportConnectPlanned13:40Observed— 51NLouthTransportConnectPlanned14:20Observed— 51NCherry ParkTransportConnectPlanned15:10Observed— 51NLouthTransportConnectPlanned15:50Observed— 51NCherry ParkTransportConnectPlanned16:10Observed— 51NLouthTransportConnectPlanned16:50Observed— 51NCherry ParkTransportConnectPlanned17:10Observed— 51NLouthTransportConnectPlanned17:50Observed— 51NCherry ParkTransportConnectPlanned18:10Observed— 51NLouthTransportConnectPlanned18:50Observed— Scheduled and observed values are kept separate. BustimeFinder does not invent realtime departures when stop-specific observations are absent.