Skip to main content
Otranspo

Route 75

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 12 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-07, 2026-08-08, 2026-08-09, 2026-08-10, 2026-08-11, 2026-08-12, 2026-08-13, 2026-08-14, 2026-08-15, 2026-08-16, 2026-08-17, 2026-08-18, 2026-08-19, 2026-08-20, 2026-08-21, 2026-08-22, 2026-08-23, 2026-08-24

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

Operator cancellation notices saved for this period

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

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

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

Service dateScheduled tripsTrips with a positionNo-position candidatesExcluded for feed gapsPosition coveragePublic feed vehicle IDsArrivals checkedArrivals within 5 minutesAverage delay (+ late, − early)How late the worst 5 in 100 were
Sep 5, 202636 of 36 trip windows had enough operator-feed evidence363600100%181,20693.5%1.6 min4.9 min
Sep 4, 202659 of 64 trip windows had enough operator-feed evidence64620296.9%29Open this dayOpen this dayOpen this dayOpen this day
Sep 3, 20268 of 64 trip windows had enough operator-feed evidence643502954.7%25Open this dayOpen this dayOpen this dayOpen this day
Sep 2, 202610 of 64 trip windows had enough operator-feed evidence644002462.5%21Open this dayOpen this dayOpen this dayOpen this day
Sep 1, 202624 of 64 trip windows had enough operator-feed evidence64572589.1%26Open this dayOpen this dayOpen this dayOpen this day
Aug 31, 202633 of 64 trip windows had enough operator-feed evidence64610395.3%31Open this dayOpen this dayOpen this dayOpen this day
Aug 30, 202631 of 36 trip windows had enough operator-feed evidence36350197.2%19Open this dayOpen this dayOpen this dayOpen this day
Aug 29, 20269 of 36 trip windows had enough operator-feed evidence361701947.2%11Open this dayOpen this dayOpen this dayOpen this day
Aug 28, 20263 of 64 trip windows had enough operator-feed evidence641904529.7%8Open this dayOpen this dayOpen this dayOpen this day
Aug 27, 202624 of 64 trip windows had enough operator-feed evidence643123148.4%15Open this dayOpen this dayOpen this dayOpen this day
Aug 26, 20260 of 64 trip windows had enough operator-feed evidence6400640%0Open this dayOpen this dayOpen this dayOpen this day
Aug 25, 202629 of 64 trip windows had enough operator-feed evidence644122164.1%25Open this dayOpen this dayOpen this dayOpen this day

