Site usage analyticsWhat is collected
Usage analytics is on by default to improve Otranspo. You can turn it off here.
Loading: Loading the route history. Live times above are ready to use.
Would you count on route 105?
No sign-in needed. A vote from a device that is not signed in counts a little less than one from an account, and a person who rates many routes counts a little less on each, so no one voice outweighs the rest.
Rider evidence
Signals below are moderated community aggregates, not official operator notices or reliability scores.
You can report without signing in. Anonymous reports count a little less when we calculate public patterns. You can add an account after submitting.
Report a specific problem
Emergency: call 9-1-1. Check official OC Transpo or STO notices before travelling.
Source: currently imported OC Transpo GTFS. Check the Alerts panel for current official notices and each stop page for observed departures.
Scheduled service and available evidence
Evidence period: Oct 14, 2026 – Oct 20, 2026
3
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: 5 trips with qualifying later matching vehicle observations. Trips with any notice: 8. 1 partial-capture day not counted.
2
2 of 630 trips with a usable feed window (0.3%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
628 with position · 2 to investigate · 48 excluded · 678 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Oct 21, 2026, 7:20 p.m..
0 of 12 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.
48 scheduled trips were excluded from the position check for feed or identity gaps.
Published position coverage: 628 / 678 (92.6%). 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: Oct 21, 2026, 6:19 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
88.2%
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: Oct 21, 2026
3 partial-capture days not counted.
24 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, September 23, 2026 to October 20, 2026: 18 days counted.
10 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: September 25, 2026, September 26, 2026, September 27, 2026, September 28, 2026, September 29, 2026, September 30, 2026, October 1, 2026, October 2, 2026, October 8, 2026, October 15, 2026.
0% of back-to-back buses on this route arrived bunched together: 160 of 35,804 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
0% of pairs (75) had a long gap: more than 1.75 times the planned wait between them.
| Time of day | Pairs checked | Bunched | Long gap |
|---|---|---|---|
| Early morning (4 to 6 a.m.) | 3,435 | 0% (1) | 0% (0) |
| Morning rush (6 to 9 a.m.) | 3,823 | 0% (6) | 0% (4) |
| Midday (9 a.m. to 3 p.m.) | 9,410 | 0% (16) | 0% (5) |
| Afternoon rush (3 to 6 p.m.) | 4,624 | 2% (99) | 1% (56) |
| Evening (6 to 10 p.m.) | 5,878 | 0% (15) | 0% (2) |
| Night (10 p.m. to 4 a.m.) | 8,634 | 0% (23) | 0% (8) |
Slowest: RIDEAU B to LEES A, 14.1 km/h actual against 15.5 km/h planned.
| From | To | Distance | Planned speed | Actual speed | Trips measured | Slow trips |
|---|---|---|---|---|---|---|
| RIDEAU B | LEES A | 2.3 km | 15.5 km/h | 14.1 km/h | 161 | 2% |
| SOUTH KEYS A | GREENBORO A | 730 m | 23.1 km/h | 19.8 km/h | 856 | 20% |
| BOWESVILLE B | LEITRIM B | 2.3 km | 27.9 km/h | 21.6 km/h | 22 | 18% |
| ST-LAURENT A | HURDMAN C | 3.2 km | 17.7 km/h | 22.6 km/h | 685 | 1% |
| UPLANDS A | AIRPORT / AÉROPORT (A) | 1.6 km | 23.3 km/h | 25 km/h | 800 | 15% |
| HURDMAN C | BILLINGS BRIDGE 1A (A) | 3.3 km | 29.8 km/h | 29 km/h | 704 | 3% |
| GREENBORO B | SOUTH KEYS D | 800 m | 32.4 km/h | 31.1 km/h | 869 | 14% |
| SOUTH KEYS D | AIRPORT / AÉROPORT (A) | 4.1 km | 28.1 km/h | 32.6 km/h | 866 | 2% |
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.
Road work
Bank between Riverside W/B and Collins
Mar 25, 2026, 7:00 a.m. to Dec 31, 2026, 5:00 p.m.
Bank lane reductions in both directions between Riverside westbound and Collins due to construction. Cyclists and pedestrians not affected. From March 25 to December 2026.
The City marks this as affecting transit.
about 0 m from the route
City record updated Sep 8, 2026, 4:24 p.m..
Road work
Pl Pickering Place between Tremblay and Bannermount
Aug 17, 2026, 12:00 a.m. to Oct 31, 2026, 5:00 p.m.
Pl Pickering Place closed between Tremblay and Bannermount due to construction. Access for local traffic maintained. From 12:00am, 17/08/26 to 5:00pm, 31/10/26
about 0 m from the route
City record updated Sep 4, 2026, 4:04 p.m..
Road work
KING EDWARD between SOMERSET / MARIE-CURIE, PRIVE and TEMPLETON
Oct 6, 2026, 12:00 a.m. to Nov 6, 2026, 5:00 p.m.
KING EDWARD off-peak lane reductions between SOMERSET / MARIE-CURIE, PRIVE and TEMPLETON due to construction. From 12:00am, 06/10/26 to 5:00pm, 06/11/26
The City marks this as affecting transit.
about 0 m from the route
City record updated Oct 9, 2026, 10:28 a.m..
Road work
LAURIER between CUMBERLAND and COPERNICUS
Oct 6, 2026, 12:00 a.m. to Nov 6, 2026, 5:00 p.m.
LAURIER off-peak lane reduction between CUMBERLAND and COPERNICUS due to construction, from October 6th to November 6th.
The City marks this as affecting transit.
about 1 m from the route
City record updated Oct 9, 2026, 11:12 a.m..
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 ↗
3 partial-capture days not counted.
8 scheduled trips with counted cancellation notices from Wed, Sep 23 to Tue, Oct 20.
Not counted: 23 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
Hours with the most cancellations: 4 p.m. (2), 1 a.m. (1), 5 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: 1 of 574 trips we could check.
Verdict
Wide prediction spread 17:00: the 95th percentile is 27.3 min later than the median.
Only 99% of scheduled trips were seen; the rest are not counted as missed.
| What | When | Measured | Scenario or next investigation |
|---|---|---|---|
| ProblemWide prediction spread | 17:00 | 27.3 min swing | Operations, not the timetable |
| CaveatCoverage gap | All measured hours | 99% | 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 in this dated sample.
88 in 100 eligible predictions were within 5 minutes of the timetable · 65,116 predictions checkedPrediction sample size: Larger sample
Based on 65,116 eligible provider predictions over 26 measured days, from Sep 22, 2026 to Oct 20, 2026.
Updated Oct 21, 2026, 6:33 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 repeated prediction-difference period has cleared the evidence threshold yet.
1 current notice affects this route
Prediction differences by stop
44 in 100 eligible predictions differed from the timetable by more than 5 minutes (248 predictions over 30 days).
Open this stop43 in 100 eligible predictions differed from the timetable by more than 5 minutes (248 predictions over 30 days).
Open this stop43 in 100 eligible predictions differed from the timetable by more than 5 minutes (247 predictions over 30 days).
Open this stop43 in 100 eligible predictions differed from the timetable by more than 5 minutes (247 predictions over 30 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 16, 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 12, 2026
Operator calendar-date records: 3 added · 5 removed
Feed fingerprint: 9de04e70fcc4165f · 54ca76e7-e78f-4623-a135-ab2c87e99d32
Service date checked: October 19, 2026
Operator calendar-date records: 0 added · 2 removed
Feed fingerprint: ec926fc0e161b73f · db43ff4c-ff08-4e90-845b-a8642cd1bcef
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 27,692 arrivals over 11 days; after has 12,519 arrivals over 5 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: September 22, 2026 to October 20, 2026
| Hour | On time | Median | 95th percentile | Evidence |
|---|---|---|---|---|
| 00:00 | 87.9% | 1.4 min late | 6.1 min late | 1,433 · 12 days |
| 01:00 | 82.5% | 1.7 min late | 8.8 min late | 1,335 · 12 days |
| 02:00 | 90.0% | 0.6 min late | 6 min late | 1,368 · 12 days |
| 03:00 | 87.5% | 0.6 min late | 7.6 min late | 1,286 · 13 days |
| 04:00 | 90.1% | 0.5 min late | 6.3 min late | 1,540 · 13 days |
| 05:00 | 83.0% | 1.5 min late | 7.3 min late | 1,545 · 13 days |
| 06:00 | 91.1% | 1.1 min late | 6.4 min late | 1,402 · 13 days |
| 07:00 | 88.2% | 1.1 min late | 6.5 min late | 1,344 · 13 days |
| 08:00 | 92.4% | 0.9 min late | 6.1 min late | 1,367 · 13 days |
| 09:00 | 92.5% | 0.8 min late | 5.7 min late | 1,252 · 13 days |
| 10:00 | 89.1% | 1 min late | 8.8 min late | 1,240 · 13 days |
| 11:00 | 85.5% | 1.7 min late | 6.4 min late | 1,224 · 13 days |
| 12:00 | 90.0% | 1.4 min late | 6.2 min late | 1,224 · 12 days |
| 13:00 | 89.0% | 0.3 min late | 7.7 min late | 1,210 · 12 days |
| 14:00 | 92.9% | 0.9 min late | 5.4 min late | 1,214 · 12 days |
| 15:00 | 85.7% | 0.7 min late | 9.6 min late | 1,293 · 12 days |
| 16:00 | 88.5% | 1.1 min late | 8.6 min late | 1,218 · 12 days |
| 17:00 | 76.2% | 2.1 min late | 29.3 min late | 1,145 · 12 days |
| 18:00 | 87.9% | 1.3 min late | 8.4 min late | 1,133 · 12 days |
| 19:00 | 88.6% | 1 min late | 6.3 min late | 1,277 · 12 days |
| 20:00 | 86.5% | 0.8 min late | 11.4 min late | 1,185 · 12 days |
| 21:00 | 87.3% | 1.1 min late | 6.8 min late | 1,173 · 12 days |
| 22:00 | 89.8% | 1 min late | 5.9 min late | 1,215 · 12 days |
| 23:00 | 88.7% | 1.1 min late | 6.2 min late | 1,216 · 12 days |
No repeated pattern below 70% is yet established across at least three service days.
573 / 581 scheduled trips published at least one position across 6 service days (98.6%).
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.
October 20, 2026 · 97 trips in the retained timetable · retained notices; capture coverage unverified
In short: 96 with a matched position · 0 with no matching position (to investigate) · 1 with an unknown outcome.
The current public route group, its published schedule variants and stop patterns, current operations, and reliability from matching eligible final provider predictions where available.
1 current GTFS route record variants are grouped by operator and public route number. Stop patterns remain tied to their published variant; aggregated reliability records are not merged into an invented percentile.