Stop impacts: #4036 -- Holly Acres (south-side) / Ramp temporary relocation: October 30 2026 - From 11:00 pm on Monday, November 2, until 11:00 pm on Friday, December 4, stop #4036 -- Holly Acres (south-side) / Ramp will be temporarily relocated 120 metres closer to Richmond Road due to construction work near the Highway 417 off-ramp. There will be no detours, but the routes below will be impacted by the stop relocation: 57 Carling Campus ~ Complexe Carling 60 Terry Fox / Tunney's Pasture 61 Tunney's Pasture & N Rideau 62 Tunney's Pasture 63 Tunney's Pasture 66 Tunneys Pasture 67 Terry Fox / Tunney's Pasture 88 Hurdman 261 Tunney's Pasture 262 Tunney's Pasture 263 Tunney's Pasture 265 Tunney's Pasture 266 Tunney's Pasture+2 more notice

No 63 trips cancelled now · 0 did not run in NovemberCancellations →

Previous measure: 89.8% of arrivals were within five minutes of the timetable (18,020 arrivals over 21 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.

STO route 63: Pointe-Gatineau

Toward La Cité1 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)

Quai local de la GAPPE #618 min sched.
de la GAPPE/CARMEN19 min sched.
de la GAPPE/OXFORD20 min sched.
SAINT-LOUIS/de la GAPPE21 min sched.
SAINT-LOUIS/BLAIS23 min sched.
SAINT-LOUIS/JOSEPH-BÉLANGER24 min sched.
SAINT-LOUIS/FORTIN24 min sched.
SAINT-LOUIS/GRÉBER25 min sched.
SAINT-ANTOINE/AIMÉ25 min sched.
SAINT-ANTOINE/ONÉSIME26 min sched.
de POINTE-GATINEAU/SAINT-ANTOINE27 min sched.
de POINTE-GATINEAU/COUSINEAU28 min sched.
LAFRENIÈRE/MOREAU29 min sched.
LAFRENIÈRE/LOUIS-RIEL0 min
LOUIS-RIEL/LOUIS-JOLLIET1 min
de l'ÉRABLIÈRE/PIERRE-RADISSON2 min
de l'ÉRABLIÈRE/de l'ABBÉ-GUINGUET2 min
de l'ÉRABLIÈRE/PIERRE-PAPIN3 min
des ANCIENS/LAFONTAINE4 min
de la SAVANE/SAINT-ANTOINE6 min
LES PROMENADES6 min
de la SAVANE/SAINT-JOSAPHAT7 min
de la SAVANE/SAINT-ROSAIRE8 min
de la SAVANE/FLORIAN-THIBAULT9 min
de LAUSANNE/de la SAVANE9 min
de LAUSANNE/d'ALBANEL10 min
de LAUSANNE/de DUCHESNAY11 min
de la CITÉ/LAMARCHE11 min
de la CITÉ/LAMARCHE12 min
de la CITÉ/de la GAPPE13 min
de la GAPPE/de la CITÉ14 min
de la GAPPE/de ROUVILLE14 min
QUAI LOCAL de la CITÉ arrivée15 min

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 27, 2026 – Nov 2, 2026

Scheduled trips with cancellation notices

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: 3.

Trips needing investigation

0 of 226 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.

226 with position · 0 to investigate · 21 excluded · 247 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 3, 2026, 3:24 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.

21 scheduled trips were excluded from the position check for feed or identity gaps.

Published position coverage: 226 / 247 (91.5%). 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 3, 2026, 1:49 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

89.8%

of eligible provider predictions were within five minutes of the timetable.

Predictions in the source: 18,020
Weekdays with evidence: 16
Evidence window: Oct 5, 2026 – Nov 2, 2026

The hours we have evidence for