Scheduled-trip detail · September 5, 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
sto:626972722026-09-0506:2506:49Observedsto:25056:24 a.m. / 6:46 a.m.11 of 11 expected snapshots · 100%
sto:626972702026-09-0507:0207:23Observedsto:25056:47 a.m. / 7:20 a.m.10 of 11 expected snapshots · 90.9%
sto:626972692026-09-0507:2507:52Observedsto:20067:23 a.m. / 7:48 a.m.12 of 12 expected snapshots · 100%
sto:626972712026-09-0508:0208:23Observedsto:20067:49 a.m. / 8:24 a.m.10 of 11 expected snapshots · 90.9%
sto:626974392026-09-0508:2508:52Observedsto:17078:23 a.m. / 8:49 a.m.12 of 12 expected snapshots · 100%
sto:626974382026-09-0509:0209:24Observedsto:17078:50 a.m. / 9:25 a.m.10 of 11 expected snapshots · 90.9%
sto:626974352026-09-0509:2509:52Observedsto:18179:25 a.m. / 9:49 a.m.12 of 12 expected snapshots · 100%
sto:626974362026-09-0510:0210:24Observedsto:18179:50 a.m. / 10:24 a.m.10 of 11 expected snapshots · 90.9%
sto:626974372026-09-0510:2510:52Observedsto:100910:14 a.m. / 10:46 a.m.12 of 12 expected snapshots · 100%
sto:626975672026-09-0511:0211:24Observedsto:140610:50 a.m. / 11:27 a.m.10 of 11 expected snapshots · 90.9%
sto:626973382026-09-0511:2511:52Observedsto:201511:18 a.m. / 11:54 a.m.12 of 12 expected snapshots · 100%
sto:626973602026-09-0512:0212:24Observedsto:230611:40 a.m. / 12:26 p.m.10 of 11 expected snapshots · 90.9%
sto:626973722026-09-0512:2512:52Observedsto:160912:13 p.m. / 12:54 p.m.12 of 12 expected snapshots · 100%
sto:626974942026-09-0513:0213:26Observedsto:160912:54 p.m. / 1:26 p.m.11 of 11 expected snapshots · 100%
sto:626975072026-09-0513:2513:54Observedsto:14091:21 p.m. / 1:55 p.m.12 of 12 expected snapshots · 100%
sto:626976402026-09-0514:0214:26Observedsto:14091:56 p.m. / 2:29 p.m.11 of 11 expected snapshots · 100%
sto:626977122026-09-0514:2514:55Observedsto:18072:17 p.m. / 2:55 p.m.13 of 12 expected snapshots · 100%
sto:626977442026-09-0515:0215:26Observedsto:18072:56 p.m. / 3:28 p.m.11 of 11 expected snapshots · 100%
sto:626977732026-09-0515:2515:55Observedsto:12073:25 p.m. / 3:53 p.m.13 of 12 expected snapshots · 100%
sto:626978052026-09-0516:0216:26Observedsto:12073:54 p.m. / 4:27 p.m.11 of 11 expected snapshots · 100%
sto:626978362026-09-0516:2516:53Observedsto:20174:16 p.m. / 4:51 p.m.12 of 12 expected snapshots · 100%
sto:626978722026-09-0517:0217:26Observedsto:20174:52 p.m. / 5:30 p.m.11 of 11 expected snapshots · 100%
sto:626979022026-09-0517:2517:52Observedsto:14095:04 p.m. / 5:51 p.m.12 of 12 expected snapshots · 100%
sto:626981262026-09-0518:0218:26Observedsto:12305:46 p.m. / 6:25 p.m.11 of 11 expected snapshots · 100%
sto:626979582026-09-0518:2518:52Observedsto:17146:18 p.m. / 6:50 p.m.12 of 12 expected snapshots · 100%
sto:626980002026-09-0519:0219:24Observedsto:25056:54 p.m. / 7:28 p.m.10 of 11 expected snapshots · 90.9%
sto:626980522026-09-0519:2519:51Observedsto:17147:04 p.m. / 7:53 p.m.12 of 12 expected snapshots · 100%
sto:626980532026-09-0520:0220:24Observedsto:17147:53 p.m. / 8:29 p.m.10 of 11 expected snapshots · 90.9%
sto:626981002026-09-0520:2520:51Observedsto:23028:14 p.m. / 8:46 p.m.12 of 12 expected snapshots · 100%
sto:626981012026-09-0521:0221:23Observedsto:15028:58 p.m. / 9:27 p.m.10 of 11 expected snapshots · 90.9%
sto:626981482026-09-0521:2521:51Observedsto:14068:33 p.m. / 9:50 p.m.12 of 12 expected snapshots · 100%
sto:626981502026-09-0522:0222:23Observedsto:14069:52 p.m. / 10:27 p.m.10 of 11 expected snapshots · 90.9%
sto:626981982026-09-0522:2522:51Observedsto:230410:27 p.m. / 10:50 p.m.12 of 12 expected snapshots · 100%
sto:626982012026-09-0523:0223:23Observedsto:230410:52 p.m. / 11:26 p.m.10 of 11 expected snapshots · 90.9%
sto:626982352026-09-0523:2823:52Observedsto:230411:27 p.m. / 11:51 p.m.11 of 11 expected snapshots · 100%
sto:626982382026-09-0524:0224:21Observedsto:230411:52 p.m. / 12:23 a.m.10 of 10 expected snapshots · 100%
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.