Skip to main content
Otranspo

Route 42

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.

  • 206870502026-09-10 · CANCELED · None publishedSep 10, 2026, 6:49 p.m.
  • 88710502026-09-10 · CANCELED · None publishedSep 10, 2026, 4:39 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 12, 202647 of 50 trip windows had enough operator-feed evidence50482096%241,68177.2%3.4 min9.2 min
Sep 11, 202666 of 66 trip windows had enough operator-feed evidence666600100%26Open this dayOpen this dayOpen this dayOpen this day
Sep 10, 202666 of 66 trip windows had enough operator-feed evidence6606600%0Open this dayOpen this dayOpen this dayOpen this day
Sep 9, 202666 of 66 trip windows had enough operator-feed evidence666600100%27Open this dayOpen this dayOpen this dayOpen this day
Sep 8, 202666 of 66 trip windows had enough operator-feed evidence666600100%27Open this dayOpen this dayOpen this dayOpen this day
Sep 7, 202637 of 40 trip windows had enough operator-feed evidence4013632.5%1Open this dayOpen this dayOpen this dayOpen this day
Sep 6, 202640 of 40 trip windows had enough operator-feed evidence4013902.5%1Open this dayOpen this dayOpen this dayOpen this day
Sep 5, 202649 of 50 trip windows had enough operator-feed evidence5014812%1Open this dayOpen this dayOpen this dayOpen this day
Sep 4, 202657 of 66 trip windows had enough operator-feed evidence6625593%2Open this dayOpen this dayOpen this dayOpen this day
Sep 3, 20267 of 66 trip windows had enough operator-feed evidence664801872.7%24Open this dayOpen this dayOpen this dayOpen this day
Sep 2, 20268 of 66 trip windows had enough operator-feed evidence665001675.8%23Open this dayOpen this dayOpen this dayOpen this day
Sep 1, 202616 of 66 trip windows had enough operator-feed evidence66640297%26Open this dayOpen this dayOpen this dayOpen this day
Aug 31, 202628 of 66 trip windows had enough operator-feed evidence66650198.5%26Open this dayOpen this dayOpen this dayOpen this day
Aug 30, 202635 of 40 trip windows had enough operator-feed evidence404000100%20Open this dayOpen this dayOpen this dayOpen this day
Aug 29, 202634 of 45 trip windows had enough operator-feed evidence454500100%22Open this dayOpen this dayOpen this dayOpen this day
Aug 28, 20263 of 62 trip windows had enough operator-feed evidence622004232.3%7Open this dayOpen this dayOpen this dayOpen this day
Aug 27, 20266 of 62 trip windows had enough operator-feed evidence623502756.5%10Open this dayOpen this dayOpen this dayOpen this day
Aug 26, 20260 of 62 trip windows had enough operator-feed evidence6200620%0Open this dayOpen this dayOpen this dayOpen this day
Aug 25, 202617 of 62 trip windows had enough operator-feed evidence623812361.3%11Open this dayOpen this dayOpen this dayOpen this day