6 a.m.96% · 492 predictions · 8 days
7 a.m.94% · 546 predictions · 7 days
8 a.m.92% · 583 predictions · 8 days
9 a.m.73% · 379 predictions · 8 days
10 a.m.85% · 423 predictions · 11 days
11 a.m.93% · 609 predictions · 12 days
12 p.m.83% · 622 predictions · 12 days
1 p.m.86% · 668 predictions · 12 days
2 p.m.92% · 570 predictions · 13 days
3 p.m.91% · 990 predictions · 12 days
4 p.m.81% · 932 predictions · 13 days
5 p.m.92% · 1,012 predictions · 12 days
6 p.m.92% · 658 predictions · 11 days
7 p.m.95% · 426 predictions · 8 days
8 p.m.89% · 407 predictions · 7 days
9 p.m.98% · 453 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 3, 2026

7 partial-capture days not counted.

What about time of day?

16 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.

Explore the dated evidence Source of this result

Buses arriving bunched

Last 28 days, October 6, 2026 to November 2, 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.

Values and interpretation

0% of back-to-back buses on this route arrived bunched together: 5 of 5,382 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

0% of pairs (7) had a long gap: more than 1.75 times the planned wait between them.

Buses arriving bunched
Time of day	Pairs checked	Bunched	Long gap
Morning rush (6 to 9 a.m.)	1,859	0% (0)	0% (0)
Midday (9 a.m. to 3 p.m.)	106	0% (0)	0% (0)
Afternoon rush (3 to 6 p.m.)	2,618	0% (5)	0% (7)
Evening (6 to 10 p.m.)	799	0% (0)	0% (0)

How this is measured →How we got this numberBunching and slow spots on every route →

Where this route is slowest

Slowest: QUAI LOCAL de la CITÉ #6 to LES PROMENADES, 8.4 km/h actual against 17.8 km/h planned.

Where this route is slowest
From	To	Distance	Planned speed	Actual speed	Trips measured	Slow trips
QUAI LOCAL de la CITÉ #6	LES PROMENADES	1.9 km	17.8 km/h	8.4 km/h	284	80%
Quai local de la GAPPE #6	SAINT-LOUIS/BLAIS	1.6 km	23.2 km/h	9.6 km/h	230	74%
Quai local de la GAPPE #6	Stop name not found	1.8 km	25.4 km/h	11.6 km/h	36	81%
LES PROMENADES	SAINT-LOUIS/MARENGÈRE	3.4 km	17.5 km/h	17.4 km/h	289	0%
SAINT-LOUIS/FORTIN	LES PROMENADES	3.6 km	19.1 km/h	18 km/h	274	1%
LES PROMENADES	QUAI LOCAL de la CITÉ arrivée	2.6 km	19.1 km/h	19.1 km/h	266	0%
SAINT-LOUIS/MARENGÈRE	SAINT-LOUIS/BLAIS	620 m	19.8 km/h	22.8 km/h	305	5%
Stop name not found	SAINT-LOUIS/FORTIN	430 m	25.6 km/h	27.6 km/h	38	8%

A slow trip took at least 1.5 times the planned time.

How this is measured →

Cancellations on this route

What these words mean →

6 partial-capture days not counted.

1 scheduled trips with counted cancellation notices from Tue, Oct 6 to Mon, Nov 2.

Not counted: 2 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.

Hours with the most cancellations: 3 p.m. (1)

Latest cancelled trips

Tue, Oct 27, scheduled 15:43

A cause is shown only when STO’s own alert for that trip gives one.

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	Weekdays	Saturdays	Sundays
Before 6 am	Usually seats0% of 21 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats0% of 330 trips	Not enough readings	Not enough readings
9 am to 3 pm	Usually seats0% of 399 trips	Usually seats0% of 70 trips	Usually seats0% of 63 trips
3 to 6 pm	Usually seats2.2% of 403 trips	Usually seats0% of 44 trips	Usually seats0% of 50 trips
6 to 10 pm	Usually seats1% of 315 trips	Usually seats0% of 15 trips	Usually seats0% of 13 trips
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 the dated prediction analysis

Verdict

What this route needs

Median provider predictions are 3.6 min later than the timetable in 1 hours of the day.

Only 92% of scheduled trips were seen; the rest are not counted as missed.

