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

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

STO miikana 95: Buckingham

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: 1 trips with qualifying later matching vehicle observations. Trips with any notice: 3.

Trips needing investigation

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

75 with position · 1 to investigate · 14 excluded · 90 scheduled trips

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

Coverage, exclusions and sources

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

Published position coverage: 75 / 90 (83.3%). 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, 5:48 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

73.6%

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

Predictions in the source: 13,182
Weekdays with evidence: 17
Evidence window: Oct 7, 2026 – Nov 4, 2026

The hours we have evidence for

0578% · 489 predictions · 8 days
0684% · 1,571 predictions · 8 days
0781% · 1,049 predictions · 7 days
0893% · 284 predictions · 8 days
1490% · 73 predictions · 8 days
1558% · 1,059 predictions · 9 days
1659% · 1,282 predictions · 10 days
1750% · 1,062 predictions · 9 days
1861% · 402 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?

9 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: 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

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

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

Buses arriving bunched
Giizhigad diba'iganan	Pairs checked	Bunched	Long gap
Early morning (4 to 6 a.m.)	199	0% (0)	0% (0)
Morning rush (6 to 9 a.m.)	4,333	1% (58)	0% (8)
Midday (9 a.m. to 3 p.m.)	25	Not enough buses
Afternoon rush (3 to 6 p.m.)	4,255	1% (48)	1% (61)
Evening (6 to 10 p.m.)	543	0% (0)	0% (0)

Aaniin ezhi-dibaabandamang →How we got this numberBunching and slow spots on every route →

Where this route is slowest

Slowest: BANK/QUEEN to PLACE d'ACCUEIL est, 7.8 km/h actual against 9.6 km/h planned.

Where this route is slowest
Wendjibàyan	Ijayan	Aaniin epiichi-waasaag	Planned speed	Actual speed	Trips measured	Slow trips
BANK/QUEEN	PLACE d'ACCUEIL est	1.4 km	9.6 km/h	7.8 km/h	101	25%
PLACE d'ACCUEIL est	Station MONTCALM bretelle dir nord #2	1.3 km	10.9 km/h	10.2 km/h	109	3%
PLACE d'ACCUEIL ouest	STATION LYON	1.6 km	16.6 km/h	13.5 km/h	77	30%
Station CASINO #2	Station LAC LEAMY #2	800 m	17.7 km/h	18.2 km/h	117	5%
Station MONTCALM bretelle dir sud #1	PLACE d'ACCUEIL ouest	2 km	16.8 km/h	18.9 km/h	79	0%
ENCAN de MASSON	Av. de BUCKINGHAM/JOSEPH	5.6 km	19.5 km/h	19.1 km/h	98	1%
LÉPINE/FINDLAY	Av. de BUCKINGHAM/MACLAREN	5.2 km	23.9 km/h	19.4 km/h	53	26%
Station LAC LEAMY #1	Station CASINO #1	550 m	22 km/h	20.4 km/h	83	19%

Bejiw madjàwin: 1.5 apì nawach kinwesh.

Aaniin ezhi-dibaabandamang →

Cancellations on this route

What these words mean →

6 partial-capture days not counted.

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

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

Latest cancelled trips

Tue, Nov 3, scheduled 16:18
Fri, Oct 30, scheduled 15:30

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	Anokii-giizhigadoon	Samdi	Anamiegìjigad
Before 6 am	Usually seats0% of 92 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats46.8% of 205 trips	Not enough readings	Not enough readings
9 am to 3 pm	Usually seats37.8% of 74 trips	Not enough readings	Not enough readings
3 to 6 pm	Usually seats37.7% of 257 trips	Not enough readings	Not enough readings
6 to 10 pm	Usually seats0% of 43 trips	Not enough readings	Not enough readings
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

Ishkwaa-inendamowin

What this route needs

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

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

