No 13 trips cancelled now · 4 did not run in NovemberCancellations →

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

ᐊᖁᑦ 13: Gatineau ⇄ Tunney's Pasture

11 ᐊᒻᒪ 16 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ

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. Not counted: 31 trips with qualifying later matching vehicle observations. Trips with any notice: 45.

Trips needing investigation

17 of 335 trips with a usable feed window (5.1%) had no matching position.

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

318 with position · 17 to investigate · 0 excluded · 335 scheduled trips

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

Coverage, exclusions and sources

0 of 10 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: 318 / 335 (94.9%). 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, 2: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

53.7%

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

Predictions in the source: 16,758
Weekdays with evidence: 18
Evidence window: Oct 6, 2026 – Nov 3, 2026

The hours we have evidence for

0690% · 940 predictions · 11 days
0762% · 1,377 predictions · 11 days
0845% · 1,986 predictions · 11 days
0972% · 842 predictions · 11 days
1461% · 214 predictions · 11 days
1540% · 1,343 predictions · 11 days
1621% · 1,260 predictions · 11 days
1751% · 1,177 predictions · 11 days
1874% · 1,136 predictions · 11 days
1975% · 308 predictions · 11 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?

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

Values and interpretation

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

4% of pairs (498) 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.)	5,084	10% (530)	3% (163)
Midday (9 a.m. to 3 p.m.)	1,187	8% (97)	2% (20)
Afternoon rush (3 to 6 p.m.)	4,696	9% (445)	6% (266)
Evening (6 to 10 p.m.)	1,903	2% (43)	3% (49)

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

Where this route is slowest

Slowest: LAVAL / LAURIER to LAURIER / ÉLISABETH-BRUYÈRE, 7.3 km/h actual against 5.6 km/h planned.

Where this route is slowest
ᐱᒋᐊᕐᕕᒃ	ᑐᕌᕐᕕᒃ	ᐅᖓᓯᒋᓂᖓ	Planned speed	Actual speed	Trips measured	Slow trips
LAVAL / LAURIER	LAURIER / ÉLISABETH-BRUYÈRE	770 m	5.6 km/h	7.3 km/h	34	3%
LAURIER / ÉLISABETH-BRUYÈRE	MAISONNEUVE / PAPINEAU	520 m	31.3 km/h	8.4 km/h	392	86%
EDDY / LAURIER	LAURIER / ÉLISABETH-BRUYÈRE	1.2 km	8.9 km/h	10.7 km/h	35	0%
LAURIER / EDDY	PIMISI B	1.4 km	12.6 km/h	11.2 km/h	214	18%
MAISONNEUVE / PAPINEAU	LAURIER / MAISONNEUVE	550 m	15.3 km/h	11.7 km/h	212	35%
LAURIER / MAISONNEUVE	PIMISI B	1.6 km	15 km/h	12 km/h	218	27%
PIMISI A	LAVAL / LAURIER	1.5 km	17.8 km/h	13.1 km/h	229	38%
PIMISI A	EDDY / LAURIER	1.1 km	13.5 km/h	14.3 km/h	231	16%

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 →

2 partial-capture days not counted.

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

Not counted: 98 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. (16), 4 p.m. (15), 6 p.m. (12)

Latest cancelled trips

Tue, Nov 3, scheduled 18:18
Tue, Nov 3, scheduled 17:07
Tue, Nov 3, scheduled 16:45
Tue, Nov 3, scheduled 09:16
Mon, Nov 2, scheduled 17:07

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 335 trips we could check.

Open the dated prediction analysis

ᐃᓱᓕᑦᑎᓂᖅ

What this route needs

Median provider predictions are 4.8 to 6 min later than the timetable in 6 hours of the day.

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

16:00 has 21% of predictions within five minutes of the timetable, against 62% the rest of the day.

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

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, 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: not enough data
06:00: 90.1% of final predictions within five minutes of the timetable, 940 predictions, typically 1.5 min late
07:00: 61.8% of final predictions within five minutes of the timetable, 1,377 predictions, typically 3.8 min late
08:00: 44.8% of final predictions within five minutes of the timetable, 1,986 predictions, typically 5.8 min late
09:00: 72% of final predictions within five minutes of the timetable, 842 predictions, typically 2.6 min late
10:00: not enough data
11:00: not enough data
12:00: not enough data
13:00: not enough data
14:00: 61.2% of final predictions within five minutes of the timetable, 214 predictions, typically 3.9 min late
15:00: 40.4% of final predictions within five minutes of the timetable, 1,343 predictions, typically 7.1 min late
16:00: 20.6% of final predictions within five minutes of the timetable, 1,260 predictions, typically 10.5 min late
17:00: 50.6% of final predictions within five minutes of the timetable, 1,177 predictions, typically 5 min late
18:00: 73.5% of final predictions within five minutes of the timetable, 1,136 predictions, typically 2.6 min late
19:00: 75.3% of final predictions within five minutes of the timetable, 308 predictions, typically 0.5 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	07:00 to 09:00 · 14:00 to 18:00	4.8 min late · 6 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	16:00	21%	Operations, not the timetable
CaveatCoverage gap	All measured hours	95%	More observation, not a service change

Measurements

Predictions later than timetable · 14:00 to 18:00: Measured arrivals 3,994; Hours affected 4; Spread 15.3 min; Median delay 6 min; Suggested running time change 6 min
Predictions later than timetable · 07:00 to 09:00: Measured arrivals 3,363; Hours affected 2; Spread 11.2 min; Median delay 4.8 min; Suggested running time change 4.8 min
One hour has a lower prediction match · 16:00: ᐃᑲᕐᕋᖅ 16:00; ᐱᕕᒃᓴᖓᓂ 20.6%; Measured arrivals 1,260; Shortfall 40.9 pts; Route median on time 61.5%
Coverage gap · All measured hours: ᑐᕌᒐᖅ 99.5%; Trips with a matching position 94.9%; ᐅᓪᓗᑦ ᐸᓯᑦ ᐊᐅᓚᑕᐅᓂᖏᑦ 5; Trips with a matching position 318; ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ 335

