Skip to main content
Otranspo

Route 400

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:627310162026-09-09 · CANCELED · None publishedSep 9, 2026, 7:00 p.m.
  • sto:627305202026-09-04 · CANCELED · None publishedSep 4, 2026, 11:49 a.m.
  • sto:627315602026-09-03 · CANCELED · None publishedSep 3, 2026, 7:12 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, 202685 of 146 trip windows had enough operator-feed evidence1468965161%28Open this dayOpen this dayOpen this dayOpen this day
Sep 12, 2026146 of 146 trip windows had enough operator-feed evidence14614600100%34Open this dayOpen this dayOpen this dayOpen this day
Sep 11, 2026187 of 187 trip windows had enough operator-feed evidence1871834097.9%82Open this dayOpen this dayOpen this dayOpen this day
Sep 10, 2026187 of 187 trip windows had enough operator-feed evidence1871861099.5%79Open this dayOpen this dayOpen this dayOpen this day
Sep 9, 2026187 of 187 trip windows had enough operator-feed evidence1871843098.4%77Open this dayOpen this dayOpen this dayOpen this day
Sep 8, 2026187 of 187 trip windows had enough operator-feed evidence1871825097.3%80Open this dayOpen this dayOpen this dayOpen this day
Sep 7, 2026146 of 146 trip windows had enough operator-feed evidence1461451099.3%38Open this dayOpen this dayOpen this dayOpen this day
Sep 6, 2026146 of 146 trip windows had enough operator-feed evidence14614600100%31Open this dayOpen this dayOpen this dayOpen this day
Sep 5, 2026146 of 146 trip windows had enough operator-feed evidence14614600100%31Open this dayOpen this dayOpen this dayOpen this day
Sep 4, 2026165 of 187 trip windows had enough operator-feed evidence1871762994.1%78Open this dayOpen this dayOpen this dayOpen this day
Sep 3, 202618 of 187 trip windows had enough operator-feed evidence18713505272.2%69Open this dayOpen this dayOpen this dayOpen this day
Sep 2, 202620 of 187 trip windows had enough operator-feed evidence18713804973.8%69Open this dayOpen this dayOpen this dayOpen this day
Sep 1, 202647 of 187 trip windows had enough operator-feed evidence1871791795.7%76Open this dayOpen this dayOpen this dayOpen this day
Aug 31, 202671 of 187 trip windows had enough operator-feed evidence1871773794.7%76Open this dayOpen this dayOpen this dayOpen this day
Aug 30, 2026120 of 146 trip windows had enough operator-feed evidence14614600100%42Open this dayOpen this dayOpen this dayOpen this day
Aug 29, 202629 of 146 trip windows had enough operator-feed evidence1468006654.8%34Open this dayOpen this dayOpen this dayOpen this day
Aug 28, 20267 of 187 trip windows had enough operator-feed evidence18785010245.5%43Open this dayOpen this dayOpen this dayOpen this day
Aug 27, 202667 of 187 trip windows had enough operator-feed evidence1878549845.5%43Open this dayOpen this dayOpen this dayOpen this day
Aug 26, 20260 of 187 trip windows had enough operator-feed evidence187001870%0Open this dayOpen this dayOpen this dayOpen this day
Aug 25, 202690 of 187 trip windows had enough operator-feed evidence18711806963.1%60Open 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:627182172026-09-1305:5506:39Excluded: 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.
sto:627182282026-09-1306:1206:56Excluded: 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.
sto:627182192026-09-1306:1506:59Excluded: 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.
sto:627183362026-09-1306:2707:11Excluded: 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.
sto:627183302026-09-1306:3007:14Excluded: 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.
sto:627183402026-09-1306:4207:26Excluded: 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.
sto:627184642026-09-1306:4507:29Excluded: 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.
sto:627182312026-09-1306:5707:41Excluded: 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.
sto:627185332026-09-1307:0007:44Excluded: 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.
sto:627182292026-09-1307:1207:56Excluded: 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.
sto:627182382026-09-1307:1507:59Excluded: 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.
sto:627183332026-09-1307:2708:11Excluded: 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.
sto:627183322026-09-1307:3008:14Excluded: 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.
sto:627184622026-09-1307:4208:26Excluded: 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.
sto:627183312026-09-1307:4508:29Excluded: 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.
sto:627185322026-09-1307:5708:41Excluded: 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.
sto:627182342026-09-1308:0008:44Excluded: 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.
sto:627182352026-09-1308:1208:56Excluded: 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.
sto:627182372026-09-1308:1508:59Excluded: 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.
sto:627183902026-09-1308:2609:12Excluded: 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:627183392026-09-1308:3009:14Excluded: 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.
sto:627183412026-09-1308:4109:27Excluded: 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:627184632026-09-1308:4509:29Excluded: 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.
sto:627190212026-09-1308:5509: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:627185242026-09-1309:0009:44Excluded: 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.
sto:627190662026-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:627182532026-09-1309:1509:59Excluded: 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.
sto:627183422026-09-1309:2510: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:627183892026-09-1309:3010:14Excluded: 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.
sto:627184652026-09-1309:4010: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:627183862026-09-1309:4510:29Excluded: 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.
sto:627191282026-09-1309:5510: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:627190242026-09-1310:0010:44Excluded: 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.
sto:627187152026-09-1310:1010: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:627190632026-09-1310:1510:59Excluded: 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.
sto:627191852026-09-1310:2511: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:627187722026-09-1310:3011:14Excluded: 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.
sto:627183882026-09-1310:4011: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:627191982026-09-1310:4511:29Excluded: 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.
sto:627190232026-09-1310:5511: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:627191292026-09-1311:0011:44Excluded: 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.
sto:627190652026-09-1311:1011: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:627187122026-09-1311:1511:59Excluded: 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.
sto:627187712026-09-1311:2512: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:627191862026-09-1311:3012:14Excluded: 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.
sto:627191972026-09-1311:4012:31Excluded: 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:627183842026-09-1311:4512:29Excluded: 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.
sto:627191272026-09-1311:5512: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:627190182026-09-1312:0012:44Excluded: 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.
sto:627184082026-09-1312:1013:01Excluded: 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:627190642026-09-1312:1512:59Excluded: feed incomplete during this tripNone published2 of 15 expected snapshots · 13.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627191372026-09-1313:1014:01No matching position; investigateNone published15 of 17 expected snapshots · 88.2%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627191382026-09-1314:1515:01No 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:627191392026-09-1315:1016:01No matching position; investigateNone published16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627191402026-09-1316:1517:01No 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:627200502026-09-1322:2723:13No 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:627201422026-09-1323:3024:12No matching position; investigateNone published14 of 15 expected snapshots · 93.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627302632026-09-1109:2610:09No matching position; investigateNone published14 of 15 expected snapshots · 93.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627315642026-09-1121:3022:10No matching position; investigateNone published15 of 14 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306572026-09-1122:1823:00No matching position; investigateNone published15 of 15 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627312622026-09-1123:1523:53No matching position; investigateNone published13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307492026-09-1011:4612:29No matching position; investigateNone published14 of 15 expected snapshots · 93.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627308092026-09-0906:0006:43No matching position; investigateNone published15 of 15 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627317052026-09-0914:2715:13No 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:627310162026-09-0918:1119:00No 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:627309842026-09-0813:0113:49No 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:627317052026-09-0814:2715:13No 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:627317072026-09-0814:3715:23No 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:627315252026-09-0815:2316: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:627305632026-09-0817:2318:14No matching position; investigateNone published16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627583592026-09-0723:3024:12No matching position; investigateNone published15 of 15 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627305202026-09-0411:0611:49No matching position; investigateNone published14 of 15 expected snapshots · 93.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627317352026-09-0417:3718:23No 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:627306812026-09-0420:1120:55Excluded: 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.
sto:627305422026-09-0420:1320:54Excluded: 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.
sto:627315632026-09-0420:2321:07Excluded: 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.
sto:627319822026-09-0420:2621:07Excluded: 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.
sto:627312282026-09-0420:3521:19Excluded: 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.
sto:627307682026-09-0420:3721:18Excluded: 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.
sto:627312062026-09-0420:4921:30Excluded: 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:627303482026-09-0420:5021:34Excluded: 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:627319832026-09-0421:0121:42Excluded: feed incomplete during this tripNone published5 of 15 expected snapshots · 33.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627308762026-09-0308:0608:52Excluded: 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:627309702026-09-0308:1809:04Excluded: 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:627313232026-09-0309:3610:19Excluded: feed incomplete during this tripNone published1 of 15 expected snapshots · 6.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627315142026-09-0310:2611:09Excluded: 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.
sto:627310542026-09-0310:3111:19Excluded: 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:627311222026-09-0310:3611:19Excluded: 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.
sto:627313242026-09-0310:4111:29Excluded: 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:627312912026-09-0310:4611:29Excluded: feed incomplete during this tripNone published2 of 15 expected snapshots · 13.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627307392026-09-0310:5111:39Excluded: 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:627303072026-09-0310:5711:40Excluded: feed incomplete during this tripNone published4 of 15 expected snapshots · 26.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627306322026-09-0312:1713:00Excluded: 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.
sto:627303822026-09-0312:2113:09Excluded: 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:627312432026-09-0312:2613:09Excluded: 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.
sto:627307782026-09-0312:3113:19Excluded: 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:627308752026-09-0312:3713:20Excluded: 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.
sto:627311262026-09-0312:4113:24Excluded: 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.
sto:627313272026-09-0312:4113: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:627312952026-09-0312:4613:29Excluded: 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.
sto:627310972026-09-0312:5113:39Excluded: 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:627303102026-09-0312:5713:40Excluded: feed incomplete during this tripNone published2 of 15 expected snapshots · 13.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627309842026-09-0313:0113:49Excluded: 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:627305502026-09-0313:0713:50Excluded: feed incomplete during this tripNone published2 of 15 expected snapshots · 13.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627303682026-09-0313:1714:00Excluded: feed incomplete during this tripNone published2 of 15 expected snapshots · 13.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627312512026-09-0314:0314:47Excluded: feed incomplete during this tripNone published1 of 15 expected snapshots · 6.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627308542026-09-0314:0914:53Excluded: 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.
sto:627305722026-09-0314:1015: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:627306052026-09-0314:1515:01Excluded: 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:627301472026-09-0314:2015:12Excluded: 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:627317042026-09-0314:2115:07Excluded: 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:627317052026-09-0314:2715: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:627313402026-09-0314:3015:22Excluded: 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:627317062026-09-0314:3115:17Excluded: 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:627317072026-09-0314:3715:23Excluded: 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:627317082026-09-0314:3915:25Excluded: feed incomplete during this tripNone published1 of 16 expected snapshots · 6.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627313312026-09-0314:4015:34Excluded: 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:627317562026-09-0314:4715:36Excluded: feed incomplete during this tripNone published1 of 16 expected snapshots · 6.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627320242026-09-0314:5215:41Excluded: feed incomplete during this tripNone published1 of 16 expected snapshots · 6.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627317092026-09-0314:5415:43Excluded: feed incomplete during this tripNone published1 of 16 expected snapshots · 6.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627319772026-09-0316:0116:56Excluded: 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:627305632026-09-0317:2318:14Excluded: 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:627317342026-09-0317:3218:18Excluded: 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:627319762026-09-0317:3518:26Excluded: 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:627317352026-09-0317:3718:23Excluded: 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:627315602026-09-0318:2319:12Excluded: feed incomplete during this tripNone published5 of 16 expected snapshots · 31.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627312902026-09-0319:1119:56Excluded: feed incomplete during this tripNone published4 of 15 expected snapshots · 26.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627319812026-09-0320:0120:42Excluded: 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:627305422026-09-0320:1320:54Excluded: feed incomplete during this tripNone published2 of 15 expected snapshots · 13.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627315242026-09-0323:3024:08Excluded: feed incomplete during this tripNone published1 of 14 expected snapshots · 7.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627310872026-09-0323:3324:15Excluded: 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.
sto:627302422026-09-0323:4524:23Excluded: feed incomplete during this tripNone published0 of 14 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627301542026-09-0324:0024:38Excluded: feed incomplete during this tripNone published0 of 14 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627312102026-09-0324:0324:45Excluded: 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.
sto:627318122026-09-0208:3009:16Excluded: 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:627317002026-09-0208:3809:22Excluded: feed incomplete during this tripNone published1 of 15 expected snapshots · 6.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627317012026-09-0208:4009:28Excluded: 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:627312772026-09-0208:4209:27Excluded: feed incomplete during this tripNone published2 of 15 expected snapshots · 13.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627317022026-09-0208:5009:38Excluded: 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:627309782026-09-0209:5610:39Excluded: feed incomplete during this tripNone published1 of 15 expected snapshots · 6.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
sto:627303052026-09-0210:0110:49Excluded: 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:627313292026-09-0213:3714:20Excluded: 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.
sto:627311282026-09-0213:4014: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:627311112026-09-0213:4714:30Excluded: 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.
sto:627312962026-09-0213:5014:39Excluded: 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:627309862026-09-0213:5714:40Excluded: 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.
sto:627315892026-09-0214:0014:49Excluded: 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:627312512026-09-0214:0314:47Excluded: 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.
sto:627308542026-09-0214:0914:53Excluded: 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.
sto:627305722026-09-0214:1015: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.
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.