Detour Route 32 South: Route 32 diverted from Laval to Station Lyon.

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

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

ᐊᖁᑦ 32: Blair ⇄ Chapel Hill

30 ᐊᒻᒪ 31 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ

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

—

No retained notice returned; this does not prove zero cancellations.

Trips needing investigation

1 of 80 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.

79 with position · 1 to investigate · 0 excluded · 80 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 3, 2026, 11:49 p.m..

Coverage, exclusions and sources

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

Published position coverage: 79 / 80 (98.8%). 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, 11:09 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

58.3%

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

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

The hours we have evidence for

0589% · 253 predictions · 11 days
0688% · 761 predictions · 11 days
0757% · 700 predictions · 10 days
0858% · 750 predictions · 10 days
1440% · 350 predictions · 10 days
1568% · 650 predictions · 10 days
1664% · 710 predictions · 10 days
1743% · 750 predictions · 10 days
1865% · 730 predictions · 10 days
1928% · 120 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?

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

Values and interpretation

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

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

Buses arriving bunched
ᐅᓪᓗᒥ ᐃᑲᕐᕋᖅ	Pairs checked	Bunched	Long gap
Morning rush (6 to 9 a.m.)	3,521	0% (1)	0% (13)
Midday (9 a.m. to 3 p.m.)	34	0% (0)	0% (0)
Afternoon rush (3 to 6 p.m.)	1,679	0% (1)	0% (1)
Evening (6 to 10 p.m.)	817	0% (0)	0% (4)

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

Where this route is slowest

Slowest: PLACE D'ORLÉANS B to JEANNE D'ARC / INNES, 16.7 km/h actual against 21.2 km/h planned.

Where this route is slowest
ᐱᒋᐊᕐᕕᒃ	ᑐᕌᕐᕕᒃ	ᐅᖓᓯᒋᓂᖓ	Planned speed	Actual speed	Trips measured	Slow trips
PLACE D'ORLÉANS B	JEANNE D'ARC / INNES	3.4 km	21.2 km/h	16.7 km/h	135	13%
DÉCOEUR / JEROME JODOIN	JEANNE D'ARC / INNES	2.5 km	20.5 km/h	17.6 km/h	135	6%
CHAPEL HILL B	DÉCOEUR / JEROME JODOIN	3.5 km	25.3 km/h	19.3 km/h	133	25%
JEANNE D'ARC / INNES	PLACE D'ORLÉANS E	3.4 km	23.6 km/h	20.1 km/h	136	2%
JEANNE D'ARC / INNES	FERN CASEY / RENAUD	5 km	32 km/h	21.1 km/h	135	50%
PLACE D'ORLÉANS E	JEANNE D'ARC 2A	2.6 km	23.9 km/h	25.9 km/h	136	1%
JEANNE D'ARC 1B	PLACE D'ORLÉANS B	2.4 km	24.3 km/h	42.2 km/h	135	0%
BLAIR D	JEANNE D'ARC 1B	6.4 km	44.4 km/h	45.4 km/h	134	4%

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

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

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

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

ᐊᖁᑎᒥᒃ ᓴᓇᔪᑦ
Jeanne d'Arc between St-Joseph and Des Épinettes
Oct 26, 2026, 12:00 a.m. to Nov 20, 2026, 5:00 p.m.
Jeanne d'Arc off-peak lane reductions in both directions between St-Joseph and Des Épinettes due to construction, from October 26th to November 20th. Flagpersons present.
ᓄᓇᓕᐅᑉ ᑎᑎᕋᖅᓯᒪᔭᖓ ᐅᓇ ᐊᑦᑐᐃᓂᖃᖅᑐᖅ ᐃᖏᕐᕋᔾᔪᑎᓄᑦ.
about 0 m from the route
City record updated Oct 26, 2026, 12:48 p.m..
ᐊᖁᑎᒥᒃ ᓴᓇᔪᑦ
BRIAN COBURN between MER-BLEUE, CH DE LA and GERRY LALONDE
Oct 26, 2026, 12:00 a.m. to Nov 20, 2026, 5:00 p.m.
BRIAN COBURN off-peak lane reductions in both directions between MER-BLEUE and GERRY LALONDE due to construction, from October 26th to November 20th. Flagpersons present.
ᓄᓇᓕᐅᑉ ᑎᑎᕋᖅᓯᒪᔭᖓ ᐅᓇ ᐊᑦᑐᐃᓂᖃᖅᑐᖅ ᐃᖏᕐᕋᔾᔪᑎᓄᑦ.
about 0 m from the route
City record updated Oct 26, 2026, 12:52 p.m..
ᐊᖁᑎᒥᒃ ᓴᓇᔪᑦ
St-Joseph between Cousineau and St-Pierre
Oct 26, 2026, 12:00 a.m. to Dec 18, 2026, 5:00 p.m.
St-Joseph off-peak lane reductions in both directions between Cousineau and St-Pierre due to construction, from October 26th to December 18th.
ᓄᓇᓕᐅᑉ ᑎᑎᕋᖅᓯᒪᔭᖓ ᐅᓇ ᐊᑦᑐᐃᓂᖃᖅᑐᖅ ᐃᖏᕐᕋᔾᔪᑎᓄᑦ.
about 0 m from the route
City record updated Oct 29, 2026, 11:56 a.m..

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 →

