From 08:41 on 26 Aug 2026
Scheduled departures
SL4Grove ParkBlue TrianglePlanned16:53Observed— SL4Grove ParkBlue TrianglePlanned17:01Observed— SL4Grove ParkBlue TrianglePlanned17:09Observed— SL4Grove ParkBlue TrianglePlanned17:17Observed— SL4Grove ParkBlue TrianglePlanned17:25Observed— SL4Grove ParkBlue TrianglePlanned17:33Observed— SL4Grove ParkBlue TrianglePlanned17:40Observed— SL4Grove ParkBlue TrianglePlanned17:47Observed— SL4Grove ParkBlue TrianglePlanned17:55Observed— SL4Grove ParkBlue TrianglePlanned18:03Observed— SL4Grove ParkBlue TrianglePlanned18:10Observed— SL4Grove ParkBlue TrianglePlanned18:18Observed— SL4Grove ParkBlue TrianglePlanned18:26Observed— SL4Grove ParkBlue TrianglePlanned18:33Observed— SL4Grove ParkBlue TrianglePlanned18:41Observed— SL4Grove ParkBlue TrianglePlanned18:49Observed— SL4Grove ParkBlue TrianglePlanned18:57Observed— SL4Grove ParkBlue TrianglePlanned19:04Observed— SL4Grove ParkBlue TrianglePlanned19:12Observed— SL4Grove ParkBlue TrianglePlanned19:19Observed— Scheduled and observed values are kept separate. BustimeFinder does not invent realtime departures when stop-specific observations are absent.