Detour: Routes 57, 61, 62, 63, 74, 75, 87 during nightly Kichi Zībī Mīkan closures: May 07 2026 -
Until further notice, routes 57, 61, 62, 63, 74, 75, and 87 will detour on weeknights and weekends between 11:30 pm and 6 am in both directions around the Kichi Zībī Mīkan parkway, between Lincoln Fields station and Churchill Avenue.
Please allow extra time for your travels.
Affected stops
Bus Stop (560#) not in use · Routes · Alternate Stop
#3013 -- Dominion 2A · · 57 Tunney's Pasture · 61 Tunney's Pasture · 62 Tunney's Pasture · 63 Tunney's Pasture · 74 Tunney's Pasture · 75 Tunney's Pasture & N Rideau · 87 Tunney's Pasture · #4941 -- Richmond (south side) / Golden
#3013 -- Dominion 1A · · 57 Crystal Bay · 61 Stittsville · 62 Stittsville · 63 Innovation · 74 Nepean Woods · 75 Barrhaven · #4922 -- Richmond (north side) / Golden
#3014 -- Lincoln Fields 1A · · 61 Stittsville · 62 Stittsville · 63 Innovation · 74 Nepean Woods · 75 Barrhaven · 87 Baseline · #3014 -- Lincoln Fields 3B OR #3014 -- Lincoln Fields 5A
#4944 -- Woodroffe (west side) / Saunders* · · 87 Baseline · #6244 -- Woodroffe (west side) / Knightsbridge
#1832 -- Woodroffe (west side) / Richmond* · · 87 Baseline · #6244 -- Woodroffe (west side) / Knightsbridge
#4942 -- Woodroffe (east side) / Saunders* · · 87 Tunney's Pasture · #6472 -- Woodroffe (east side) / Knightsbridge
#2783 -- Woodroffe (east side) / Richmond* · · 87 Tunney's Pasture · #6472 -- Woodroffe (east side) / Knightsbridge
*These stops are already not in use due to the closure of Woodroffe Avenue (Byron/Richmond to Kichi Zībī Mīkan)
Detour routing
57 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing.
57 Bayshore: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe, right onto Carling, left onto J-Ramp, continue regular routing.
61 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing.
61 Stittsville / Terry Fox: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing.
62 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing.
62 Stittsville: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing.
63 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing.
63 Innovation/ Briarbrook: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing.
74 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing.
74 Limebank: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing.
75 Tunney's Pasture & N Rideau: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing.
75 Barrhaven Centre / Cambrian: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing.
87 Baseline: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe, right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing.
87 Tunney's Pasture: From Woodroffe and Byron, turn right onto Byron, continue on Richmond, left onto Churchill, right onto Scott to regular route.
Detour Map+1 more notice
No 87 trips cancelled now · 0 did not run in NovemberCancellations →
Previous measure: 81.5% of arrivals were within five minutes of the timetable (11,059 arrivals over 17 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.
No retained notice returned; this does not prove zero cancellations.
Trips needing investigation
0
0 of 95 trips with a usable feed window (0%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
95 with position · 0 to investigate · 20 excluded · 115 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 4, 2026, 6:47 p.m..
Coverage, exclusions and sources
20 scheduled trips were excluded from the position check for feed or identity gaps.
Published position coverage: 95 / 115 (82.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: Nov 4, 2026, 5:38 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.
What does the evidence show?
Predictions against the timetable
81.5%
of eligible provider predictions were within five minutes of the timetable.
Within five minutesOutside
Predictions in the source
11,059
Weekdays with evidence
17
Evidence window
Oct 6, 2026 – Nov 3, 2026
The hours we have evidence for
0595% · 392 predictions · 7 days
0690% · 607 predictions · 7 days
0791% · 578 predictions · 6 days
0896% · 584 predictions · 7 days
0975% · 77 predictions · 8 days
1574% · 860 predictions · 9 days
1673% · 1,001 predictions · 10 days
1780% · 1,076 predictions · 9 days
1886% · 275 predictions · 8 days
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
6 partial-capture days not counted.
What about time of day?
9 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: 21 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 12, 2026.
Early morning (4 to 6 a.m.)0%
Morning rush (6 to 9 a.m.)0%
Midday (9 a.m. to 3 p.m.)0%
Afternoon rush (3 to 6 p.m.)2%
Evening (6 to 10 p.m.)0%
Values and interpretation
1% of back-to-back buses on this route arrived bunched together: 100 of 8,093 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
1% of pairs (82) had a long gap: more than 1.75 times the planned wait between them.
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: none of the trips we could check.
When this route is usually busy
From the load level STO’s buses report, over the last eight weeks. A time is marked usually busy when at least half of the trips with a reading reached standing room or fuller.
No time of day was usually busy in the last eight weeks.
When this route is usually busy
Anokii-giizhigadoon
Samdi
Anamiegìjigad
Before 6 am
Usually seats0% of 92 trips
Not enough readings
Not enough readings
6 to 9 am
Usually seats36.7% of 335 trips
Not enough readings
Not enough readings
9 am to 3 pm
Usually seats9.1% of 99 trips
Not enough readings
Not enough readings
3 to 6 pm
Usually seats34.5% of 333 trips
Not enough readings
Not enough readings
6 to 10 pm
Usually seats1.6% of 62 trips
Not enough readings
Not enough readings
After 10 pm
Not enough readings
Not enough readings
Not enough readings
Based on 56 computed days.
Source: the occupancy status in STO’s public real-time vehicle feed, which STO sets from each bus’s load sensor (seats available under 60% full, standing room under 90%, full above 90%).
Each trip counts once per time of day, at the highest load it reported.
Reports of an empty bus are left out, because older records could not tell an empty bus from one with no sensor.
A time of day needs at least 12 trips on at least 4 different days before anything is shown. Holidays are counted with their day of the week.
Open history, reliability and route analysis
Route check
How route 87 has been running
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.
Based on 11,059 eligible provider predictions over 17 measured days, from Oct 6, 2026 to Nov 3, 2026.
Updated Nov 4, 2026, 5:32 p.m.
Where and when did predictions differ repeatedly?
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.
40 in 100 eligible predictions differed from the timetable by more than 5 minutes (161 predictions over 18 days).
Open this stop
These 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.
No trips start in the next 4 hoursChecks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?
0 of 95 checked trips need a closer look0 of 95 trips with enough public-feed evidence had no matching position over 7 days. 20 of 115 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
Nawaj na gii-mino-izhiwebad gaa-ishkwaa-aanjichigaadeg?
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 5,980 arrivals over 10 days; after has 795 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.
How this route is judged: Regular all-stop route
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.
What this data cannot prove
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.
Official current feed: explicit cancellations, skipped stops and active notices.
Matched observations: vehicle positions and settled predictions tied to the official schedule.
Official timetable: what was planned, kept separate from what was observed.
Rider and operator reports: leads about routes, times and places to investigate, not numeric proof by themselves.
Provisional results, published evidence
How did predictions compare with the timetable?
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
No repeated pattern below 70% is yet established across at least three service days.
Bus scheduled, gaawiin dash gii-waabandanziimin realtime
95 / 115 scheduled trips published at least one position across 5 service days (82.6%).
07:006 / 15 trips without a position60.0%
06:007 / 20 trips without a position65.0%
05:002 / 10 trips without a position80.0%
17:002 / 10 trips without a position80.0%
08:002 / 15 trips without a position86.7%
15:001 / 20 trips without a position95.0%
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
Trips scheduled that day
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 · 23 trips in the retained timetable · retained notices; capture coverage unverified
In short: 12 with a matched position · 0 with no matching position (to investigate) · 11 with an unknown outcome.