2 partial-capture days not counted.

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

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

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

Latest cancelled trips

Wed, Oct 14, scheduled 17:02

OC Transpo gives no reason for single trips, so none is shown.

Did not come (no bus seen, no notice), last 7 days: 1 of 80 trips we could check.

Open the dated prediction analysis

ᐃᓱᓕᑦᑎᓂᖅ

What this route needs

Median provider predictions are 3.4 to 6.1 min later than the timetable in 8 hours of the day.

Predictions near the start are about 2.6 min later than the timetable; the difference grows by another 4.6 min along the route.

19:00 has 28% of predictions within five minutes of the timetable, against 61% the rest of the day.

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

Scenario: 3 to 6 min more running time on 120 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, 10 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: 89.3% of final predictions within five minutes of the timetable, 253 predictions, typically 3.4 min late
06:00: 87.6% of final predictions within five minutes of the timetable, 761 predictions, typically 0.7 min late
07:00: 56.6% of final predictions within five minutes of the timetable, 700 predictions, typically 4.4 min late
08:00: 58.1% of final predictions within five minutes of the timetable, 750 predictions, typically 4.3 min late
09:00: not enough data
10:00: not enough data
11:00: not enough data
12:00: not enough data
13:00: not enough data
14:00: 40.3% of final predictions within five minutes of the timetable, 350 predictions, typically 6.1 min late
15:00: 68% of final predictions within five minutes of the timetable, 650 predictions, typically 3 min late
16:00: 63.8% of final predictions within five minutes of the timetable, 710 predictions, typically 3.6 min late
17:00: 43.3% of final predictions within five minutes of the timetable, 750 predictions, typically 6 min late
18:00: 65.1% of final predictions within five minutes of the timetable, 730 predictions, typically 3.5 min late
19:00: 28.3% of final predictions within five minutes of the timetable, 120 predictions, typically 5.6 min late
20:00: not enough data
21:00: not enough data
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	ᖃᖓ	ᐅᑦᑐᕋᖅᑕᐅᓯᒪᔪᖅ	Scenario or next investigation
ProblemPredictions later than timetable	05:00 · 07:00 to 09:00 · 14:00 · 16:00 to 20:00	3.4 min late … 4.6 min late	More running time
ProblemOne hour has a lower prediction match	19:00	28%	Operations, not the timetable
CaveatCoverage gap	All measured hours	99%	More observation, not a service change

Measurements

Predictions later than timetable · 16:00 to 20:00: Measured arrivals 2,310; Hours affected 4; Spread 8.2 min; Median delay 4.6 min; Suggested running time change 4.6 min
Predictions later than timetable · 07:00 to 09:00: Measured arrivals 1,450; Hours affected 2; Spread 6.6 min; Median delay 4.4 min; Suggested running time change 4.4 min
Predictions later than timetable · 14:00: Measured arrivals 350; Hours affected 1; Spread 7.1 min; Median delay 6.1 min; Suggested running time change 6.1 min
Predictions later than timetable · 05:00: Measured arrivals 253; Hours affected 1; Spread 7.3 min; Median delay 3.4 min; Suggested running time change 3.4 min
One hour has a lower prediction match · 19:00: ᐃᑲᕐᕋᖅ 19:00; ᐱᕕᒃᓴᖓᓂ 28.3%; Measured arrivals 120; Shortfall 32.7 pts; Route median on time 61%
Coverage gap · All measured hours: ᑐᕌᒐᖅ 99.5%; Trips with a matching position 98.8%; ᐅᓪᓗᑦ ᐸᓯᑦ ᐊᐅᓚᑕᐅᓂᖏᑦ 5; Trips with a matching position 79; ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ 80

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 were often far from the timetable in this dated sample.

58 in 100 eligible predictions were within 5 minutes of the timetable · 10,324 predictions checked

Prediction sample size: Larger sample

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

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

19–20: 72 in 100 eligible predictions differed from the timetable by more than 5 minutes (120 predictions over 10 days).
14–15: 60 in 100 eligible predictions differed from the timetable by more than 5 minutes (350 predictions over 10 days).
17–18: 57 in 100 eligible predictions differed from the timetable by more than 5 minutes (750 predictions over 10 days).
07–08: 43 in 100 eligible predictions differed from the timetable by more than 5 minutes (700 predictions over 10 days).

No current official notice matches this route.

Prediction differences by stop

