Scheduled service and available evidence
Evidence period: Oct 27, 2026 – Nov 2, 2026
0
Trips in the published timetable marked cancelled without qualifying later matching vehicle observations in our archive. This does not prove the trip did not operate. Not counted: 2 trips with qualifying later matching vehicle observations. Trips with any notice: 2.
1
1 of 45 trips with a usable feed window (2.2%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
44 with position · 1 to investigate · 0 excluded · 45 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 3, 2026, 11:20 p.m..
0 scheduled trips were excluded from the position check for feed or identity gaps.
Published position coverage: 44 / 45 (97.8%). 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 3, 2026, 10:08 p.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
82.9%
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.
7 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 6, 2026 to November 2, 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.
0% of back-to-back buses on this route arrived bunched together: 6 of 4,120 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
0% of pairs (6) had a long gap: more than 1.75 times the planned wait between them.
| Tó: nikahwistá:ke | Pairs checked | Bunched | Long gap |
|---|---|---|---|
| Morning rush (6 to 9 a.m.) | 1,352 | 0% (0) | 0% (0) |
| Afternoon rush (3 to 6 p.m.) | 2,576 | 0% (6) | 0% (6) |
| Evening (6 to 10 p.m.) | 192 | 0% (0) | 0% (0) |
Slowest: MACFARLANE / BRIGGS to HUNT CLUB / RIVERSIDE, 15.7 km/h actual against 15.8 km/h planned.
| Tsi nón:we | Tsi nón:we | Tsi niió:re (distance) | Planned speed | Actual speed | Trips measured | Slow trips |
|---|---|---|---|---|---|---|
| MACFARLANE / BRIGGS | HUNT CLUB / RIVERSIDE | 3.6 km | 15.8 km/h | 15.7 km/h | 83 | 0% |
| HUNT CLUB / RIVERSIDE | MACFARLANE / MERIVALE | 3.8 km | 22.6 km/h | 23.9 km/h | 66 | 3% |
| BASELINE 1C | VAAN / WOODROFFE | 3 km | 25.9 km/h | 24.5 km/h | 72 | 4% |
| MACFARLANE / MERIVALE | VAAN / COLEWAY | 2.3 km | 25 km/h | 25.4 km/h | 65 | 5% |
| VAAN / WOODROFFE | MACFARLANE / BRIGGS | 2.6 km | 25.5 km/h | 26.5 km/h | 83 | 0% |
| HUNT CLUB / RIVERSIDE | SOUTH KEYS A | 4.1 km | 27 km/h | 28.8 km/h | 83 | 2% |
| GREENBORO B | HUNT CLUB / RIVERSIDE | 4.4 km | 36.5 km/h | 32.3 km/h | 67 | 7% |
A slow trip took at least 1.5 times the planned time.
2 partial-capture days not counted.
1 scheduled trips with counted cancellation notices from Tue, Oct 6 to Mon, Nov 2.
Not counted: 5 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
Hours with the most cancellations: 3 p.m. (1)
OC Transpo gives no reason for single trips, so none is shown.
Did not come (no bus seen, no notice), last 7 days: 1 of 45 trips we could check.
Ka' nikarihò:ten
Median provider predictions are 4.6 min later than the timetable in 1 hours of the day.
08:00 has 53% of predictions within five minutes of the timetable, against 88% the rest of the day.
Only 98% of scheduled trips were seen; the rest are not counted as missed.
| What | Ó:nen | Tewaterièn:tare | Scenario or next investigation |
|---|---|---|---|
| ProblemPredictions later than timetable | 08:00 | 4.6 min late | More running time |
| ProblemOne hour has a lower prediction match | 08:00 | 53% | Operations, not the timetable |
| 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.
Bottom line
Provider predictions were usually close to schedule, but check the problem times below.
83 in 100 eligible predictions were within 5 minutes of the timetable · 6,585 predictions checkedPrediction sample size: Larger sample
Based on 6,585 eligible provider predictions over 18 measured days, from Oct 5, 2026 to Nov 2, 2026.
Updated Nov 3, 2026, 10:32 p.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 current official notice matches this route.
Prediction differences by stop
35 in 100 eligible predictions differed from the timetable by more than 5 minutes (79 predictions over 20 days).
Open this stop35 in 100 eligible predictions differed from the timetable by more than 5 minutes (79 predictions over 20 days).
Open this stop35 in 100 eligible predictions differed from the timetable by more than 5 minutes (79 predictions over 20 days).
Open this stop35 in 100 eligible predictions differed from the timetable by more than 5 minutes (79 predictions over 20 days).
Open this stopThese are route-specific provider predictions compared with the timetable. They identify repeated prediction differences at a place and time, not measured arrivals or their cause.
Open a time period to see each service day, scheduled trip, feed gap, observed public vehicle ID, and the exact counts behind this summary.
Schedule change check
This compares the current retained official schedule with the prior retained version. Schedule changes are facts about what was planned. They do not prove that a trip ran.
Current published schedule began October 30, 2026
We check ne first Monday after ne á:se schedule began, tánon ne Monday one week earlier. Akwé:kon figures, official GTFS versions named below.
At least one selected date uses added or removed calendar-date service. Treat this as holiday or special-service context, not ordinary weekday growth.
Wenhniserá:te wahatkáhtho: October 26, 2026
Operator calendar-date records: 0 added · 2 removed
Kahiatónhsera: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad
Wenhniserá:te wahatkáhtho: November 2, 2026
Operator calendar-date records: 0 added · 2 removed
Kahiatónhsera: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945
Enkwatkáhtho' ne arrivals 14 wenhniserá:tens tsi niió:re aorí:wa ne change tánon' ohnà:ken. Ne tsi enkwatkáhtho' entewahró:ri' tsi nikarì:wes ne 7 wenhniserá:tens tánon' 200 arrivals iá:ken'.
Still collecting: before has 3,651 arrivals over 10 days; after has 743 arrivals over 2 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 5, 2026 to November 2, 2026
| Hour | Ioiánere tsi nikarì:wes | Median | 95th percentile | Tsi tó:kenske |
|---|---|---|---|---|
| 06:00 | 94.6% | 0 min late | 2.5 min late | 448 · 10 days |
| 07:00 | 88.8% | 2 min late | 7.8 min late | 851 · 10 days |
| 08:00 | 52.5% | 4.6 min late | 12 min late | 284 · 10 days |
| 15:00 | 86.5% | 1.9 min late | 7.5 min late | 245 · 10 days |
| 16:00 | 77.6% | 2.6 min late | 10 min late | 830 · 10 days |
| 17:00 | 87.8% | 2.1 min late | 7.1 min late | 868 · 10 days |
| 18:00 | 89.2% | 1.3 min late | 6.5 min late | 120 · 10 days |
1 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
44 / 45 scheduled trips published at least one position across 5 service days (97.8%).
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 2, 2026 · 9 trips in the retained timetable · retained notices; capture coverage unverified
In short: 9 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.