Skip to main content
Otranspo

Route 65

Trip service evidence

Open the totals. See the day, scheduled trip, public feed vehicle ID, and the data gaps that were excluded.

Verifiable timetables for 19 of 30 days

Each date uses an official timetable retained before that service day began. Days without that timetable are not counted as zero trips or as no-shows.

See excluded dates

2026-08-14, 2026-08-15, 2026-08-16, 2026-08-17, 2026-08-18, 2026-08-19, 2026-08-20, 2026-08-21, 2026-08-22, 2026-08-23, 2026-08-24

The JSON download includes source versions, checksums and retrieval times.

Operator cancellation notices saved for this period

These rows record when the operator published CANCELED or DELETED. A notice does not prove the trip stayed cancelled; any later matching vehicle observation is flagged below. Collection starts with this feature’s release, so an empty earlier day means “not retained,” not zero cancellations.

No explicit cancellation statement has been retained for this period. This does not prove that every trip operated.

Open a service day to load its exact settled-arrival timing. The weekly and monthly views keep trip visibility, feed gaps, and vehicle IDs fast instead of making every rider wait for a large archive scan.

Service dateScheduled tripsTrips with a positionNo-position candidatesExcluded for feed gapsPosition coveragePublic feed vehicle IDsArrivals checkedArrivals within 5 minutesAverage delay (+ late, − early)How late the worst 5 in 100 were
Sep 12, 202634 of 34 trip windows had enough operator-feed evidence343400100%29Open this dayOpen this dayOpen this dayOpen this day
Sep 11, 202668 of 68 trip windows had enough operator-feed evidence686800100%30Open this dayOpen this dayOpen this dayOpen this day
Sep 10, 202668 of 68 trip windows had enough operator-feed evidence686800100%31Open this dayOpen this dayOpen this dayOpen this day
Sep 9, 202668 of 68 trip windows had enough operator-feed evidence686800100%32Open this dayOpen this dayOpen this dayOpen this day
Sep 8, 202668 of 68 trip windows had enough operator-feed evidence68635092.6%31Open this dayOpen this dayOpen this dayOpen this day
Sep 7, 202634 of 34 trip windows had enough operator-feed evidence343400100%29Open this dayOpen this dayOpen this dayOpen this day
Sep 6, 202634 of 34 trip windows had enough operator-feed evidence343400100%29Open this dayOpen this dayOpen this dayOpen this day
Sep 5, 202634 of 34 trip windows had enough operator-feed evidence34331097.1%27Open this dayOpen this dayOpen this dayOpen this day
Sep 4, 202664 of 68 trip windows had enough operator-feed evidence68660297.1%28Open this dayOpen this dayOpen this dayOpen this day
Sep 3, 202611 of 68 trip windows had enough operator-feed evidence684002858.8%22Open this dayOpen this dayOpen this dayOpen this day
Sep 2, 202614 of 68 trip windows had enough operator-feed evidence684102760.3%21Open this dayOpen this dayOpen this dayOpen this day
Sep 1, 202618 of 68 trip windows had enough operator-feed evidence68620691.2%28Open this dayOpen this dayOpen this dayOpen this day
Aug 31, 202632 of 68 trip windows had enough operator-feed evidence68581985.3%28Open this dayOpen this dayOpen this dayOpen this day
Aug 30, 202629 of 34 trip windows had enough operator-feed evidence34311291.2%25Open this dayOpen this dayOpen this dayOpen this day
Aug 29, 20266 of 34 trip windows had enough operator-feed evidence341202235.3%11Open this dayOpen this dayOpen this dayOpen this day
Aug 28, 20262 of 68 trip windows had enough operator-feed evidence681705125%9Open this dayOpen this dayOpen this dayOpen this day
Aug 27, 202621 of 68 trip windows had enough operator-feed evidence682903942.6%15Open this dayOpen this dayOpen this dayOpen this day
Aug 26, 20260 of 68 trip windows had enough operator-feed evidence6800680%0Open this dayOpen this dayOpen this dayOpen this day
Aug 25, 202622 of 68 trip windows had enough operator-feed evidence684202661.8%20Open this dayOpen this dayOpen this dayOpen this day

Scheduled-trip detail

Choose a date in the table to see every scheduled trip. Until then, the list focuses on cases that need investigation.

