Map
FRPrevious measure: 83.7% of arrivals were within five minutes of the timetable (20,159 arrivals over 18 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.
Every 30 to 60 min
Scheduled service and available evidence
Evidence period: Oct 29, 2026 – Nov 4, 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: 3 trips with qualifying later matching vehicle observations. Trips with any notice: 3.
3
3 of 185 trips with a usable feed window (1.6%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
182 with position · 3 to investigate · 0 excluded · 185 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 5, 2026, 7:55 a.m..
0 of 8 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.
0 scheduled trips were excluded from the position check for feed or identity gaps.
Published position coverage: 182 / 185 (98.4%). 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 5, 2026, 6:39 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
83.7%
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 5, 2026
2 partial-capture days not counted.
18 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 8, 2026 to November 4, 2026: 25 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.
1% of back-to-back buses on this route arrived bunched together: 17 of 3,320 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
1% of pairs (17) had a long gap: more than 1.75 times the planned wait between them.
| Time of day | Pairs checked | Bunched | Long gap |
|---|---|---|---|
| Morning rush (6 to 9 a.m.) | 465 | 0% (0) | 0% (0) |
| Afternoon rush (3 to 6 p.m.) | 1,888 | 1% (17) | 1% (12) |
| Evening (6 to 10 p.m.) | 967 | 0% (0) | 1% (5) |
Slowest: TAPIOLA / RUSHFORD to JOHNSTON / CONROY, 22.9 km/h actual against 14.3 km/h planned.
| From | To | Distance | Planned speed | Actual speed | Trips measured | Slow trips |
|---|---|---|---|---|---|---|
| TAPIOLA / RUSHFORD | JOHNSTON / CONROY | 1.6 km | 14.3 km/h | 22.9 km/h | 284 | 0% |
| GREENBORO B | TAPIOLA / RUSHFORD | 4.4 km | 24.8 km/h | 22.9 km/h | 280 | 5% |
| LORRY GREENBERG / CONROY | JOHNSTON / CONROY | 2.5 km | 40.5 km/h | 25.5 km/h | 300 | 62% |
| JOHNSTON / CONROY | TAPIOLA / BRANDO | 1.4 km | 20.9 km/h | 25.7 km/h | 302 | 4% |
A slow trip took at least 1.5 times the planned time.
Road work and event road closures the City of Ottawa has published, measured as near this route’s path. Near is not proof that the bus is detoured: check the operator’s own alerts for that.
The City’s road work list could not be read right now.
A route counts as near when its timetable path passes within 40 m of the City’s mapped closure; a stop counts when it is within 75 m.
Source: City of Ottawa traffic events (road work and closures). Contains information licensed under the Open Government Licence, City of Ottawa. The City says this list is best effort and may be incomplete. City of Ottawa traffic map ↗
2 partial-capture days not counted.
1 scheduled trips with counted cancellation notices from Thu, Oct 8 to Wed, Nov 4.
Not counted: 10 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
Hours with the most cancellations: 10 a.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: 3 of 185 trips we could check.
Verdict
Median provider predictions are 3.2 to 5.1 min later than the timetable in 2 hours of the day.
Predictions near the start are about 4.3 min later than the timetable, with a similar difference near the end. This does not establish the cause.
16:00 has 44% of predictions within five minutes of the timetable, against 86% the rest of the day.
Only 98% of scheduled trips were seen; the rest are not counted as missed.
Next investigation: test terminal recovery and the preceding trip against operational records. Predictions alone do not establish the cause.
| What | When | Measured | Scenario or next investigation |
|---|---|---|---|
| ProblemPredictions later than timetable | 07:00 · 16:00 | 3.2 min late · 5.1 min late | Recovery time at the terminal |
| ProblemOne hour has a lower prediction match | 16:00 | 44% | 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.
84 in 100 eligible predictions were within 5 minutes of the timetable · 20,159 predictions checkedPrediction sample size: Larger sample
Based on 20,159 eligible provider predictions over 18 measured days, from Oct 7, 2026 to Nov 4, 2026.
Updated Nov 5, 2026, 7: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 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.
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 the first Monday after the new schedule began and the Monday one week earlier. Every figure comes from the retained 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.
Service date checked: October 26, 2026
Operator calendar-date records: 0 added · 2 removed
Feed fingerprint: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad
Service date checked: November 2, 2026
Operator calendar-date records: 0 added · 2 removed
Feed fingerprint: 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 11,187 arrivals over 10 days; after has 4,481 arrivals over 4 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 7, 2026 to November 4, 2026
| Hour | On time | Median | 95th percentile | Evidence |
|---|---|---|---|---|
| 06:00 | 100.0% | 1.8 min late | 3.7 min late | 330 · 11 days |
| 07:00 | 57.0% | 3.2 min late | 14 min late | 660 · 11 days |
| 08:00 | 94.2% | 1.9 min late | 5.1 min late | 675 · 11 days |
| 09:00 | 82.3% | 2.8 min late | 6.6 min late | 671 · 11 days |
| 10:00 | 85.4% | 1.8 min late | 11.1 min late | 669 · 11 days |
| 11:00 | 92.0% | 1.5 min late | 6.4 min late | 671 · 11 days |
| 12:00 | 97.9% | 0.5 min late | 3.8 min late | 671 · 11 days |
| 13:00 | 94.9% | 0.7 min late | 3.1 min late | 671 · 11 days |
| 14:00 | 85.7% | 1.3 min late | 9.2 min late | 671 · 11 days |
| 15:00 | 83.8% | 1 min late | 6.1 min late | 951 · 11 days |
| 16:00 | 44.0% | 5.1 min late | 19.4 min late | 712 · 11 days |
| 17:00 | 79.3% | 1.2 min late | 7.8 min late | 647 · 11 days |
| 18:00 | 83.0% | 2 min late | 7.9 min late | 1,001 · 11 days |
| 19:00 | 76.9% | 2.9 min late | 8.9 min late | 636 · 11 days |
| 20:00 | 99.6% | 2.4 min late | 4.6 min late | 671 · 11 days |
| 21:00 | 88.7% | 2.1 min late | 6.1 min late | 671 · 11 days |
| 22:00 | 85.7% | 1.5 min late | 8.5 min late | 673 · 11 days |
| 23:00 | 92.6% | 1.3 min late | 10.6 min late | 598 · 11 days |
2 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
182 / 185 scheduled trips published at least one position across 5 service days (98.4%).
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 4, 2026 · 37 trips in the retained timetable · retained notices; capture coverage unverified
In short: 35 with a matched position · 2 with no matching position (to investigate) · 0 with an unknown outcome.