17:00 has 50% of predictions within five minutes of the timetable, against 78% 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, 9 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: 78.1% of final predictions within five minutes of the timetable, 489 predictions, typically 2.1 min late
06:00: 84% of final predictions within five minutes of the timetable, 1,571 predictions, typically 1 min late
07:00: 81.1% of final predictions within five minutes of the timetable, 1,049 predictions, typically 2.7 min late
08:00: 93% of final predictions within five minutes of the timetable, 284 predictions, typically 2 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: 90.4% of final predictions within five minutes of the timetable, 73 predictions, typically 1.3 min late
15:00: 57.8% of final predictions within five minutes of the timetable, 1,059 predictions, typically 4.3 min late
16:00: 59.3% of final predictions within five minutes of the timetable, 1,282 predictions, typically 3.7 min late
17:00: 49.6% of final predictions within five minutes of the timetable, 1,062 predictions, typically 4.4 min late
18:00: 61.2% of final predictions within five minutes of the timetable, 402 predictions, typically 3.9 min late
19:00: not enough data
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	Aaniin apii	Tibàdjigade	Scenario or next investigation
ProblemPredictions later than timetable	15:00 to 19:00	4.1 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	17:00	50%	Operations, not the timetable

Measurements

Predictions later than timetable · 15:00 to 19:00: Measured arrivals 3,805; Hours affected 4; Spread 8 min; Median delay 4.1 min; Suggested running time change 4.1 min
One hour has a lower prediction match · 17:00: Dibaa'igan 17:00; Weweni apii 49.6%; Measured arrivals 1,062; Shortfall 28.5 pts; Route median on time 78.1%

Open history, reliability and route analysis

Route check

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

74 in 100 eligible predictions were within 5 minutes of the timetable · 13,182 predictions checked

Aaniin minik gikendaasowinan: Larger sample

Based on 13,182 eligible provider predictions over 17 measured days, from Oct 7, 2026 to Nov 4, 2026.

Updated Nov 5, 2026, 5: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: 50 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,062 predictions over 9 days).
15–16: 42 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,059 predictions over 9 days).
16–17: 41 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,282 predictions over 10 days).
18–19: 39 in 100 eligible predictions differed from the timetable by more than 5 minutes (402 predictions over 8 days).

No current official notice matches this route.

Prediction differences by stop