TripScheduled serviceWhat the public evidence saysVehicle ID(s) published by the feedFirst / last observedFeed evidence during this trip
sto:627321702026-09-0814:1114:33No matching position; investigateNone published10 of 11 expected snapshots · 90.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322012026-09-0817:1017:30No matching position; investigateNone published11 of 10 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322122026-09-0817:3517:57No matching position; investigateNone published11 of 11 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322172026-09-0818:1018:27No matching position; investigateNone published10 of 10 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321772026-09-0818:3518:54No matching position; investigateNone published10 of 10 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626982362026-09-0523:3823:55No matching position; investigateNone published10 of 10 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322032026-09-0420:3020:47Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322282026-09-0420:5221:11Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321752026-09-0308:1008:29Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321872026-09-0308:1608:36Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321742026-09-0308:3108:50Excluded: feed incomplete during this tripNone published2 of 10 expected snapshots · 20%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322132026-09-0308:3508:55Excluded: feed incomplete during this tripNone published2 of 10 expected snapshots · 20%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321732026-09-0309:4009:59Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321842026-09-0309:4110:01Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321662026-09-0310:4010:59Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322052026-09-0311:1111:31Excluded: feed incomplete during this tripNone published3 of 10 expected snapshots · 30%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322262026-09-0312:4013:00Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322112026-09-0313:1113:33Excluded: feed incomplete during this tripNone published1 of 11 expected snapshots · 9.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321702026-09-0314:1114:33Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322222026-09-0314:4015:00Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322002026-09-0315:0815:28Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321822026-09-0315:1115:33Excluded: feed incomplete during this tripNone published1 of 11 expected snapshots · 9.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321982026-09-0315:2715:47Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321972026-09-0315:5116:11Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321802026-09-0316:0516:27Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322062026-09-0316:1016:30Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322232026-09-0316:1916:41Excluded: feed incomplete during this tripNone published1 of 11 expected snapshots · 9.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322022026-09-0316:2816:48Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321952026-09-0317:2917:49Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322122026-09-0317:3517:57Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321792026-09-0317:5018:10Excluded: feed incomplete during this tripNone published2 of 10 expected snapshots · 20%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322202026-09-0317:5518:17Excluded: feed incomplete during this tripNone published3 of 11 expected snapshots · 27.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322292026-09-0318:5519:14Excluded: feed incomplete during this tripNone published2 of 10 expected snapshots · 20%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322182026-09-0319:0019:17Excluded: feed incomplete during this tripNone published2 of 10 expected snapshots · 20%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322032026-09-0320:3020:47Excluded: feed incomplete during this tripNone published2 of 10 expected snapshots · 20%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322152026-09-0323:3023:47Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321742026-09-0208:3108:50Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322132026-09-0208:3508:55Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321652026-09-0208:5009:09Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321692026-09-0208:5509:15Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321712026-09-0209:1009:29Excluded: feed incomplete during this tripNone published2 of 10 expected snapshots · 20%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322042026-09-0209:1509:35Excluded: feed incomplete during this tripNone published2 of 10 expected snapshots · 20%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321862026-09-0210:1110:31Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321992026-09-0213:4014:00Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321702026-09-0214:1114:33Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322222026-09-0214:4015:00Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322002026-09-0215:0815:28Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321822026-09-0215:1115:33Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321982026-09-0215:2715:47Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322072026-09-0215:4416:06Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321972026-09-0215:5116:11Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321802026-09-0216:0516:27Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322062026-09-0216:1016:30Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322232026-09-0216:1916:41Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322022026-09-0216:2816:48Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322142026-09-0216:4117:03Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321962026-09-0216:5017:10Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321832026-09-0217:0117:23Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322012026-09-0217:1017:30Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321682026-09-0217:1517:37Excluded: feed incomplete during this tripNone published1 of 11 expected snapshots · 9.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321952026-09-0217:2917:49Excluded: feed incomplete during this tripNone published2 of 10 expected snapshots · 20%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322182026-09-0219:0019:17Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322282026-09-0220:5221:11Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322232026-09-0116:1916:41Excluded: feed incomplete during this tripNone published4 of 11 expected snapshots · 36.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321792026-09-0117:5018:10Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322202026-09-0117:5518:17Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322172026-09-0118:1018:27Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321852026-09-0118:1518:34Excluded: feed incomplete during this tripNone published2 of 10 expected snapshots · 20%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321782026-09-0118:3018:47Excluded: feed incomplete during this tripNone published5 of 10 expected snapshots · 50%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321842026-08-3109:4110:01Excluded: feed incomplete during this tripNone published4 of 10 expected snapshots · 40%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322012026-08-3117:1017:30Excluded: feed incomplete during this tripNone published2 of 10 expected snapshots · 20%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321682026-08-3117:1517:37Excluded: feed incomplete during this tripNone published3 of 11 expected snapshots · 27.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322122026-08-3117:3517:57Excluded: feed incomplete during this tripNone published7 of 11 expected snapshots · 63.6%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322172026-08-3118:1018:27Excluded: feed incomplete during this tripNone published7 of 10 expected snapshots · 70%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321772026-08-3118:3518:54Excluded: feed incomplete during this tripNone published6 of 10 expected snapshots · 60%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322182026-08-3119:0019:17No matching position; investigateNone published8 of 10 expected snapshots · 80%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322032026-08-3120:3020:47Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322282026-08-3120:5221:11Excluded: feed incomplete during this tripNone published4 of 10 expected snapshots · 40%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322152026-08-3123:3023:47Excluded: feed incomplete during this tripNone published6 of 10 expected snapshots · 60%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627738602026-08-3009:3809:55Excluded: feed incomplete during this tripNone published4 of 10 expected snapshots · 40%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627754402026-08-3020:3820:55No matching position; investigateNone published10 of 10 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627755752026-08-3021:4622:03Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626974262026-08-2909:4610:03Excluded: feed incomplete during this tripNone published4 of 10 expected snapshots · 40%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626973532026-08-2911:4612:03Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626973832026-08-2912:3812:55Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626974882026-08-2912:4613:03Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626975262026-08-2913:3813:55Excluded: feed incomplete during this tripNone published3 of 10 expected snapshots · 30%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626976542026-08-2913:4614:03Excluded: feed incomplete during this tripNone published4 of 10 expected snapshots · 40%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626977852026-08-2915:3815:55Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626977982026-08-2915:4616:03Excluded: feed incomplete during this tripNone published1 of 10 expected snapshots · 10%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626978482026-08-2916:3816:55Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626978612026-08-2916:4617:03Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626979162026-08-2917:3817:55Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626979242026-08-2917:4618:03Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626981332026-08-2918:3818:55Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626979982026-08-2918:4619:03Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626980282026-08-2919:3819:55Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626980062026-08-2919:4620:03Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626980982026-08-2920:3820:55Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626980602026-08-2920:4621:03Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626981042026-08-2921:3821:55Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626981202026-08-2921:4622:03Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626981762026-08-2922:3822:55Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626981742026-08-2922:4623:03Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321942026-08-2805:1005:29Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321882026-08-2805:3305:53Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321762026-08-2805:4005:59Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322212026-08-2806:0306:23Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321642026-08-2806:1006:29Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322102026-08-2806:3006:49Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322272026-08-2806:3506:55Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321632026-08-2806:5007:09Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321902026-08-2806:5507:15Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321672026-08-2807:0807:27Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321912026-08-2807:1407:34Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322092026-08-2807:3107:50Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322252026-08-2807:3507:55Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322192026-08-2807:5308:12Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321892026-08-2807:5708:17Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321752026-08-2808:1008:29Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321872026-08-2808:1608:36Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321742026-08-2808:3108:50Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322132026-08-2808:3508:55Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321652026-08-2808:5009:09Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321692026-08-2808:5509:15Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321712026-08-2809:1009:29Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322042026-08-2809:1509:35Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321732026-08-2809:4009:59Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321842026-08-2809:4110:01Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321862026-08-2810:1110:31Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321662026-08-2810:4010:59Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322052026-08-2811:1111:31Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321722026-08-2811:4011:59Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321812026-08-2812:1112:33Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322262026-08-2812:4013:00Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322112026-08-2813:1113:33Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321992026-08-2813:4014:00Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321702026-08-2814:1114:33Excluded: feed incomplete during this tripNone published4 of 11 expected snapshots · 36.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321982026-08-2815:2715:47Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322072026-08-2815:4416:06Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321972026-08-2815:5116:11Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321802026-08-2816:0516:27Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322062026-08-2816:1016:30Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322232026-08-2816:1916:41Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322022026-08-2816:2816:48Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322142026-08-2816:4117:03Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321962026-08-2816:5017:10Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321832026-08-2817:0117:23Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627322012026-08-2817:1017:30Excluded: feed incomplete during this tripNone published0 of 10 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627321682026-08-2817:1517:37Excluded: feed incomplete during this tripNone published0 of 11 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
What these labels mean
Trip seen in the feed
A public vehicle observation overlaps this trip’s scheduled window. IDs match exactly, or an OC numeric timetable suffix is reconciled to one unique live trip on this route and date. Both trip IDs and the matching rule are included in the download.
Missing position to investigate
No public vehicle position matched the scheduled trip, and that trip’s own scheduled window had at least 75% of the expected operator-feed snapshots with observations near both ends. This needs investigation and is not proof of cancellation.
Missing data, not a missing bus
The trip window lacks enough operator-specific archive coverage, or a live trip ID cannot be assigned to one unique scheduled trip. It is excluded from missing-service counts.
Public vehicle identifier
An identifier published by the realtime feed. It may change and is not necessarily a verified physical fleet number.
Operator-confirmed cancellation
Historical cancellation is published only when a retained operator trip update explicitly marks it cancelled or deleted. Position absence alone is never relabelled as cancellation.
Which timetable was used?
Each date uses the latest retained official timetable fetched before that Toronto service day began. Days without such a timetable are not counted as zero service or as no-shows. Source version IDs, checksums and fetch times are included in the JSON download.