FERN CASEY / RENAUD
82 in 100 eligible predictions differed from the timetable by more than 5 minutes (159 predictions over 20 days).
Open this stop
RENAUD / COMPASS
77 in 100 eligible predictions differed from the timetable by more than 5 minutes (159 predictions over 20 days).
Open this stop
FERN CASEY / LOCUST
75 in 100 eligible predictions differed from the timetable by more than 5 minutes (159 predictions over 20 days).
Open this stop
RENAUD / DE LA MÉLODIE
73 in 100 eligible predictions differed from the timetable by more than 5 minutes (159 predictions over 20 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 live cancellation answerOC Transpo’s live trip-update feed did not answer this check. That is a feed gap. It does not mean zero cancellations, and it is not proof of a cancellation. Open the evidence to see the schedule, retained explicit cancellation notices, and every labelled data gap.
Possible no-shows after checking feed gaps?: 1 of 80 checked trips need a closer look1 of 80 trips with enough public-feed evidence had no matching position over 7 days. 0 of 80 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 13.4 min (positive means later; negative means earlier)58 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.

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

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

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

Current published schedule began October 30, 2026

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

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

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

ᓯᕗᓂᐊᓂ

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

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 16
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 66
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 2
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 05:43–19:12

Operator calendar-date records: 0 added · 2 removed

ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᓯᒋᐊᕈᑎᖓ: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

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

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

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 16
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 66
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 2
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 05:43–19:12

Operator calendar-date records: 0 added · 2 removed

ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᓯᒋᐊᕈᑎᖓ: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

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

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

Still collecting: before has 5,759 arrivals over 10 days; after has 1,152 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: 58.3%
Eligible predictions checked: 10,324
Weekdays with data: 18
95th-percentile predicted delay: 13.4 min late

Patterns by hour (11)

Patterns by hour (11)
ᐃᑲᕐᕋᖅ	ᐱᕕᒃᓴᖓᓂ	Median	95th percentile	ᓇᓗᓇᐃᖅᓯᔾᔪᑎᑦ
05:00	89.3%	3.4 min late	10.7 min late	253 · 11 days
06:00	87.6%	0.7 min late	11.2 min late	761 · 11 days
07:00	56.6%	4.4 min late	10.6 min late	700 · 10 days
08:00	58.1%	4.3 min late	11.4 min late	750 · 10 days
09:00	80.0%	1.1 min late	11.9 min late	20 · 10 days
14:00	40.3%	6.1 min late	13.2 min late	350 · 10 days
15:00	68.0%	3 min late	10.7 min late	650 · 10 days
16:00	63.8%	3.6 min late	9.8 min late	710 · 10 days
17:00	43.3%	6 min late	17.6 min late	750 · 10 days
18:00	65.1%	3.5 min late	13.6 min late	730 · 10 days
19:00	28.3%	5.6 min late	11 min late	120 · 10 days

8 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

79 / 80 scheduled trips published at least one position across 5 service days (98.8%).

16:001 / 10 trips without a position90.0%
05:000 / 5 trips without a position100.0%
06:000 / 10 trips without a position100.0%
07:000 / 10 trips without a position100.0%
08:000 / 10 trips without a position100.0%
14: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.

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 · 16 trips in the retained timetable · retained notices; capture coverage unverified

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

05:43– 06:18
Trip 18821020Vehicle position matchedFirst / last feed position: 5:21 a.m. EST / 6:23 a.m. EST; not actual start or end times.
06:11– 06:48
Trip 9220020Vehicle position matchedFirst / last feed position: 5:49 a.m. EST / 6:52 a.m. EST; not actual start or end times.
06:36– 07:18
Trip 31899020Vehicle position matchedFirst / last feed position: 6:28 a.m. EST / 7:28 a.m. EST; not actual start or end times.
07:06– 07:48
Trip 22662020Vehicle position matchedFirst / last feed position: 6:45 a.m. EST / 7:55 a.m. EST; not actual start or end times.
07:36– 08:18
Trip 26970020Vehicle position matchedFirst / last feed position: 7:14 a.m. EST / 8:20 a.m. EST; not actual start or end times.
08:06– 08:48
Trip 16837020Vehicle position matchedFirst / last feed position: 7:58 a.m. EST / 8:47 a.m. EST; not actual start or end times.
08:30– 09:12
Trip 23640020Vehicle position matchedFirst / last feed position: 7:45 a.m. EST / 9:11 a.m. EST; not actual start or end times.
14:17– 14:52
Trip 1174020Vehicle position matchedFirst / last feed position: 1:58 p.m. EST / 3:06 p.m. EST; not actual start or end times.
15:00– 15:37
Trip 24717020Vehicle position matchedFirst / last feed position: 2:55 p.m. EST / 3:46 p.m. EST; not actual start or end times.
15:30– 16:14
Trip 29010020Vehicle position matchedFirst / last feed position: 2:49 p.m. EST / 4:14 p.m. EST; not actual start or end times.
16:00– 16:44
Trip 7163020Vehicle position matchedFirst / last feed position: 4:01 p.m. EST / 4:44 p.m. EST; not actual start or end times.
16:32– 17:16
Trip 18162020Vehicle position matchedFirst / last feed position: 4:21 p.m. EST / 5:23 p.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).