No 32 trips cancelled now · 5 did not run in NovemberCancellations →

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

STO ᐊᖁᑎᖓ 32: Plateau

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 29, 2026 – Nov 4, 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. Trips with any notice: 1.

Trips needing investigation

5 of 412 trips with a usable feed window (1.2%) had no matching position.

These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.

407 with position · 5 to investigate · 93 excluded · 505 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 5, 2026, 12:45 a.m..

Coverage, exclusions and sources

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

Published position coverage: 407 / 505 (80.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 5, 2026, 12:10 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

78.2%

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

Predictions in the source: 52,742
Weekdays with evidence: 17
Evidence window: Oct 6, 2026 – Nov 3, 2026

The hours we have evidence for

0090% · 461 predictions · 8 days
0598% · 623 predictions · 8 days
0694% · 1,589 predictions · 8 days
0787% · 1,944 predictions · 7 days
0878% · 2,056 predictions · 8 days
0985% · 1,419 predictions · 9 days
1092% · 1,079 predictions · 9 days
1194% · 1,304 predictions · 10 days
1290% · 1,176 predictions · 9 days
1395% · 1,213 predictions · 9 days
1495% · 1,111 predictions · 10 days
1562% · 1,918 predictions · 9 days
1658% · 2,081 predictions · 10 days
1756% · 2,393 predictions · 9 days
1879% · 1,567 predictions · 8 days
1983% · 1,171 predictions · 8 days
2086% · 1,119 predictions · 8 days
2191% · 1,149 predictions · 8 days
2284% · 1,242 predictions · 8 days
2390% · 1,210 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 5, 2026

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

Explore the dated evidence Source of this result

Buses arriving bunched

Last 28 days, October 8, 2026 to November 4, 2026: 20 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

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

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

Buses arriving bunched
ᐅᓪᓗᒥ ᐃᑲᕐᕋᖅ	Pairs checked	Bunched	Long gap
Early morning (4 to 6 a.m.)	528	0% (0)	0% (0)
Morning rush (6 to 9 a.m.)	7,046	4% (253)	3% (226)
Midday (9 a.m. to 3 p.m.)	9,436	0% (36)	0% (2)
Afternoon rush (3 to 6 p.m.)	8,888	7% (655)	7% (602)
Evening (6 to 10 p.m.)	6,229	2% (137)	0% (22)
Night (10 p.m. to 4 a.m.)	3,811	0% (11)	0% (3)

ᖃᓄᖅ ᐅᒃᑐᖅᑕᐅᒻᒪᖔᑦ →How we got this numberBunching and slow spots on every route →

Where this route is slowest

Slowest: CENTRE RIDEAU to KENT / SPARKS, 7.6 km/h actual against 13.4 km/h planned.

Where this route is slowest
ᐱᒋᐊᕐᕕᒃ	ᑐᕌᕐᕕᒃ	ᐅᖓᓯᒋᓂᖓ	Planned speed	Actual speed	Trips measured	Slow trips
CENTRE RIDEAU	KENT / SPARKS	1.2 km	13.4 km/h	7.6 km/h	491	41%
KENT / SPARKS	du PORTAGE/AUBRY	1.2 km	11.7 km/h	8.9 km/h	530	31%
TERRASSES de la CHAUDIÈRE	de l'HÔTEL-de-VILLE/LAURIER	750 m	12.6 km/h	11.4 km/h	573	11%
du PORTAGE/AUBRY	LAURIER/EDDY	470 m	12.9 km/h	13.1 km/h	552	9%
de l'HÔTEL-de-VILLE/LAURIER	CENTRE RIDEAU	2.5 km	11.7 km/h	15.3 km/h	479	0%
ALEXANDRE-TACHÉ/SAINT-JOSEPH	ALEXANDRE-TACHÉ/CHÂTEAUBRIAND	530 m	19.2 km/h	17.5 km/h	562	17%
PLATEAU/EUROPE	du PLATEAU/du MARIGOT	1.9 km	18.9 km/h	18.6 km/h	536	5%
VANIER/du PLATEAU	PLATEAU/EUROPE	2.2 km	23.7 km/h	18.7 km/h	472	14%

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

ᖃᓄᖅ ᐅᒃᑐᖅᑕᐅᒻᒪᖔᑦ →

ᓄᓇᓕᐅᑉ ᐊᖅᑯᑎᓂᒃ ᐱᓕᕆᓂᖓ ᐅᓇ ᐊᖅᑯᑎ ᖃᓂᒋᔮᓂ

ᐋᑐᕚ ᓄᓇᓕᖓᑕ ᑐᓴᖅᑎᑦᑎᓂᖏᑦ ᐊᖁᑏᑦ ᓴᓇᔭᐅᔪᑦ ᒪᑐᑦᑕᐅᔪᓪᓗ ᑲᑐᔾᔨᖃᑎᒌᓐᓂᖏᓐᓄᑦ, ᑕᒪᑐᒪ ᐊᖁᑎᐅᑉ ᖃᓂᒋᔮᓂ. ᖃᓂᒋᔭᐅᓂᖓ ᓴᖅᑭᑦᑎᙱᑦᑐᖅ ᐸᔅ ᐊᓯᐊᒍᑦ ᐃᖏᕐᕋᓂᖓᓂᒃ. ᑕᒪᑐᒥᖓ ᖃᐅᔨᔪᒪᒍᕕᑦ, ᐊᐅᓚᑦᑎᔨᐅᑉ ᑐᓴᒐᒃᓴᖏᑦ ᕿᒥᕐᕈᒋᑦ.

ᓄᓇᓕᐅᑉ ᐊᖁᑎᓂ ᓴᓇᓂᖏᑦ ᑎᑎᕋᖅᓯᒪᔪᑦ ᐅᖃᓕᒫᕋᔅᓴᐅᙱᑦᑐᑦ ᒫᓐᓇ.

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.

ᐱᕝᕕᖓ: ᐋᑐᕚ ᓄᓇᓕᐊ, ᐊᖅᑯᑎᓂ ᐱᓇᓱᐊᕐᓂᐅᔪᑦ ᒪᑐᓯᒪᔪᓪᓗ. ᑐᓴᒐᒃᓴᐃᑦ ᐊᑐᖅᑕᐅᔪᑦ Open Government Licence ᑯᑦ, ᐋᑐᕚ ᓄᓇᓕᐊ. ᓄᓇᓕᐊ ᐅᖃᖅᑐᖅ ᑎᑎᕋᖅᓯᒪᔪᑦ ᐱᐅᓂᖅᐹᒥ ᐱᓇᓱᐊᕈᓯᐅᓂᖏᓐᓂᒃ. ᐃᓘᓐᓇᖏᓐᓂᒃ ᐃᓗᓕᖃᙱᓐᓇᔭᖅᑐᑦ. ᐋᑐᕚ ᓄᓈᓖᑦ ᐊᖅᑯᑏᑦ ᓄᓇᙳᐊᖓ ↗

Cancellations on this route

What these words mean →

6 partial-capture days not counted.

4 scheduled trips with counted cancellation notices from Thu, Oct 8 to Wed, Nov 4.

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. (2), 2 p.m. (1), 4 p.m. (1)

Latest cancelled trips

Fri, Oct 30, scheduled 15:08
Fri, Oct 23, scheduled 15:08
Fri, Oct 23, scheduled 14:38
Thu, Oct 15, scheduled 16:20

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: 5 of 412 trips we could check.

Open the dated prediction analysis

ᐃᓱᓕᑦᑎᓂᖅ

What this route needs

Median provider predictions are 4 min later than the timetable in 3 hours of the day.

Predictions near the start are about 3.4 min later than the timetable, with a similar difference near the end. This does not establish the cause.

Predicted waits All measured hours are 1.4 min longer than scheduled waits.

17:00 has 56% of predictions within five minutes of the timetable, against 88% the rest of the day.

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, 20 hours with samples

00:00: 89.6% of final predictions within five minutes of the timetable, 461 predictions, typically 0.2 min late
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 98.4% of final predictions within five minutes of the timetable, 623 predictions, typically 1 min late
06:00: 93.5% of final predictions within five minutes of the timetable, 1,589 predictions, typically 0.8 min late
07:00: 87.3% of final predictions within five minutes of the timetable, 1,944 predictions, typically 1.8 min late
08:00: 77.6% of final predictions within five minutes of the timetable, 2,056 predictions, typically 1.8 min late
09:00: 85.2% of final predictions within five minutes of the timetable, 1,419 predictions, typically 1.6 min late
10:00: 91.7% of final predictions within five minutes of the timetable, 1,079 predictions, typically 1.3 min late
11:00: 93.7% of final predictions within five minutes of the timetable, 1,304 predictions, typically 0.9 min late
12:00: 89.8% of final predictions within five minutes of the timetable, 1,176 predictions, typically 1.5 min late
13:00: 95.1% of final predictions within five minutes of the timetable, 1,213 predictions, typically 1 min late
14:00: 95% of final predictions within five minutes of the timetable, 1,111 predictions, typically 0.6 min late
15:00: 62.4% of final predictions within five minutes of the timetable, 1,918 predictions, typically 3.6 min late
16:00: 57.8% of final predictions within five minutes of the timetable, 2,081 predictions, typically 4 min late
17:00: 56% of final predictions within five minutes of the timetable, 2,393 predictions, typically 4 min late
18:00: 79.3% of final predictions within five minutes of the timetable, 1,567 predictions, typically 1.9 min late
19:00: 82.9% of final predictions within five minutes of the timetable, 1,171 predictions, typically 1.4 min late
20:00: 85.7% of final predictions within five minutes of the timetable, 1,119 predictions, typically 1.3 min late
21:00: 91% of final predictions within five minutes of the timetable, 1,149 predictions, typically 1 min late
22:00: 84.4% of final predictions within five minutes of the timetable, 1,242 predictions, typically 1.6 min late
23:00: 90.2% of final predictions within five minutes of the timetable, 1,210 predictions, typically 1.5 min late

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	ᖃᖓ	ᐅᑦᑐᕋᖅᑕᐅᓯᒪᔪᖅ	Scenario or next investigation
ProblemPredictions later than timetable	15:00 to 18:00	4 min late	Recovery time at the terminal
ProblemPredicted spacing varies	All measured hours	1.4 min extra wait	Manage the headway
ProblemOne hour has a lower prediction match	17:00	56%	Operations, not the timetable

Measurements

Predictions later than timetable · 15:00 to 18:00: Measured arrivals 6,392; Hours affected 3; Spread 11.3 min; Median delay 4 min; Suggested running time change 4 min
Predicted spacing varies · All measured hours: ᓄᖃᕐᕕᐃᑦ 80; Extra wait share 27.3%; Matched arrivals 9,375; ᐅᑕᖅᑭᓂᖅ ᐃᓚᔭᐅᔪᖅ 1.4 min; Scheduled wait 5.2 min
One hour has a lower prediction match · 17:00: ᐃᑲᕐᕋᖅ 17:00; ᐱᕕᒃᓴᖓᓂ 56%; Measured arrivals 2,393; Shortfall 32.4 pts; Route median on time 88.4%

Open history, reliability and route analysis

Route check

How route 32 has been running

A short summary of what we know. We say so when we cannot answer a question.

Bottom line

Provider predictions often differed from the timetable; actual arrivals were not independently measured.

78 in 100 eligible predictions were within 5 minutes of the timetable · 52,742 predictions checked

Prediction sample size: Larger sample

Based on 52,742 eligible provider predictions over 17 measured days, from Oct 6, 2026 to Nov 3, 2026.

Updated Nov 4, 2026, 11: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.

17–18: 44 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,393 predictions over 9 days).
16–17: 42 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,081 predictions over 10 days).
15–16: 38 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,918 predictions over 9 days).

