From 05:41 on 26 Aug 2026
Scheduled departures
SL4Grove ParkBlue TrianglePlanned16:55Observed— SL4Grove ParkBlue TrianglePlanned17:03Observed— SL4Grove ParkBlue TrianglePlanned17:11Observed— SL4Grove ParkBlue TrianglePlanned17:19Observed— SL4Grove ParkBlue TrianglePlanned17:27Observed— SL4Grove ParkBlue TrianglePlanned17:35Observed— SL4Grove ParkBlue TrianglePlanned17:42Observed— SL4Grove ParkBlue TrianglePlanned17:49Observed— SL4Grove ParkBlue TrianglePlanned17:57Observed— SL4Grove ParkBlue TrianglePlanned18:05Observed— SL4Grove ParkBlue TrianglePlanned18:12Observed— SL4Grove ParkBlue TrianglePlanned18:20Observed— SL4Grove ParkBlue TrianglePlanned18:28Observed— SL4Grove ParkBlue TrianglePlanned18:35Observed— SL4Grove ParkBlue TrianglePlanned18:43Observed— SL4Grove ParkBlue TrianglePlanned18:51Observed— SL4Grove ParkBlue TrianglePlanned18:59Observed— SL4Grove ParkBlue TrianglePlanned19:06Observed— SL4Grove ParkBlue TrianglePlanned19:13Observed— SL4Grove ParkBlue TrianglePlanned19:20Observed— Scheduled and observed values are kept separate. BustimeFinder does not invent realtime departures when stop-specific observations are absent.