Scenario: 4 min more running time on 3 trips. The schedule-block model adds no 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 data
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: not enough data
06:00: 95.7% of final predictions within five minutes of the timetable, 492 predictions, typically 0.6 min late
07:00: 94% of final predictions within five minutes of the timetable, 546 predictions, typically 1.2 min late
08:00: 92.1% of final predictions within five minutes of the timetable, 583 predictions, typically 0.8 min late
09:00: 73.4% of final predictions within five minutes of the timetable, 379 predictions, typically 3.6 min late
10:00: 84.6% of final predictions within five minutes of the timetable, 423 predictions, typically 1.7 min late
11:00: 93.4% of final predictions within five minutes of the timetable, 609 predictions, typically 1.6 min late
12:00: 83.3% of final predictions within five minutes of the timetable, 622 predictions, typically 2.3 min late
13:00: 86.2% of final predictions within five minutes of the timetable, 668 predictions, typically 2.2 min late
14:00: 91.6% of final predictions within five minutes of the timetable, 570 predictions, typically 1.2 min late
15:00: 90.9% of final predictions within five minutes of the timetable, 990 predictions, typically 1.7 min late
16:00: 80.6% of final predictions within five minutes of the timetable, 932 predictions, typically 2.4 min late
17:00: 91.9% of final predictions within five minutes of the timetable, 1,012 predictions, typically 1.2 min late
18:00: 92.1% of final predictions within five minutes of the timetable, 658 predictions, typically 2.2 min late
19:00: 94.8% of final predictions within five minutes of the timetable, 426 predictions, typically 0.9 min late
20:00: 89.2% of final predictions within five minutes of the timetable, 407 predictions, typically 2.2 min late
21:00: 97.8% of final predictions within five minutes of the timetable, 453 predictions, typically 1.9 min late
22:00: not enough data
23:00: not enough data

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	When	Measured	Scenario or next investigation
ProblemPredictions later than timetable	09:00	3.6 min late	More running time
CaveatCoverage gap	All measured hours	92%	More observation, not a service change

Measurements

Predictions later than timetable · 09:00: Measured arrivals 379; Hours affected 1; Spread 4.5 min; Median delay 3.6 min; Suggested running time change 3.6 min
Coverage gap · All measured hours: Target 99.5%; Trips with a matching position 91.5%; Service days 5; Trips with a matching position 226; Scheduled trips 247

Open history, reliability and route analysis

Route check

How route 63 has been running

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.

90 in 100 eligible predictions were within 5 minutes of the timetable · 18,020 predictions checked

Prediction sample size: Larger sample

Based on 18,020 eligible provider predictions over 21 measured days, from Oct 5, 2026 to Nov 2, 2026.

Updated Nov 3, 2026, 2: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.

No current official notice matches this route.

Prediction differences by stop