Open history, reliability and route analysis

Route check

How route 13 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.

54 in 100 eligible predictions were within 5 minutes of the timetable · 16,758 predictions checked

Prediction sample size: Larger sample

Based on 16,758 eligible provider predictions over 18 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.

16–17: 79 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,260 predictions over 11 days).
15–16: 60 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,343 predictions over 11 days).
08–09: 55 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,986 predictions over 11 days).
17–18: 49 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,177 predictions over 11 days).

No current official notice matches this route.

Prediction differences by stop

BOOTH / ZAIDA EDDY
72 in 100 eligible predictions differed from the timetable by more than 5 minutes (548 predictions over 20 days).
Open this stop
EDDY / LAURIER
71 in 100 eligible predictions differed from the timetable by more than 5 minutes (546 predictions over 20 days).
Open this stop
BOOTH / WELLINGTON
67 in 100 eligible predictions differed from the timetable by more than 5 minutes (547 predictions over 20 days).
Open this stop
BOOTH / VIMY
67 in 100 eligible predictions differed from the timetable by more than 5 minutes (549 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?: 0 of 10Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 17 of 335 checked trips need a closer look17 of 335 trips with enough public-feed evidence had no matching position over 7 days. 0 of 335 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 19.9 min (positive means later; negative means earlier)54 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.9 min average predicted wait0.7 min beyond the scheduled wait, based on 2,408 eligible predictions at 12 high-frequency stops over 15 days.

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

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

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

Current published schedule began October 30, 2026

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

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

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

ᓯᕗᓂᐊᓂ

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

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 67
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 33
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 3
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 06:14–19:23

Operator calendar-date records: 0 added · 2 removed

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

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

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

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 67
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 33
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 3
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 06:14–19:23

Operator calendar-date records: 0 added · 2 removed

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

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

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

Still collecting: before has 9,214 arrivals over 10 days; after has 4,036 arrivals over 4 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: 53.7%
Eligible predictions checked: 16,758
Weekdays with data: 18
95th-percentile predicted delay: 19.9 min late

Patterns by hour (10)

Patterns by hour (10)
ᐃᑲᕐᕋᖅ	ᐱᕕᒃᓴᖓᓂ	Median	95th percentile	ᓇᓗᓇᐃᖅᓯᔾᔪᑎᑦ
06:00	90.1%	1.5 min late	5.7 min late	940 · 11 days
07:00	61.8%	3.8 min late	13.3 min late	1,377 · 11 days
08:00	44.8%	5.8 min late	18.7 min late	1,986 · 11 days
09:00	72.0%	2.6 min late	16.4 min late	842 · 11 days
14:00	61.2%	3.9 min late	12 min late	214 · 11 days
15:00	40.4%	7.1 min late	20.9 min late	1,343 · 11 days
16:00	20.6%	10.5 min late	30 min late	1,260 · 11 days
17:00	50.6%	5 min late	21.7 min late	1,177 · 11 days
18:00	73.5%	2.6 min late	13.3 min late	1,136 · 11 days
19:00	75.3%	0.5 min late	10.8 min late	308 · 11 days

6 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

318 / 335 scheduled trips published at least one position across 5 service days (94.9%).

18:005 / 35 trips without a position85.7%
16:004 / 40 trips without a position90.0%
17:004 / 40 trips without a position90.0%
06:002 / 35 trips without a position94.3%
09:001 / 20 trips without a position95.0%
07:001 / 45 trips without a position97.8%

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

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

06:14– 06:29
Trip 16610040Vehicle position matchedFirst / last feed position: 6:01 a.m. EST / 6:29 a.m. EST; not actual start or end times.
06:18– 06:37
Trip 35994040Vehicle position matchedFirst / last feed position: 5:50 a.m. EST / 6:37 a.m. EST; not actual start or end times.
06:27– 06:42
Trip 4751040Vehicle position matchedFirst / last feed position: 6:25 a.m. EST / 6:41 a.m. EST; not actual start or end times.
06:31– 06:53
Trip 2481040Vehicle position matchedFirst / last feed position: 6:30 a.m. EST / 6:56 a.m. EST; not actual start or end times.
06:39– 06:54
Trip 17637040Vehicle position matchedFirst / last feed position: 6:38 a.m. EST / 7:48 a.m. EST; not actual start or end times.
06:46– 07:08
Trip 24582040Vehicle position matchedFirst / last feed position: 6:42 a.m. EST / 7:08 a.m. EST; not actual start or end times.
06:56– 07:11
Trip 22351040Vehicle position matchedFirst / last feed position: 6:57 a.m. EST / 7:14 a.m. EST; not actual start or end times.
07:01– 07:23
Trip 5207040Vehicle position matchedFirst / last feed position: 6:34 a.m. EST / 7:28 a.m. EST; not actual start or end times.
07:11– 07:27
Trip 6822040Vehicle position matchedFirst / last feed position: 7:10 a.m. EST / 8:37 a.m. EST; not actual start or end times.
07:16– 07:38
Trip 3506040Vehicle position matchedFirst / last feed position: 7:16 a.m. EST / 7:40 a.m. EST; not actual start or end times.
07:26– 07:42
Trip 20662040Vehicle position matchedFirst / last feed position: 6:41 a.m. EST / 7:51 a.m. EST; not actual start or end times.
07:31– 07:45
Trip 16218040Vehicle position matchedFirst / last feed position: 6:49 a.m. EST / 7:57 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).