STATION LYON
49 in 100 eligible predictions differed from the timetable by more than 5 minutes (104 predictions over 16 days).
Open this stop
BÉLANGER/ROSS
48 in 100 eligible predictions differed from the timetable by more than 5 minutes (149 predictions over 18 days).
Open this stop
BANK/QUEEN
47 in 100 eligible predictions differed from the timetable by more than 5 minutes (106 predictions over 16 days).
Open this stop
MACLAREN EST/JAMES
47 in 100 eligible predictions differed from the timetable by more than 5 minutes (149 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

Pàkinan pejig dibaigan ji-wàbandaman endaso-gìzhigad, odàbànag, àpì kàwin gegò gì-ayàsinog, odàbàn ishinikàzowinan, gaye kakina àjindàsowinan.

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?: 1 of 76 checked trips need a closer look1 of 76 trips with enough public-feed evidence had no matching position over 7 days. 14 of 90 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
Àniin gà-ikidong, gaye àniin dibaigan mazina'igan ikido?: At the 95th percentile, the predicted difference was 11.1 min (positive means later; negative means earlier)74 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.

Ganawaabandan aanjichigewin

Apii-mazina'igan: jibwaa miinawaa ishkwaa

Ow ozhibiigan ijinàgwad noongom, kaye ijinàgwad kayàsh. Ow ozhibiigan ikido kà-inendjigàdeg. Kawin ondji-kikendàgwasinon kidji-ki-majàd odàbàn.

Current published schedule began November 3, 2026

Giizhigad gaa-onaabanjigaadeg endaso-mazina'iganing

Ningii-ganawaabandaamin nitam Ishkwaa-anami'e-giizhigad ishkwaa oshki-mazina'igan gii-maajitaamagak, miinawaa Ishkwaa-anami'e-giizhigad bezhig anami'e-giizhigad jibwaa. Gakina agindaasowinan onjimagadoon GTFS mazina'iganan gaa-ganawendamang, ezhinikaadegin dabazhish.

Bezhig gemaa nawaj giizhigad gaa-onaabanjigeyan, bakaan izhi-bimiwizhiwewag odaabaanag. Ganabaj anami'e-giizhigad gemaa wiikonge-giizhigad. Gaawiin iwe apane izhiwebasinoon.

Jibwà

Giizhigad gaa-andawaabanjigaadeg: November 2, 2026

Maajaawinan ozhibii'igaadegin: 18
Nibawin kà-ozhibiigàdegin: 126
Miikanan gaa-ozhibii'igaadegin: 2
Àpi odàbànag pimosewaad, ozhibii'igaade: 05:30–18:30

Operator calendar-date records: 1 added · 0 removed

Ozhibii'igan ezhinaagwak: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

Oshki mazina'igan

Giizhigad gaa-andawaabanjigaadeg: November 9, 2026

Maajaawinan ozhibii'igaadegin: 18
Nibawin kà-ozhibiigàdegin: 126
Miikanan gaa-ozhibii'igaadegin: 2
Àpi odàbànag pimosewaad, ozhibii'igaade: 05:30–18:30

Operator calendar-date records: 1 added · 0 removed

Ozhibii'igan ezhinaagwak: 64b436d79ab51a76 · 623ad8b0-ad29-4d70-b8e6-e594a396233e

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 7,065 arrivals over 10 days; after has 1,047 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.

Waabandan aaniin ezhi-inaabadak gaye aaniin ezhi-agindaasong

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

Within 5 minutes of schedule: 73.6%
Eligible predictions checked: 13,182
Weekdays with data: 17
95th-percentile predicted delay: 11.1 min late

Patterns by hour (9)

Patterns by hour (9)
Dibaa'igan	Weweni apii	Median	95th percentile	Gikendaasowinan
05:00	78.1%	2.1 min late	11.6 min late	489 · 8 days
06:00	84.0%	1 min late	7.4 min late	1,571 · 8 days
07:00	81.1%	2.7 min late	10.8 min late	1,049 · 7 days
08:00	93.0%	2 min late	5.2 min late	284 · 8 days
14:00	90.4%	1.3 min late	6.1 min late	73 · 8 days
15:00	57.8%	4.3 min late	10.6 min late	1,059 · 9 days
16:00	59.3%	3.7 min late	10.9 min late	1,282 · 10 days
17:00	49.6%	4.4 min late	13.2 min late	1,062 · 9 days
18:00	61.2%	3.9 min late	13.8 min late	402 · 8 days

4 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

75 / 90 scheduled trips published at least one position across 5 service days (83.3%).

07:002 / 5 trips without a position60.0%
06:007 / 20 trips without a position65.0%
05:003 / 15 trips without a position80.0%
16:002 / 15 trips without a position86.7%
15:001 / 20 trips without a position95.0%
14:000 / 10 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 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

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

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

05:30– 06:47
Trip sto:63295158Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 7:00 a.m. EST; not actual start or end times.
05:45– 07:02
Trip sto:63290294Vehicle position matchedFirst / last feed position: 5:48 a.m. EST / 7:09 a.m. EST; not actual start or end times.
05:58– 07:15
Trip sto:63294835Vehicle position matchedFirst / last feed position: 5:57 a.m. EST / 7:25 a.m. EST; not actual start or end times.
06:15– 07:37
Trip sto:63295909Vehicle position matchedFirst / last feed position: 6:17 a.m. EST / 7:52 a.m. EST; not actual start or end times.
06:30– 07:57
Trip sto:63295120Vehicle position matchedFirst / last feed position: 6:31 a.m. EST / 8:08 a.m. EST; not actual start or end times.
06:45– 08:12
Trip sto:63295267Vehicle position matchedFirst / last feed position: 6:46 a.m. EST / 8:17 a.m. EST; not actual start or end times.
06:59– 08:26
Trip sto:63295866Vehicle position matchedFirst / last feed position: 7:01 a.m. EST / 8:24 a.m. EST; not actual start or end times.
07:15– 08:42
Trip sto:63294750Vehicle position matchedFirst / last feed position: 7:12 a.m. EST / 8:46 a.m. EST; not actual start or end times.
14:30– 15:49
Trip sto:63295773Vehicle position matchedFirst / last feed position: 2:37 p.m. EST / 2:46 p.m. EST; not actual start or end times.
14:45– 16:06
Trip sto:63295875Vehicle position matchedFirst / last feed position: 2:46 p.m. EST / 2:46 p.m. EST; not actual start or end times.
15:00– 16:22
Trip sto:63295767Vehicle position matchedFirst / last feed position: 4:17 p.m. EST / 4:17 p.m. EST; not actual start or end times.
15:15– 16:40
Trip sto:63294655Vehicle position matchedFirst / last feed position: 4:17 p.m. EST / 4:41 p.m. EST; not actual start or end times.

· Open all evidence for this day

Draft

This translation is a draft.

Help improve it

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

Read this page in English

This page is a machine draft in Algonquin (Anishinaabemowin), the language of the Anishinabe Algonquin Nation. 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 algonquin (anishinaabemowin), la langue de la Nation algonquine anishinabe. 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).