Scheduled-trip detail · September 12, 2026

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
54660702026-09-1205:3906:04Observed21615:39 a.m. / 6:20 a.m.8 of 11 expected snapshots · 72.7%
44280702026-09-1206:0606:30Observed22016:01 a.m. / 6:39 a.m.9 of 11 expected snapshots · 81.8%
117390702026-09-1206:3907:04Observed22016:40 a.m. / 8:04 a.m.7 of 11 expected snapshots · 63.6%
158680702026-09-1207:0607:30Observed64986:22 a.m. / 7:30 a.m.8 of 11 expected snapshots · 72.7%
169850702026-09-1207:3908:06Observed21607:23 a.m. / 8:06 a.m.11 of 12 expected snapshots · 91.7%
38580702026-09-1208:0608:30Observed48237:35 a.m. / 8:40 a.m.11 of 11 expected snapshots · 100%
161770702026-09-1208:0908:36Observed67038:08 a.m. / 10:09 a.m.12 of 12 expected snapshots · 100%
36160702026-09-1208:3609:00Observed22168:06 a.m. / 9:11 a.m.10 of 11 expected snapshots · 90.9%
194500702026-09-1208:3909:06Observed48238:41 a.m. / 10:05 a.m.11 of 12 expected snapshots · 91.7%
66150702026-09-1209:0609:30Observed21598:35 a.m. / 9:40 a.m.9 of 11 expected snapshots · 81.8%
99270702026-09-1209:0909:36Observed22168:27 a.m. / 9:49 a.m.10 of 12 expected snapshots · 83.3%
171230702026-09-1209:3610:00Observed25269:43 a.m. / 10:13 a.m.10 of 11 expected snapshots · 90.9%
37990702026-09-1209:3910:06Observed21598:56 a.m. / 10:34 a.m.11 of 12 expected snapshots · 91.7%
140930702026-09-1210:0610:30Observed64999:38 a.m. / 10:32 a.m.11 of 11 expected snapshots · 100%
165040702026-09-1210:0910:36Observed252610:15 a.m. / 11:21 a.m.12 of 12 expected snapshots · 100%
46940702026-09-1210:3611:00Observed215910:35 a.m. / 11:05 a.m.11 of 11 expected snapshots · 100%
155060702026-09-1210:3911:06Observed221310:41 a.m. / 11:11 a.m.12 of 12 expected snapshots · 100%
202880702026-09-1211:0611:30Observed216011:06 a.m. / 12:09 p.m.11 of 11 expected snapshots · 100%
7510702026-09-1211:0911:36Observed253611:04 a.m. / 12:04 p.m.12 of 12 expected snapshots · 100%
152520702026-09-1211:3612:00No 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.
141330702026-09-1211:3912:06Observed222511:34 a.m. / 12:09 p.m.11 of 12 expected snapshots · 91.7%
167010702026-09-1212:0612:31Observed253612:05 p.m. / 12:48 p.m.9 of 11 expected snapshots · 81.8%
141030702026-09-1212:0912:36No matching position; investigateNone published10 of 12 expected snapshots · 83.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
148780702026-09-1212:3613:03Observed222512:10 p.m. / 1:36 p.m.10 of 12 expected snapshots · 83.3%
229710702026-09-1212:3613:01Observed658512:35 p.m. / 1:13 p.m.10 of 11 expected snapshots · 90.9%
83700702026-09-1213:0613:32Observed66591:05 p.m. / 1:40 p.m.11 of 12 expected snapshots · 91.7%
7660702026-09-1213:0913:36Observed65851:14 p.m. / 1:41 p.m.12 of 12 expected snapshots · 100%
113110702026-09-1213:3814:04Observed22251:37 p.m. / 2:11 p.m.10 of 12 expected snapshots · 83.3%
115490702026-09-1213:3914:06Observed66591:40 p.m. / 2:04 p.m.11 of 12 expected snapshots · 91.7%
197030702026-09-1214:0614:32Observed21011:51 p.m. / 2:40 p.m.10 of 12 expected snapshots · 83.3%
77060702026-09-1214:0914:36Observed22252:12 p.m. / 2:42 p.m.11 of 12 expected snapshots · 91.7%
142690702026-09-1214:3615:02Observed48352:35 p.m. / 3:09 p.m.11 of 12 expected snapshots · 91.7%
217080702026-09-1214:3915:06Observed21011:57 p.m. / 3:19 p.m.12 of 12 expected snapshots · 100%
37040702026-09-1215:0615:32Observed21342:44 p.m. / 3:41 p.m.11 of 12 expected snapshots · 91.7%
108080702026-09-1215:0915:36Observed48353:10 p.m. / 3:49 p.m.12 of 12 expected snapshots · 100%
88540702026-09-1215:3616:01Observed48303:40 p.m. / 4:10 p.m.11 of 11 expected snapshots · 100%
55930702026-09-1215:3916:06Observed21342:55 p.m. / 4:34 p.m.12 of 12 expected snapshots · 100%
146900702026-09-1216:0616:31Observed21144:06 p.m. / 5:24 p.m.11 of 11 expected snapshots · 100%
133660702026-09-1216:0916:36Observed48304:11 p.m. / 4:48 p.m.12 of 12 expected snapshots · 100%
193390702026-09-1216:3617:01Observed21344:35 p.m. / 5:08 p.m.11 of 11 expected snapshots · 100%
144410702026-09-1216:3917:06Observed22154:42 p.m. / 5:09 p.m.12 of 12 expected snapshots · 100%
12680702026-09-1217:0617:33Observed21345:09 p.m. / 6:06 p.m.11 of 12 expected snapshots · 91.7%
193810702026-09-1217:0617:31Observed25105:05 p.m. / 5:42 p.m.11 of 11 expected snapshots · 100%
175440702026-09-1217:3618:01Observed21895:35 p.m. / 6:11 p.m.11 of 11 expected snapshots · 100%
76230702026-09-1217:3918:06Observed25105:43 p.m. / 6:11 p.m.12 of 12 expected snapshots · 100%
114380702026-09-1218:0818:33Observed21346:07 p.m. / 6:41 p.m.11 of 11 expected snapshots · 100%
161100702026-09-1218:0918:36Observed21896:12 p.m. / 6:41 p.m.12 of 12 expected snapshots · 100%
75770702026-09-1218:3619:01Observed46376:26 p.m. / 7:03 p.m.11 of 11 expected snapshots · 100%
16890702026-09-1218:3919:06Observed21346:42 p.m. / 7:16 p.m.12 of 12 expected snapshots · 100%
23020702026-09-1219:0619:31Observed22157:03 p.m. / 7:32 p.m.10 of 11 expected snapshots · 90.9%
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.