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 · 4 did not run in NovemberCancellations →
Previous measure: 86.4% of arrivals were within five minutes of the timetable (42,050 arrivals over 27 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.
87
Mìkana 87: Tunney's Pasture ⇄ Baseline
Endaso 15 biinish 30 min
ijàTunney's Pasture3 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)
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: 6.
Trips needing investigation
5
5 of 615 trips with a usable feed window (0.8%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
610 with position · 5 to investigate · 0 excluded · 615 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 4, 2026, 2:13 p.m..
Coverage, exclusions and sources
0 of 12 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: 610 / 615 (99.2%). 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, 12:39 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
86.4%
of eligible provider predictions were within five minutes of the timetable.
Within five minutesOutside
Predictions in the source
42,050
Weekdays with evidence
19
Evidence window
Oct 6, 2026 – Nov 3, 2026
The hours we have evidence for
0697% · 400 predictions · 10 days
0797% · 909 predictions · 12 days
0892% · 1,521 predictions · 12 days
0991% · 1,714 predictions · 12 days
1090% · 1,751 predictions · 14 days
1193% · 1,860 predictions · 14 days
1292% · 1,868 predictions · 14 days
1387% · 1,869 predictions · 14 days
1489% · 1,897 predictions · 14 days
1579% · 1,801 predictions · 14 days
1658% · 1,820 predictions · 14 days
1772% · 1,412 predictions · 14 days
1892% · 1,294 predictions · 14 days
1989% · 884 predictions · 14 days
2082% · 760 predictions · 10 days
2181% · 763 predictions · 10 days
2296% · 129 predictions · 10 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
2 partial-capture days not counted.
What about time of day?
17 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.
Morning rush (6 to 9 a.m.)0%
Midday (9 a.m. to 3 p.m.)1%
Afternoon rush (3 to 6 p.m.)2%
Evening (6 to 10 p.m.)0%
Night (10 p.m. to 4 a.m.)0%
Values and interpretation
1% of back-to-back buses on this route arrived bunched together: 313 of 37,417 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
1% of pairs (266) had a long gap: more than 1.75 times the planned wait between them.
8 scheduled trips with counted cancellation notices from Wed, Oct 7 to Tue, Nov 3.
Not counted: 14 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. (3), 2 p.m. (2), 8 a.m. (1)
Latest cancelled trips
Tue, Nov 3, scheduled 17:37
Mon, Nov 2, scheduled 16:28
Mon, Nov 2, scheduled 14:27
Wed, Oct 28, scheduled 08:40
Tue, Oct 27, scheduled 16:50
OC Transpo gives no reason for single trips, so none is shown.
Did not come (no bus seen, no notice), last 7 days: 4 of 615 trips we could check.
Open the dated prediction analysis
Ishkwaa-inendamowin
What this route needs
Median provider predictions are 3.6 min later than the timetable in 1 hours of the day.
Predictions near the start are about 3.3 min later than the timetable; the difference grows by another 2.1 min along the route.
16:00 has 58% of predictions within five minutes of the timetable, against 90% the rest of the day.
Only 99% of scheduled trips were seen; the rest are not counted as missed.
Scenario: 4 min more running time on 86 trips. The schedule-block model estimates 20 additional buses; fleet and workforce feasibility are unverified.
Assumptions: published departure times, trip blocks and service pattern stay fixed while running time changes. A scheduler must test headways, transfers, recovery, fleet circulation, operator shifts, labour rules and cost before use.
Final provider predictions within five minutes of the timetable, by hour, last 14 days, 17 hours with samples
00:00: not enough data00
01:00: not enough data01
02:00: not enough data02
03:00: not enough data03
04:00: not enough data04
05:00: not enough data05
06:00: 96.8% of final predictions within five minutes of the timetable, 400 predictions, typically 1 min late06
07:00: 96.6% of final predictions within five minutes of the timetable, 909 predictions, typically 0.1 min early07
08:00: 91.8% of final predictions within five minutes of the timetable, 1,521 predictions, typically 0.3 min late08
09:00: 90.5% of final predictions within five minutes of the timetable, 1,714 predictions, typically 1.2 min late09
10:00: 89.9% of final predictions within five minutes of the timetable, 1,751 predictions, typically 0.5 min late10
11:00: 93.1% of final predictions within five minutes of the timetable, 1,860 predictions, typically 1 min late11
12:00: 91.8% of final predictions within five minutes of the timetable, 1,868 predictions, typically 1.2 min late12
13:00: 87.3% of final predictions within five minutes of the timetable, 1,869 predictions, typically 1.1 min late13
14:00: 88.6% of final predictions within five minutes of the timetable, 1,897 predictions, typically 0.7 min late14
15:00: 79.4% of final predictions within five minutes of the timetable, 1,801 predictions, typically 2 min late15
16:00: 57.6% of final predictions within five minutes of the timetable, 1,820 predictions, typically 3.6 min late16
17:00: 72.3% of final predictions within five minutes of the timetable, 1,412 predictions, typically 2.2 min late17
18:00: 91.7% of final predictions within five minutes of the timetable, 1,294 predictions, typically 0.7 min late18
19:00: 88.8% of final predictions within five minutes of the timetable, 884 predictions, typically 1.4 min late19
20:00: 82.2% of final predictions within five minutes of the timetable, 760 predictions, typically 1.9 min late20
21:00: 81.4% of final predictions within five minutes of the timetable, 763 predictions, typically 1.6 min late21
22:00: 96.1% of final predictions within five minutes of the timetable, 129 predictions, typically 1.8 min late22
23:00: not enough data23
90% or more of predictions within five minutes
80 to 90% of predictions within five minutes
under 80% of predictions within five minutes
not enough data
Findings
What
Aaniin apii
Tibàdjigade
Scenario or next investigation
Problem!Predictions later than timetable
16:00
3.6 min late
More running time
Problem!One hour has a lower prediction match
16:00
58%
Operations, not the timetable
Caveat?Coverage gap
All measured hours
99%
More observation, not a service change
Measurements
Predictions later than timetable · 16:00
Measured arrivals 1,820
Hours affected 1
Spread 13.7 min
Median delay 3.6 min
Suggested running time change 3.6 min
One hour has a lower prediction match · 16:00
Dibaa'igan 16:00
Weweni apii 57.6%
Measured arrivals 1,820
Shortfall 32.3 pts
Route median on time 89.9%
Coverage gap · All measured hours
Ijitchigewin 99.5%
Trips with a matching position 99.2%
Anokii-giizhigadoon 5
Trips with a matching position 610
Maajaawinan ozhibii'igaadegin 615
16:00 30 → to 3416:00 35 → to 39
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, but check the problem times below.
Based on 42,050 eligible provider predictions over 27 measured days, from Oct 6, 2026 to Nov 3, 2026.
Updated Nov 4, 2026, 12: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.
16–17: 42 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,820 predictions over 14 days).
0 of 12Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?
5 of 615 checked trips need a closer look5 of 615 trips with enough public-feed evidence had no matching position over 7 days. 0 of 615 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 22,730 arrivals over 14 days; after has 7,415 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.
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
1 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
Bus scheduled, gaawiin dash gii-waabandanziimin realtime
610 / 615 scheduled trips published at least one position across 5 service days (99.2%).
07:002 / 41 trips without a position95.1%
08:002 / 49 trips without a position95.9%
17:001 / 38 trips without a position97.4%
05:000 / 5 trips without a position100.0%
06:000 / 20 trips without a position100.0%
09:000 / 44 trips without a position100.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 · 107 trips in the retained timetable · retained notices; capture coverage unverified
In short: 106 with a matched position · 1 with no matching position (to investigate) · 0 with an unknown outcome.
05:59– 06:14
Trip 10048030Vehicle position matchedFirst / last feed position: 6:01 a.m. EST / 6:12 a.m. EST; not actual start or end times.
06:27– 06:42
Trip 18016030Vehicle position matchedFirst / last feed position: 5:52 a.m. EST / 6:36 a.m. EST; not actual start or end times.
06:29– 06:44
Trip 3882030Vehicle position matchedFirst / last feed position: 6:25 a.m. EST / 6:47 a.m. EST; not actual start or end times.
06:48– 07:03
Trip 3370030Vehicle position matchedFirst / last feed position: 6:12 a.m. EST / 7:04 a.m. EST; not actual start or end times.
06:48– 07:03
Trip 5521030Vehicle position matchedFirst / last feed position: 6:42 a.m. EST / 7:13 a.m. EST; not actual start or end times.
07:05– 07:20
Trip 8202030Vehicle position matchedFirst / last feed position: 7:05 a.m. EST / 7:19 a.m. EST; not actual start or end times.
07:10– 07:29
Trip 30955030Vehicle position matchedFirst / last feed position: 6:37 a.m. EST / 7:25 a.m. EST; not actual start or end times.
07:17– 07:32
Trip 30641030Vehicle position matchedFirst / last feed position: 7:09 a.m. EST / 7:38 a.m. EST; not actual start or end times.
07:23– 07:52
Trip 32845030Vehicle position matchedFirst / last feed position: 7:20 a.m. EST / 7:50 a.m. EST; not actual start or end times.
07:32– 07:47
Trip 16628030Vehicle position matchedFirst / last feed position: 7:26 a.m. EST / 7:46 a.m. EST; not actual start or end times.
07:38– 08:07
Trip 24966030Vehicle position matchedFirst / last feed position: 6:55 a.m. EST / 8:03 a.m. EST; not actual start or end times.
07:39– 08:08
Trip 17800030Vehicle position matchedFirst / last feed position: 6:53 a.m. EST / 8:10 a.m. EST; not actual start or end times.