QUAI LOCAL de la CITÉ #6
47 in 100 eligible predictions differed from the timetable by more than 5 minutes (331 predictions over 24 days).
Open this stop
Quai local de la GAPPE #6
40 in 100 eligible predictions differed from the timetable by more than 5 minutes (324 predictions over 24 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.

Check every trip and date

Open a time period to see each service day, scheduled trip, feed gap, observed public vehicle ID, and the exact counts behind this summary.

What riders want to know

Is any trip cancelled right now?: 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?: 0 of 226 checked trips need a closer look0 of 226 trips with enough public-feed evidence had no matching position over 7 days. 21 of 247 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
How did provider predictions differ from the timetable?: At the 95th percentile, the predicted difference was 6.1 min (positive means later; negative means earlier)90 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
What wait did provider predictions imply?: No route-level result meets the evidence threshold yet. This does not mean gaps did not happen.

Schedule change check

Published schedule: before and after

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 November 1, 2026

Selected service day from each published schedule

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.

Before

Service date checked: October 26, 2026

Scheduled trips: 0
Distinct scheduled stops: 0
Distinct published paths: 0
Published service span: —–—

Feed fingerprint: ef904cebae995976 · cdda76b5-d299-4755-bb81-ca8cd4d16647

New schedule

Service date checked: November 2, 2026

Scheduled trips: 43
Distinct scheduled stops: 60
Distinct published paths: 2
Published service span: 5:47 a.m.–9:40 p.m.

Operator calendar-date records: 1 added · 0 removed

Feed fingerprint: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

Did service improve after the change?

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 10,376 arrivals over 13 days; after has 1,015 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.

See the definitions, thresholds and evidence order

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 5, 2026 to November 2, 2026

Within 5 minutes of schedule: 89.8%
Eligible predictions checked: 18,020
Weekdays with data: 16
95th-percentile predicted delay: 6.1 min late

Patterns by hour (17)

Patterns by hour (17)
Hour	On time	Median	95th percentile	Evidence
05:00	87.3%	1.7 min late	5.9 min late	55 · 4 days
06:00	95.7%	0.6 min late	4.3 min late	492 · 8 days
07:00	94.0%	1.2 min late	5.1 min late	546 · 7 days
08:00	92.1%	0.8 min late	5.6 min late	583 · 8 days
09:00	73.4%	3.6 min late	8.1 min late	379 · 8 days
10:00	84.6%	1.7 min late	5.7 min late	423 · 11 days
11:00	93.4%	1.6 min late	5 min late	609 · 12 days
12:00	83.3%	2.3 min late	15.5 min late	622 · 12 days
13:00	86.2%	2.2 min late	11 min late	668 · 12 days
14:00	91.6%	1.2 min late	6.4 min late	570 · 13 days
15:00	90.9%	1.7 min late	5.4 min late	990 · 12 days
16:00	80.6%	2.4 min late	6.6 min late	932 · 13 days
17:00	91.9%	1.2 min late	5.3 min late	1,012 · 12 days
18:00	92.1%	2.2 min late	5.1 min late	658 · 11 days
19:00	94.8%	0.9 min late	4.1 min late	426 · 8 days
20:00	89.2%	2.2 min late	5.6 min late	407 · 7 days
21:00	97.8%	1.9 min late	4 min late	453 · 8 days

No repeated pattern below 70% is yet established across at least three service days.

Scheduled bus, but not observed in realtime

226 / 247 scheduled trips published at least one position across 5 service days (91.5%).

05:001 / 5 trips without a position80.0%
07:004 / 20 trips without a position80.0%
19:002 / 10 trips without a position80.0%
20:002 / 10 trips without a position80.0%
21:002 / 10 trips without a position80.0%
18:002 / 12 trips without a position83.3%

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.

Service day

November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026 October 27, 2026

November 2, 2026 · 43 trips in the retained timetable · retained notices; capture coverage unverified

In short: 24 with a matched position · 0 with no matching position (to investigate) · 19 with an unknown outcome.

05:47– 06:11
Trip sto:63296464Vehicle position matchedFirst / last feed position: 5:51 a.m. EST / 6:10 a.m. EST; not actual start or end times.
06:14– 06:38
Trip sto:63296486Vehicle position matchedFirst / last feed position: 6:11 a.m. EST / 6:17 a.m. EST; not actual start or end times.
06:17– 06:41
Trip sto:63296463Vehicle position matchedFirst / last feed position: 6:11 a.m. EST / 6:17 a.m. EST; not actual start or end times.
06:47– 07:11
Trip sto:63296466Insufficient coverage or identity; outcome unknown
07:14– 07:38
Trip sto:63296481Insufficient coverage or identity; outcome unknown
07:17– 07:41
Trip sto:63296468Insufficient coverage or identity; outcome unknown
07:44– 08:08
Trip sto:63296487Insufficient coverage or identity; outcome unknown
07:49– 08:13
Trip sto:63296469Insufficient coverage or identity; outcome unknown
08:14– 08:38
Trip sto:63296488Insufficient coverage or identity; outcome unknown
08:17– 08:41
Trip sto:63296467Vehicle position matchedFirst / last feed position: 8:45 a.m. EST / 8:47 a.m. EST; not actual start or end times.
08:44– 09:08
Trip sto:63296489Vehicle position matchedFirst / last feed position: 8:45 a.m. EST / 9:05 a.m. EST; not actual start or end times.
09:17– 09:41
Trip sto:63296465Vehicle position matchedFirst / last feed position: 9:10 a.m. EST / 9:41 a.m. EST; not actual start or end times.

· Open all evidence for this day