Scheduled service and available evidence
Evidence period: Oct 28, 2026 – Nov 3, 2026
—
No retained notice returned; this does not prove zero cancellations.
1
1 of 60 trips with a usable feed window (1.7%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
59 with position · 1 to investigate · 0 excluded · 60 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 4, 2026, 8:56 a.m..
0 scheduled trips were excluded from the position check for feed or identity gaps.
Published position coverage: 59 / 60 (98.3%). This is not a delivered-service rate. 7 service days in this source.
Timetables retained before the service day: 7 / 7 requested days · 0 missing days.
Historical calculation: Nov 4, 2026, 7:40 a.m.
Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.
Predictions against the timetable
96.3%
of eligible provider predictions were within five minutes of the timetable.
Share of predictions within five minutes of the timetable. Only eligible hours are shown; an absent hour does not mean zero.
These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.
Calculated: Nov 4, 2026
2 partial-capture days not counted.
6 hourly cohorts meet the thresholds of 30 predictions and 5 service days. Hourly thresholds are assessed separately from the route-wide aggregate.
Improvement or decline requires comparable periods. This single result cannot establish a trend.
Last 28 days, October 7, 2026 to November 3, 2026: 26 days counted.
2 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: October 8, 2026, October 15, 2026.
Too few buses were measured to judge bunching: 0 pairs checked, 30 needed.
Not enough trips yet to measure speed between timepoints (20 trips needed for each segment).
Aaniin ezhi-dibaabandamang →2 partial-capture days not counted.
No counted cancellations on this route in the last four weeks. Notices we could not check would be listed below.
Did not come (no bus seen, no notice), last 7 days: 1 of 60 trips we could check.
Ishkwaa-inendamowin
98% of predictions are within five minutes of the timetable in a typical sampled hour; the lowest sampled hour is 83%.
Only 98% of scheduled trips were seen; the rest are not counted as missed.
| What | Aaniin apii | Tibàdjigade | Scenario or next investigation |
|---|---|---|---|
| StrengthPredictions consistently close to timetable | 06:00, 07:00, 08:00, 15:00, 16:00, 17:00 | 98% | Keep what works |
| CaveatCoverage gap | All measured hours | 98% | More observation, not a service change |
Route check
A short summary of what we know. We say so when we cannot answer a question.
Ishkwàdj ikidowin
Provider predictions were usually close to schedule in this dated sample.
96 in 100 eligible predictions were within 5 minutes of the timetable · 2,408 predictions checkedAaniin minik gikendaasowinan: Larger sample
Based on 2,408 eligible provider predictions over 18 measured days, from Oct 6, 2026 to Nov 3, 2026.
Updated Nov 4, 2026, 8:32 a.m.
These are repeated prediction-to-timetable differences, not independently measured service failures. They use the same eligible predictions as the result above, but group by stop rather than hour, so the lists need not match line for line.
No repeated prediction-difference period has cleared the evidence threshold yet.
No current official notice matches this route.
Prediction differences by stop
We do not yet have enough route-by-stop history to name a recurring problem stop. Rider reports are used as leads, not proof.
Pàkinan pejig dibaigan ji-wàbandaman endaso-gìzhigad, odàbànag, àpì kàwin gegò gì-ayàsinog, odàbàn ishinikàzowinan, gaye kakina àjindàsowinan.
Ganawaabandan aanjichigewin
Ow ozhibiigan ijinàgwad noongom, kaye ijinàgwad kayàsh. Ow ozhibiigan ikido kà-inendjigàdeg. Kawin ondji-kikendàgwasinon kidji-ki-majàd odàbàn.
Current published schedule began October 30, 2026
Ningii-ganawaabandaamin nitam Ishkwaa-anami'e-giizhigad ishkwaa oshki-mazina'igan gii-maajitaamagak, miinawaa Ishkwaa-anami'e-giizhigad bezhig anami'e-giizhigad jibwaa. Gakina agindaasowinan onjimagadoon GTFS mazina'iganan gaa-ganawendamang, ezhinikaadegin dabazhish.
Bezhig gemaa nawaj giizhigad gaa-onaabanjigeyan, bakaan izhi-bimiwizhiwewag odaabaanag. Ganabaj anami'e-giizhigad gemaa wiikonge-giizhigad. Gaawiin iwe apane izhiwebasinoon.
Giizhigad gaa-andawaabanjigaadeg: October 26, 2026
Operator calendar-date records: 0 added · 2 removed
Ozhibii'igan ezhinaagwak: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad
Giizhigad gaa-andawaabanjigaadeg: November 2, 2026
Operator calendar-date records: 0 added · 2 removed
Ozhibii'igan ezhinaagwak: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945
We will compare settled arrivals for the 14 days before and after the change. We publish the comparison only after both sides have at least 7 service days and 200 arrivals.
Still collecting: before has 1,362 arrivals over 10 days; after has 408 arrivals over 3 days. No improvement or decline is claimed yet.
Checksums let anyone verify which retained timetable produced the counts. A changed count does not identify a cause, cancellation, operator decision, or passenger impact.
We compare the last eligible provider prediction for each scheduled arrival with the official schedule. These are not independently measured arrivals. A result needs at least 200 eligible predictions. Within 5 minutes is the rider-facing target used here.
The public feed does not provide dependable passenger counts or passed-up-rider events. A missing position does not by itself prove a cancellation, no-show, short turn or cause.
Provisional results, published evidence
Each hour compares the last eligible provider prediction for a scheduled arrival with the timetable. “Within 5 minutes” describes that prediction difference, not a measured arrival or proof that a bus ran.
Evidence window: October 6, 2026 to November 3, 2026
| Dibaa'igan | Weweni apii | Median | 95th percentile | Gikendaasowinan |
|---|---|---|---|---|
| 06:00 | 100.0% | 0.4 min late | 1.6 min late | 223 · 10 days |
| 07:00 | 95.1% | 0.3 min early | 2.8 min late | 223 · 10 days |
| 08:00 | 100.0% | 0.7 min early | 1.6 min late | 230 · 10 days |
| 15:00 | 100.0% | 0.5 min late | 2.8 min late | 229 · 10 days |
| 16:00 | 82.6% | 2.4 min late | 11.2 min late | 230 · 10 days |
| 17:00 | 94.7% | 0.3 min early | 5.5 min late | 227 · 10 days |
No repeated pattern below 70% is yet established across at least three service days.
59 / 60 scheduled trips published at least one position across 5 service days (98.3%).
This is not a confirmed no-show. A missing position can mean a cancelled or missed bus, but it can also mean an unassigned trip ID or an operator-feed gap. Otranspo publishes the gap because it matters to riders while keeping the conclusion honest.
Prediction check: the last eligible provider prediction no earlier than ten minutes before the scheduled arrival, counted once per trip, stop and scheduled Toronto calendar date. It is compared with the timetable, not an independently measured arrival. Trip-position check: the timetable kept before each service day, matched to recorded positions. Exact IDs are preferred; an OC timetable suffix is matched only to one trip on the same route and date with an overlapping time window. Missing timetables, ambiguous matches and feed gaps stay labelled; they are not confirmed no-shows. Sources and limitations.
Dated service
The timetable, notices and what the live feed says are shown apart. Seeing a bus on the map does not prove you can board it.
November 3, 2026 · 12 trips in the retained timetable · retained notices; capture coverage unverified
In short: 12 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.