No current official notice matches this route.

Prediction differences by stop

LAURIER/EDDY
42 in 100 eligible predictions differed from the timetable by more than 5 minutes (704 predictions over 18 days).
Open this stop
du PORTAGE/AUBRY
42 in 100 eligible predictions differed from the timetable by more than 5 minutes (702 predictions over 18 days).
Open this stop
ALEXANDRE-TACHÉ/MILLAR
39 in 100 eligible predictions differed from the timetable by more than 5 minutes (711 predictions over 18 days).
Open this stop
ALEXANDRE-TACHÉ/CHÂTEAUBRIAND
39 in 100 eligible predictions differed from the timetable by more than 5 minutes (713 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.

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?: 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?: 5 of 412 checked trips need a closer look5 of 412 trips with enough public-feed evidence had no matching position over 7 days. 93 of 505 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 11.8 min (positive means later; negative means earlier)78 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
What wait did provider predictions imply?: 6.6 min average predicted wait1.4 min beyond the scheduled wait, based on 9,375 eligible predictions at 80 high-frequency stops over 14 days.

ᐊᐅᓪᓚᖅᑕᕐᕕᐅᓂᖏᑦ ᐊᓯᔾᔨᕐᓂᖏᓐᓂᒃ ᕿᒥᕐᕈᓂᖅ

ᓴᖅᑭᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᖏᑦ ᐅᓪᓗᖏᑦ: ᓯᕗᓂᐊᓂ ᑭᖑᓂᐊᓂᓗ

ᐅᓇ ᒫᓐᓇ ᐊᐅᓚᓂᕐᒧᑦ ᐸᕐᓇᐅᑎ ᓇᓪᓕᐅᓇᐃᓪᓗᒍ ᓯᕗᓪᓕᐅᔪᒧᑦ ᐸᕐᓇᐅᑎᒧᑦ. ᐸᕐᓇᐅᑎᒥ ᐊᓯᔾᔨᕐᓂᑦ ᐸᕐᓇᓯᒪᔪᓂᒃ ᓇᓗᓇᐃᖅᓯᔪᑦ. ᐃᖏᕐᕋᓂᖅ ᐊᐅᓚᓚᐅᕐᓂᖓᓂᒃ ᓇᓗᓇᐃᖅᓯᖏᑦᑐᑦ.

Current published schedule began November 2, 2026

ᐅᓪᓗᖅ ᓂᕈᐊᖅᑕᐅᓯᒪᔪᖅ ᐊᑐᓂ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐅᓪᓗᓂ ᐃᑲᕐᕋᓂᓪᓗ ᓴᖅᑭᑕᐅᓯᒪᔪᓂᑦ

ᑕᑯᓐᓇᕈᑦᑕᖅᐳᒍᑦ ᓯᕗᓪᓕᖅᐹᖅ ᓇᒡᒐᔾᔭᐅ ᓄᑖᑦ ᐊᐅᓚᓂᕐᒧᑦ ᐸᕐᓇᐅᑎᑦ ᐱᒋᐊᓚᐅᖅᑎᓪᓗᒋᑦ. ᐊᒻᒪ ᓇᒡᒐᔾᔭᐅ ᐱᓇᓱᐊᕈᓯᕐᒥᒃ ᓯᕗᓂᐊᒍᑦ. ᓈᓴᐅᑎᑦ ᑕᒪᕐᒥᒃ ᐱᔭᐅᔪᑦ ᐱᑕᖃᕐᓂᐊᖅᑐᓂᑦ ᒐᕙᒪᐅᑉ GTFS ᑐᓴᒐᒃᓴᖏᓐᓂᑦ. ᐊᑎᖏᑦ ᐊᑖᓂ ᐃᓗᓕᖃᖅᑐᑦ.

ᐅᓪᓗᑦ ᓂᕈᐊᖅᓯᒪᔭᑎᑦ ᐊᑕᐅᓯᖅ ᐅᖓᑖᓄᓪᓗ ᐊᐅᓚᓂᖓ ᐊᓯᔾᔨᖅᑕᐅᓯᒪᔪᖅ. ᐅᓇ ᖁᕕᐊᓱᐊᕐᕕᐅᓂᖓᓄᑦ ᐅᕝᕙᓘᓐᓃᑦ ᐊᔾᔨᐅᙱᑦᑐᒥᒃ ᐊᐅᓚᓂᖃᕐᓂᖓᓄᑦ ᐱᔾᔪᑎᖃᖅᑐᖅ. ᐱᓇᓱᐊᕐᕕᐅᔪᓂ ᐅᓪᓗᓂ ᐊᐅᓚᓂᖓ ᐅᒃᓱᓂᖓᓂᒃ ᑐᑭᖃᙱᑦᑐᖅ.

ᓯᕗᓂᐊᓂ

ᐱᔨᑦᑎᕋᐅᑎᐅᑉ ᐅᓪᓗᖓ ᕿᒥᕐᕈᐊᖅᑕᐅᔪᖅ: October 26, 2026

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 0
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 0
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 0
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: —–—

ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᓯᒋᐊᕈᑎᖓ: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

ᓄᑖᖅ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐸᕐᓇᐅᑎ

ᐱᔨᑦᑎᕋᐅᑎᐅᑉ ᐅᓪᓗᖓ ᕿᒥᕐᕈᐊᖅᑕᐅᔪᖅ: November 2, 2026

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 101
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 81
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 3
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 05:06–00:37 next day

Operator calendar-date records: 1 added · 0 removed

ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᓯᒋᐊᕈᑎᖓ: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

ᐱᔨᑦᑎᕋᐅᑎᑦ ᐱᐅᓯᕚᓕᓚᐅᖅᐸᑦ ᐊᓯᔾᔨᕐᓂᐅᑉ ᑭᖑᓂᐊᒍᑦ?

ᑎᑭᓐᓂᖏᑦ ᓇᓗᓇᐃᖅᓯᒪᔪᑦ ᐊᔾᔨᒌᙱᓐᓂᖏᑦ ᖃᐅᔨᓴᕐᓂᐊᖅᐸᕗᑦ. 14 ᐅᓪᓗᓂ ᐊᓯᔾᔨᕐᓂᖓᑕ ᓯᕗᓂᖓᓂ ᑭᖑᓂᖓᓂᓗ. ᓴᖅᑭᑎᑦᑎᓂᐊᖅᐳᒍᑦ ᒪᕐᕉᒃ ᐱᑕᖃᓕᕋᐃᒐᒃ ᐱᔨᑦᑎᕐᕕᐅᔪᓂᒃ ᐅᓪᓗᓂᒃ 7 ᐅᖓᑖᓄᓪᓗ, ᑎᑭᓐᓂᕐᓂᓪᓗ 200 ᐅᖓᑖᓄᓪᓗ.

Still collecting: before has 29,033 arrivals over 10 days; after has 4,353 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 6, 2026 to November 3, 2026

Within 5 minutes of schedule: 78.2%
Eligible predictions checked: 52,742
Weekdays with data: 17
95th-percentile predicted delay: 11.8 min late

Patterns by hour (20)

Patterns by hour (20)
ᐃᑲᕐᕋᖅ	ᐱᕕᒃᓴᖓᓂ	Median	95th percentile	ᓇᓗᓇᐃᖅᓯᔾᔪᑎᑦ
00:00	89.6%	0.2 min late	5.9 min late	461 · 8 days
05:00	98.4%	1 min late	4.2 min late	623 · 8 days
06:00	93.5%	0.8 min late	5.1 min late	1,589 · 8 days
07:00	87.3%	1.8 min late	6.5 min late	1,944 · 7 days
08:00	77.6%	1.8 min late	13.4 min late	2,056 · 8 days
09:00	85.2%	1.6 min late	8.7 min late	1,419 · 9 days
10:00	91.7%	1.3 min late	5.6 min late	1,079 · 9 days
11:00	93.7%	0.9 min late	5.1 min late	1,304 · 10 days
12:00	89.8%	1.5 min late	5.8 min late	1,176 · 9 days
13:00	95.1%	1 min late	4.9 min late	1,213 · 9 days
14:00	95.0%	0.6 min late	4.7 min late	1,111 · 10 days
15:00	62.4%	3.6 min late	13 min late	1,918 · 9 days
16:00	57.8%	4 min late	20.8 min late	2,081 · 10 days
17:00	56.0%	4 min late	15.3 min late	2,393 · 9 days
18:00	79.3%	1.9 min late	9.7 min late	1,567 · 8 days
19:00	82.9%	1.4 min late	7.3 min late	1,171 · 8 days
20:00	85.7%	1.3 min late	7.2 min late	1,119 · 8 days
21:00	91.0%	1 min late	7.1 min late	1,149 · 8 days
22:00	84.4%	1.6 min late	7.9 min late	1,242 · 8 days
23:00	90.2%	1.5 min late	5.5 min late	1,210 · 8 days

3 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.

Scheduled bus, but not observed in realtime

421 / 505 scheduled trips published at least one position across 5 service days (83.4%).

07:0019 / 50 trips without a position62.0%
06:0014 / 40 trips without a position65.0%
18:005 / 20 trips without a position75.0%
19:005 / 20 trips without a position75.0%
20:005 / 20 trips without a position75.0%
21:005 / 20 trips without a position75.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.

Service day

November 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

November 4, 2026 · 101 trips in the retained timetable · retained notices; capture coverage unverified

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

05:06– 05:48
Trip sto:63296340Insufficient coverage or identity; outcome unknown
05:26– 06:08
Trip sto:63296339Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 6:02 a.m. EST; not actual start or end times.
05:46– 06:28
Trip sto:63296131Vehicle position matchedFirst / last feed position: 5:48 a.m. EST / 6:20 a.m. EST; not actual start or end times.
06:06– 06:50
Trip sto:63296341Vehicle position matchedFirst / last feed position: 6:05 a.m. EST / 6:44 a.m. EST; not actual start or end times.
06:10– 06:49
Trip sto:63296332Vehicle position matchedFirst / last feed position: 6:08 a.m. EST / 6:46 a.m. EST; not actual start or end times.
06:16– 07:00
Trip sto:63295982Vehicle position matchedFirst / last feed position: 6:16 a.m. EST / 6:55 a.m. EST; not actual start or end times.
06:24– 07:08
Trip sto:63296342Vehicle position matchedFirst / last feed position: 6:24 a.m. EST / 7:05 a.m. EST; not actual start or end times.
06:35– 07:20
Trip sto:63295983Vehicle position matchedFirst / last feed position: 6:35 a.m. EST / 7:25 a.m. EST; not actual start or end times.
06:40– 07:20
Trip sto:63296331Vehicle position matchedFirst / last feed position: 6:22 a.m. EST / 7:15 a.m. EST; not actual start or end times.
06:45– 07:32
Trip sto:63295984Vehicle position matchedFirst / last feed position: 6:40 a.m. EST / 7:30 a.m. EST; not actual start or end times.
06:53– 07:40
Trip sto:63295976Vehicle position matchedFirst / last feed position: 6:52 a.m. EST / 7:39 a.m. EST; not actual start or end times.
07:02– 07:51
Trip sto:63295979Vehicle position matchedFirst / last feed position: 7:01 a.m. EST / 7:50 a.m. EST; not actual start or end times.

· Open all evidence for this day

ᑐᕌᕝᑦ

ᑖᓐᓇ ᐅᖃᐅᓯᒧᑦ ᐊᓯᔾᔨᖅᓯᒪᔪᖅ ᑐᕌᕝᑦᐅᕗᖅ.

Help improve it

About 48% of this site is translated so far. The rest is shown in English.

Read this page in English

This translation is a draft.

This page is a machine draft in Inuktitut (ᐃᓄᒃᑎᑐᑦ), the language of the Inuit. It was prepared without review by its speakers, and is waiting for one. Speakers and the community are invited to correct it. We will replace it with their words. Ottawa is on the unceded territory of the Anishinabe Algonquin Nation.

Cette page est une ébauche automatique en inuktitut (ᐃᓄᒃᑎᑐᑦ), la langue des Inuits. Elle a été préparée sans révision par ses locuteurs, et attend l’un d’eux. Les locuteurs et la communauté sont invités à la corriger. Nous la remplacerons par leurs mots. Ottawa se trouve sur le territoire non cédé de la Nation algonquine anishinabe (Anishinabe Algonquin Nation).