Stop impacts: #3019 -- Pinecrest A and B relocation: September 01 2026 -
Updates to routing and alternate stops for routes 301, 303, 404, 406, and 454 made on September 14, 2026.
From 5:00 am on Wednesday, September 9, until further notice, all bus platforms at Pinecrest Station will be relocated outside of the station bus loop and onto Pinecrest Road for ongoing work.
As a result, routes 60, 61, 62, 63, 66, 67, 81, 82, 301, 303, 404, 406, 454, and 691 will service alternate stops.
Please allow extra time for your travels.
Affected stops
Bus Stop (560#) not in use · Routes · Alternate Stop
#3019 -- Pinecrest A · · 61 Stittsville · 62 Stittsville · 63 Innovation / Briarbrook · 81 Tunney's Pasture · 82 Baseline · 301 Richmond / Stittsville · 303 Carp · 404 Canadian Tire Centre · 406 Canadian Tire Centre · 454 Terry Fox · 691 Omer-Deslauriers · TEMP -- Pinecrest (west-side) / station entrance
#3019 -- Pinecrest B · · 60 Terry Fox / Tunney's Pasture · 66 Tunneys Pasture · 67 Terry Fox / Tunney's Pasture · #5595 -- Pinecrest (east-side) / Queensview
#3019 -- Pinecrest B · · 61 Tunney's Pasture & N Rideau · 62 Tunney's Pasture · 63 Tunney's Pasture No service to Pinecrest Station, September 19 – 20 · TEMP -- Pinecrest (east-side) / Iris (EB 417 on-ramp from Pinecrest)
#3019 -- Pinecrest B · · 301 Bayshore / Carlingwood · 303 Carlingwood · #1946 -- Pinecrest Mall
#3019 -- Pinecrest B · · 404 Tunney's Pasture · 406 Limebank · 454 Lansdowne · TEMP -- Pinecrest (east-side) / Iris (EB 417 on-ramp from Pinecrest)
Detour routing
60 Terry Fox / Tunney's Pasture: From Pinecrest northbound, do not enter station, service temporary platform on Pinecrest at Quensview, continue regular route.
61 Tunney's Pasture: From Pinecrest northbound, do not enter station, service temporary platform on Pinecrest at Quensview, continue regular route.
61 Stittsville: From Highway 417 westbound off-ramp, do not enter station, left onto Pinecrest, service temporary stop outside station, right onto ramp to Highway 417 westbound.
62 Tunney's Pasture: From Pinecrest northbound, service temporary platform on Pinecrest at Quensview, continue regular route.
62 Stittsville: From Highway 417 westbound off-ramp, do not enter station, left onto Pinecrest, service temporary stop outside station, right onto ramp to Highway 417 westbound.
63 Tunney's Pasture: From Pinecrest northbound, do not enter station, service temporary platform on Pinecrest at Quensview, continue regular route.
63 Innovation/ Briarbrook: From Highway 417 westbound off-ramp, do not enter station, left onto Pinecrest, service temporary stop outside station, right onto ramp to Highway 417 westbound.
66 Tunney's Pasture: From Pinecrest northbound, do not enter station, service temporary platform on Pinecrest at Quensview, continue regular route.
67 Terry Fox / Tunney's Pasture: From Pinecrest northbound, do not enter station, service temporary platform on Pinecrest at Quensview, continue regular route.
81 Tunney's Pasture: From Pinecrest southbound, do not enter station, service, temporary stop outside station, continue Greenbank to regular route.
82 Baseline: From Pinecrest southbound, do not enter station, service, temporary stop outside station, continue Greenbank to regular route.
301 Richmond / Stittsville: From Highway 417 westbound off-ramp at Pinecrest, left onto Pinecrest Service temporary stop on Pinecrest, right onto Ramp to Highway 417 wesbtound.
301 Bayshore: From Highway 417 eastbound off-ramp at Pinecrest, continue Iris, Keep left and continue Mall Roadway, use Pinecrest Mall loop to turnaround, left onto Mall Roadway, right onto to remain on Iris, right onto Pinecrest, right onto Ramp to Highway 417 Eastbound, continue regular route.
303 Carp: From Highway 417 westbound off-ramp at Pinecrest, left onto Pinecrest Service temporary stop on Pinecrest, right onto Ramp to Highway 417 wesbtound.
303 Carlingwood: From Highway 417 eastbound off-ramp at Pinecrest, continue Iris, Keep left and continue Mall Roadway, use Pinecrest Mall loop to turnaround, left onto Mall Roadway, right onto to remain on Iris, right onto Pinecrest, right onto Ramp to Highway 417 Eastbound, continue regular route.
404 Tunney's Pasture: From Highway 417 eastbound off-ramp at Pinecrest, left onto Pinecrest, right onto Highway 417 eastbound, service stop on Pinecrest on-ramp.
404 Canadian Tire Centre: From Highway 417 westbound off-ramp at Pinecrest, left onto Pinecrest, service temporary stop, right onto ramp to Highway 417 westound.
406 Limebank: From Highway 417 eastbound off-ramp at Pinecrest, left onto Pinecrest, right onto Highway 417 eastbound, service stop on Pinecrest on-ramp.
406 Canadian Tire Centre: From Highway 417 westbound off-ramp at Pinecrest, left onto Pinecrest, service temporary stop, right onto ramp to Highway 417 westound.
454 Lansdowne: From Highway 417 eastbound off-ramp at Pinecrest, left onto Pinecrest, right onto Highway 417 eastbound, service stop on Pinecrest on-ramp.
454 Terry Fox: From Highway 417 westbound off-ramp at Pinecrest, left onto Pinecrest, service temporary stop, right onto ramp to Highway 417 westound.
691 Omer-Deslauriers: From Pinecrest southbound, do not enter station, continue southbound and service temporary stop, continue regular route.
No 81 trips cancelled now · 5 did not run in NovemberCancellations →
Previous measure: 70.6% of arrivals were within five minutes of the timetable (146,779 arrivals over 27 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.
Live times did not load
Showing the timetable. Buses may run early or late.
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: 8 trips with qualifying later matching vehicle observations. Trips with any notice: 11.
Trips needing investigation
6
6 of 468 trips with a usable feed window (1.3%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
462 with position · 6 to investigate · 0 excluded · 468 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 5, 2026, 3:55 a.m..
Coverage, exclusions and sources
0 of 9 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: 462 / 468 (98.7%). 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, 3:08 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.
What does the evidence show?
Predictions against the timetable
70.6%
of eligible provider predictions were within five minutes of the timetable.
Within five minutesOutside
Predictions in the source
146,779
Weekdays with evidence
19
Evidence window
Oct 6, 2026 – Nov 3, 2026
The hours we have evidence for
0090% · 1,279 predictions · 14 days
0585% · 473 predictions · 11 days
0688% · 3,220 predictions · 13 days
0784% · 4,030 predictions · 15 days
0867% · 4,708 predictions · 15 days
0973% · 5,148 predictions · 15 days
1069% · 4,824 predictions · 15 days
1168% · 4,755 predictions · 15 days
1279% · 4,888 predictions · 15 days
1378% · 4,878 predictions · 15 days
1469% · 4,917 predictions · 15 days
1565% · 4,839 predictions · 15 days
1660% · 4,900 predictions · 15 days
1754% · 5,135 predictions · 15 days
1856% · 5,105 predictions · 15 days
1971% · 4,675 predictions · 15 days
2068% · 4,252 predictions · 15 days
2169% · 4,232 predictions · 15 days
2268% · 3,674 predictions · 15 days
2375% · 2,181 predictions · 15 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 5, 2026
2 partial-capture days not counted.
What about time of day?
20 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.
Morning rush (6 to 9 a.m.)1%
Midday (9 a.m. to 3 p.m.)0%
Afternoon rush (3 to 6 p.m.)1%
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: 483 of 93,827 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
0% of pairs (397) had a long gap: more than 1.75 times the planned wait between them.
12 scheduled trips with counted cancellation notices from Thu, Oct 8 to Wed, Nov 4.
Not counted: 31 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
Hours with the most cancellations: 6 p.m. (2), 7 a.m. (1), 8 a.m. (1)
Latest cancelled trips
Sat, Oct 31, scheduled 11:28
Fri, Oct 30, scheduled 20:02
Thu, Oct 29, scheduled 21:02
Wed, Oct 28, scheduled 17:40
Wed, Oct 28, scheduled 12:36
OC Transpo gives no reason for single trips, so none is shown.
Did not come (no bus seen, no notice), last 7 days: 5 of 468 trips we could check.
Open the dated prediction analysis
Ishkwaa-inendamowin
What this route needs
Median provider predictions are 3.1 to 3.8 min later than the timetable in 6 hours of the day.
Predictions near the start are about 3.7 min later than the timetable, with a similar difference near the end. This does not establish the cause.
Next investigation: test terminal recovery and the preceding trip against operational records. Predictions alone do not establish the cause.
Final provider predictions within five minutes of the timetable, by hour, last 14 days, 21 hours with samples
00:00: 90% of final predictions within five minutes of the timetable, 1,279 predictions, typically 0.4 min late00
01:00: not enough data01
02:00: not enough data02
03:00: not enough data03
04:00: not enough data04
05:00: 84.6% of final predictions within five minutes of the timetable, 473 predictions, typically 1.3 min late05
06:00: 88.3% of final predictions within five minutes of the timetable, 3,220 predictions, typically 1 min late06
07:00: 84.4% of final predictions within five minutes of the timetable, 4,030 predictions, typically 2.1 min late07
08:00: 67% of final predictions within five minutes of the timetable, 4,708 predictions, typically 3.3 min late08
09:00: 73.1% of final predictions within five minutes of the timetable, 5,148 predictions, typically 1.9 min late09
10:00: 68.8% of final predictions within five minutes of the timetable, 4,824 predictions, typically 2.5 min late10
11:00: 68.3% of final predictions within five minutes of the timetable, 4,755 predictions, typically 2.9 min late11
12:00: 78.8% of final predictions within five minutes of the timetable, 4,888 predictions, typically 2.4 min late12
13:00: 78.3% of final predictions within five minutes of the timetable, 4,878 predictions, typically 1.3 min late13
14:00: 69.1% of final predictions within five minutes of the timetable, 4,917 predictions, typically 1.9 min late14
15:00: 64.6% of final predictions within five minutes of the timetable, 4,839 predictions, typically 3.5 min late15
16:00: 60% of final predictions within five minutes of the timetable, 4,900 predictions, typically 3.8 min late16
17:00: 53.7% of final predictions within five minutes of the timetable, 5,135 predictions, typically 4.5 min late17
18:00: 56.2% of final predictions within five minutes of the timetable, 5,105 predictions, typically 3.8 min late18
19:00: 71.4% of final predictions within five minutes of the timetable, 4,675 predictions, typically 2.5 min late19
20:00: 68.3% of final predictions within five minutes of the timetable, 4,252 predictions, typically 3.1 min late20
21:00: 68.9% of final predictions within five minutes of the timetable, 4,232 predictions, typically 2.8 min late21
22:00: 68% of final predictions within five minutes of the timetable, 3,674 predictions, typically 2.8 min late22
23:00: 75.1% of final predictions within five minutes of the timetable, 2,181 predictions, typically 2.1 min late23
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
08:00 · 15:00 to 19:00 · 20:00
3.3 min late … 3.1 min late
Recovery time at the terminal
Measurements
Predictions later than timetable · 15:00 to 19:00
Measured arrivals 19,979
Hours affected 4
Spread 12.2 min
Median delay 3.8 min
Suggested running time change 3.8 min
Predictions later than timetable · 08:00
Measured arrivals 4,708
Hours affected 1
Spread 9.7 min
Median delay 3.3 min
Suggested running time change 3.3 min
Predictions later than timetable · 20:00
Measured arrivals 4,252
Hours affected 1
Spread 7.3 min
Median delay 3.1 min
Suggested running time change 3.1 min
08:00 62 → to 6508:00 52 → to 5515:00 69 → to 7315:00 61 → to 6516:00 67 → to 7116:00 61 → to 6517:00 62 → to 6617:00 57 → to 6118:00 59 → to 6318:00 54 → to 5820:00 55 → to 5820:00 50 → to 53
Open history, reliability and route analysis
Route check
How route 81 has been running
A short summary of what we know. We say so when we cannot answer a question.
Ishkwàdj ikidowin
Provider predictions often differed from the timetable; actual arrivals were not independently measured.
Based on 146,779 eligible provider predictions over 27 measured days, from Oct 6, 2026 to Nov 3, 2026.
Updated Nov 5, 2026, 2:32 a.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.
17–18: 46 in 100 eligible predictions differed from the timetable by more than 5 minutes (5,135 predictions over 15 days).
18–19: 44 in 100 eligible predictions differed from the timetable by more than 5 minutes (5,105 predictions over 15 days).
16–17: 40 in 100 eligible predictions differed from the timetable by more than 5 minutes (4,900 predictions over 15 days).
15–16: 35 in 100 eligible predictions differed from the timetable by more than 5 minutes (4,839 predictions over 15 days).
1 current notice affects this route
• Stop impacts: #3019 -- Pinecrest A and B relocation
40 in 100 eligible predictions differed from the timetable by more than 5 minutes (948 predictions over 29 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.
0 of 9Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?
6 of 468 checked trips need a closer look6 of 468 trips with enough public-feed evidence had no matching position over 7 days. 0 of 468 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 76,487 arrivals over 14 days; after has 32,861 arrivals over 6 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
11 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
462 / 468 scheduled trips published at least one position across 1 service days (98.7%).
10:002 / 28 trips without a position92.9%
19:001 / 24 trips without a position95.8%
21:001 / 24 trips without a position95.8%
11:001 / 28 trips without a position96.4%
16:001 / 28 trips without a position96.4%
05:000 / 5 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 4, 2026 · 71 trips in the retained timetable · retained notices; capture coverage unverified
In short: 69 with a matched position · 2 with no matching position (to investigate) · 0 with an unknown outcome.
05:31– 06:30
Trip 36881040Vehicle position matchedFirst / last feed position: 5:19 a.m. EST / 6:28 a.m. EST; not actual start or end times.
06:06– 07:07
Trip 16455040Vehicle position matchedFirst / last feed position: 5:54 a.m. EST / 7:08 a.m. EST; not actual start or end times.
06:10– 07:03
Trip 36975040Vehicle position matchedFirst / last feed position: 5:43 a.m. EST / 7:04 a.m. EST; not actual start or end times.
06:34– 07:28
Trip 13170040Vehicle position matchedFirst / last feed position: 6:29 a.m. EST / 7:24 a.m. EST; not actual start or end times.
06:36– 07:40
Trip 31048040Vehicle position matchedFirst / last feed position: 6:24 a.m. EST / 7:40 a.m. EST; not actual start or end times.
07:06– 08:03
Trip 28801040Vehicle position matchedFirst / last feed position: 6:45 a.m. EST / 8:00 a.m. EST; not actual start or end times.
07:06– 08:13
Trip 34901040Vehicle position matchedFirst / last feed position: 7:06 a.m. EST / 8:11 a.m. EST; not actual start or end times.
07:31– 08:43
Trip 14614040Vehicle position matchedFirst / last feed position: 7:26 a.m. EST / 8:41 a.m. EST; not actual start or end times.
07:34– 08:33
Trip 36623040Vehicle position matchedFirst / last feed position: 7:30 a.m. EST / 8:39 a.m. EST; not actual start or end times.
08:06– 09:17
Trip 4711040Vehicle position matchedFirst / last feed position: 8:01 a.m. EST / 9:11 a.m. EST; not actual start or end times.
08:07– 09:03
Trip 29135040Vehicle position matchedFirst / last feed position: 8:09 a.m. EST / 9:01 a.m. EST; not actual start or end times.
08:36– 09:41
Trip 23914040Vehicle position matchedFirst / last feed position: 8:40 a.m. EST / 9:48 a.m. EST; not actual start or end times.