Skip to main content
Otranspo

Route 49

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 20 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-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.

  • sto:627311872026-09-09 · CANCELED · None publishedSep 9, 2026, 7:03 p.m.
  • sto:627312992026-09-09 · CANCELED · None publishedSep 9, 2026, 6:52 p.m.
  • sto:627311872026-09-08 · CANCELED · None publishedSep 8, 2026, 7:04 p.m.
  • sto:627302312026-09-04 · CANCELED · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Sep 4, 2026, 11:09 a.m.
  • sto:627315432026-09-04 · CANCELED · None publishedSep 4, 2026, 11:18 a.m.
  • sto:627311872026-09-03 · CANCELED · None publishedSep 3, 2026, 7:03 p.m.
  • sto:627312992026-09-01 · CANCELED · None publishedSep 1, 2026, 6:52 p.m.

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 13, 202622 of 34 trip windows had enough operator-feed evidence341931255.9%11Open this dayOpen this dayOpen this dayOpen this day
Sep 12, 202634 of 34 trip windows had enough operator-feed evidence343400100%19Open this dayOpen this dayOpen this dayOpen this day
Sep 11, 202672 of 72 trip windows had enough operator-feed evidence727200100%52Open this dayOpen this dayOpen this dayOpen this day
Sep 10, 202672 of 72 trip windows had enough operator-feed evidence72702097.2%52Open this dayOpen this dayOpen this dayOpen this day
Sep 9, 202672 of 72 trip windows had enough operator-feed evidence72693095.8%53Open this dayOpen this dayOpen this dayOpen this day
Sep 8, 202672 of 72 trip windows had enough operator-feed evidence72702097.2%52Open this dayOpen this dayOpen this dayOpen this day
Sep 7, 202634 of 34 trip windows had enough operator-feed evidence343400100%20Open this dayOpen this dayOpen this dayOpen this day
Sep 6, 202634 of 34 trip windows had enough operator-feed evidence34331097.1%19Open this dayOpen this dayOpen this dayOpen this day
Sep 5, 202634 of 34 trip windows had enough operator-feed evidence343400100%21Open this dayOpen this dayOpen this dayOpen this day
Sep 4, 202667 of 72 trip windows had enough operator-feed evidence72682294.4%50Open this dayOpen this dayOpen this dayOpen this day
Sep 3, 202611 of 72 trip windows had enough operator-feed evidence725801480.6%43Open this dayOpen this dayOpen this dayOpen this day
Sep 2, 202613 of 72 trip windows had enough operator-feed evidence725701579.2%45Open this dayOpen this dayOpen this dayOpen this day
Sep 1, 202624 of 72 trip windows had enough operator-feed evidence72710198.6%50Open this dayOpen this dayOpen this dayOpen this day
Aug 31, 202631 of 72 trip windows had enough operator-feed evidence72710198.6%54Open this dayOpen this dayOpen this dayOpen this day
Aug 30, 202628 of 34 trip windows had enough operator-feed evidence343400100%18Open this dayOpen this dayOpen this dayOpen this day
Aug 29, 20265 of 34 trip windows had enough operator-feed evidence341801652.9%13Open this dayOpen this dayOpen this dayOpen this day
Aug 28, 20261 of 72 trip windows had enough operator-feed evidence722304931.9%20Open this dayOpen this dayOpen this dayOpen this day
Aug 27, 202625 of 72 trip windows had enough operator-feed evidence724103156.9%31Open this dayOpen this dayOpen this dayOpen this day
Aug 26, 20260 of 72 trip windows had enough operator-feed evidence7200720%0Open this dayOpen this dayOpen this dayOpen this day
Aug 25, 202628 of 72 trip windows had enough operator-feed evidence725002269.4%36Open 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:627185802026-09-1307:0707:54Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627197752026-09-1307:1007:59Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627197762026-09-1308:0708:54Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627185792026-09-1308:1008:59Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627185812026-09-1309:0709:56Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627197732026-09-1309:1009:59Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627197742026-09-1310:0710:56Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627191532026-09-1310:1011:02Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627189782026-09-1311:0711:56Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627185732026-09-1311:1012:02Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627189362026-09-1312:0712:57Excluded: feed incomplete during this tripNone published2 of 16 expected snapshots · 12.5%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627183242026-09-1312:1013:04Excluded: feed incomplete during this tripNone published3 of 17 expected snapshots · 17.6%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627198882026-09-1321:0721:54No matching position; investigateNone published15 of 16 expected snapshots · 93.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627199982026-09-1322:1022:58No matching position; investigateNone published16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627200672026-09-1323:0723:52No matching position; investigateNone published12 of 15 expected snapshots · 80%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627305322026-09-1014:5515:56No matching position; investigateNone published19 of 19 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627303862026-09-1015:5516:56No matching position; investigateNone published19 of 19 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627315432026-09-0910:2511:18No matching position; investigateNone published17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627312992026-09-0917:5518:52No matching position; investigateNone published18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627311872026-09-0918:0519:04No matching position; investigateNone published18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627315432026-09-0810:2511:18No matching position; investigateNone published17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627311872026-09-0818:0519:04No matching position; investigateNone published18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627191532026-09-0610:1011:02No matching position; investigateNone published17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627315552026-09-0413:3414:32No matching position; investigateNone published18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304332026-09-0416:0517:18No matching position; investigateNone published20 of 21 expected snapshots · 95.2%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307252026-09-0420:2421:13Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306962026-09-0420:4121:39Excluded: feed incomplete during this tripNone published4 of 18 expected snapshots · 22.2%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627313192026-09-0307:5808:44Excluded: feed incomplete during this tripNone published2 of 16 expected snapshots · 12.5%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627310402026-09-0308:0509:09Excluded: feed incomplete during this tripNone published3 of 19 expected snapshots · 15.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306062026-09-0309:2110:14Excluded: feed incomplete during this tripNone published1 of 17 expected snapshots · 5.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627301852026-09-0310:3511:33Excluded: feed incomplete during this tripNone published3 of 18 expected snapshots · 16.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627302772026-09-0312:2513:18Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304742026-09-0312:3513:33Excluded: feed incomplete during this tripNone published1 of 18 expected snapshots · 5.6%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304302026-09-0312:5513:48Excluded: feed incomplete during this tripNone published2 of 17 expected snapshots · 11.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627315652026-09-0314:2515:18Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627318472026-09-0314:3515:38Excluded: feed incomplete during this tripNone published1 of 19 expected snapshots · 5.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627303862026-09-0315:5516:56Excluded: feed incomplete during this tripNone published3 of 19 expected snapshots · 15.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304222026-09-0317:2518:22Excluded: feed incomplete during this tripNone published3 of 18 expected snapshots · 16.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627311872026-09-0318:0519:04Excluded: feed incomplete during this tripNone published4 of 18 expected snapshots · 22.2%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627302862026-09-0323:4024:29Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627302872026-09-0324:2525:07Excluded: feed incomplete during this tripNone published3 of 15 expected snapshots · 20%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627318162026-09-0208:3509:34Excluded: feed incomplete during this tripNone published2 of 18 expected snapshots · 11.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306122026-09-0213:5514:48Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627305162026-09-0214:0515:04Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627315652026-09-0214:2515:18Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627318472026-09-0214:3515:38Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627305322026-09-0214:5515:56Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627315312026-09-0214:5516:02Excluded: feed incomplete during this tripNone published0 of 20 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306132026-09-0215:0516:14Excluded: feed incomplete during this tripNone published0 of 20 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627302512026-09-0215:2016:29Excluded: feed incomplete during this tripNone published0 of 20 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306382026-09-0215:2516:26Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307172026-09-0215:3516:44Excluded: feed incomplete during this tripNone published0 of 20 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627303862026-09-0215:5516:56Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304332026-09-0216:0517:18Excluded: feed incomplete during this tripNone published0 of 21 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307182026-09-0216:2517:26Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304752026-09-0216:3517:40Excluded: feed incomplete during this tripNone published1 of 19 expected snapshots · 5.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627312992026-09-0117:5518:52Excluded: feed incomplete during this tripNone published5 of 18 expected snapshots · 27.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307252026-08-3120:2421:13Excluded: feed incomplete during this tripNone published4 of 16 expected snapshots · 25%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626974732026-08-2912:0712:57Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626973632026-08-2912:1013:04Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626974992026-08-2913:0513:55Excluded: feed incomplete during this tripNone published3 of 16 expected snapshots · 18.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626976242026-08-2913:1014:05Excluded: feed incomplete during this tripNone published5 of 17 expected snapshots · 29.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626978872026-08-2917:0717:59Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626978842026-08-2917:1018:05Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626979412026-08-2918:0718:54Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626979452026-08-2918:1019:00Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626980012026-08-2919:0719:54Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626979812026-08-2919:1020:00Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626980292026-08-2920:0720:54Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626980122026-08-2920:1021:00Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626981072026-08-2921:0721:54Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626981362026-08-2921:1022:00Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626981832026-08-2922:0722:54Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:626981822026-08-2922:1022:58Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627303392026-08-2805:5006:49Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627314162026-08-2806:1707:11Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304992026-08-2806:3507:36Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627311662026-08-2806:4307:29Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627318492026-08-2806:4607:32Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627318532026-08-2806:4807:46Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627305132026-08-2806:5007:36Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627318482026-08-2806:5607:43Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627318522026-08-2807:0107:51Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627313222026-08-2807:0508:07Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627318512026-08-2807:0507:55Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627318502026-08-2807:1008:00Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627317892026-08-2807:1808:20Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627311482026-08-2807:3508:39Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627317902026-08-2807:4308:45Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627313192026-08-2807:5808:44Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627310402026-08-2808:0509:09Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627313182026-08-2808:1809:16Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627318162026-08-2808:3509:34Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627310422026-08-2808:5209:46Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306082026-08-2809:0510:02Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306062026-08-2809:2110:14Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627315422026-08-2809:3510:32Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627318182026-08-2809:5210:45Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627312472026-08-2810:0511:02Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627315432026-08-2810:2511:18Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627301852026-08-2810:3511:33Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627312482026-08-2810:5511:48Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627310762026-08-2811:0512:03Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627301862026-08-2811:2512:18Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627302312026-08-2811:3512:33Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627310772026-08-2811:5512:48Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304292026-08-2812:0513:03Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627302772026-08-2812:2513:18Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304742026-08-2812:3513:33Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304302026-08-2812:5513:48Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306112026-08-2813:0514:03Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304672026-08-2813:2514:18Excluded: feed incomplete during this tripNone published1 of 17 expected snapshots · 5.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627315552026-08-2813:3414:32Excluded: feed incomplete during this tripNone published4 of 18 expected snapshots · 22.2%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627302512026-08-2815:2016:29Excluded: feed incomplete during this tripNone published1 of 20 expected snapshots · 5%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306382026-08-2815:2516:26Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307172026-08-2815:3516:44Excluded: feed incomplete during this tripNone published0 of 20 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627303862026-08-2815:5516:56Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304332026-08-2816:0517:18Excluded: feed incomplete during this tripNone published0 of 21 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307182026-08-2816:2517:26Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304752026-08-2816:3517:40Excluded: feed incomplete during this tripNone published1 of 19 expected snapshots · 5.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304342026-08-2816:5517:56Excluded: feed incomplete during this tripNone published1 of 19 expected snapshots · 5.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627313002026-08-2817:0518:08Excluded: feed incomplete during this tripNone published1 of 19 expected snapshots · 5.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306862026-08-2822:4023:34Excluded: feed incomplete during this tripNone published5 of 17 expected snapshots · 29.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627303392026-08-2705:5006:49Excluded: feed incomplete during this tripNone published4 of 18 expected snapshots · 22.2%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306122026-08-2713:5514:48Excluded: feed incomplete during this tripNone published9 of 17 expected snapshots · 52.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627305322026-08-2714:5515:56Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627315312026-08-2714:5516:02Excluded: feed incomplete during this tripNone published0 of 20 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306132026-08-2715:0516:14Excluded: feed incomplete during this tripNone published0 of 20 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627302512026-08-2715:2016:29Excluded: feed incomplete during this tripNone published0 of 20 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306382026-08-2715:2516:26Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307172026-08-2715:3516:44Excluded: feed incomplete during this tripNone published0 of 20 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627303862026-08-2715:5516:56Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304332026-08-2716:0517:18Excluded: feed incomplete during this tripNone published0 of 21 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307182026-08-2716:2517:26Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304752026-08-2716:3517:40Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304342026-08-2716:5517:56Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627313002026-08-2717:0518:08Excluded: feed incomplete during this tripNone published0 of 19 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627304222026-08-2717:2518:22Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307462026-08-2717:3518:34Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627312992026-08-2717:5518:52Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627311872026-08-2718:0519:04Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307232026-08-2718:2519:18Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627302642026-08-2719:0019:58Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627302492026-08-2719:2520:14Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307242026-08-2719:4020:38Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307252026-08-2720:2421:13Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306962026-08-2720:4121:39Excluded: feed incomplete during this tripNone published0 of 18 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307042026-08-2721:2522:13Excluded: feed incomplete during this tripNone published0 of 16 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627302842026-08-2721:4022:34Excluded: feed incomplete during this tripNone published0 of 17 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627302852026-08-2722:2523:10Excluded: feed incomplete during this tripNone published0 of 15 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.