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

Previous measure: 77.3% of arrivals were within five minutes of the timetable (6,590 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 93: Masson

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

2 of 49 trips with a usable feed window (4.1%) had no matching position.

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

47 with position · 2 to investigate · 11 excluded · 60 scheduled trips

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

Coverage, exclusions and sources

0 of 4 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.

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

Published position coverage: 47 / 60 (78.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, 10:39 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

77.3%

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

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

The hours we have evidence for

05100% · 182 predictions · 8 days
0696% · 746 predictions · 8 days
0791% · 602 predictions · 7 days
0890% · 221 predictions · 7 days
1595% · 459 predictions · 9 days
1662% · 664 predictions · 10 days
1780% · 546 predictions · 9 days
1859% · 217 predictions · 7 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?

8 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: 38 of 3,817 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

3% of pairs (121) 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
Morning rush (6 to 9 a.m.)	1,606	0% (1)	0% (0)
Afternoon rush (3 to 6 p.m.)	1,917	2% (37)	5% (91)
Evening (6 to 10 p.m.)	294	0% (0)	10% (30)

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, 8.6 km/h actual against 10.8 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	10.8 km/h	8.6 km/h	58	17%
PLACE d'ACCUEIL est	Station MONTCALM bretelle dir nord #2	1.3 km	9.8 km/h	10.4 km/h	73	0%
PLACE d'ACCUEIL ouest	STATION LYON	1.6 km	16.6 km/h	13 km/h	47	26%
de l'ARÉNA/LOMBARD	PARC-O-BUS GEORGES/ROUTE 148	2 km	23.8 km/h	14.5 km/h	47	49%
PARC-O-BUS GEORGES/ROUTE 148	de l'ARÉNA/LOMBARD arrivée	2.1 km	20.5 km/h	17.3 km/h	71	17%
Station CASINO #2	Station LAC LEAMY #2	800 m	17.5 km/h	17.8 km/h	77	8%
du PROGRÈS/de GENÈVE	de NEUVILLE/de CHAVILLE	2.8 km	19.3 km/h	18.7 km/h	46	0%
Station MONTCALM bretelle dir sud #1	PLACE d'ACCUEIL ouest	2 km	17.3 km/h	19.3 km/h	53	0%

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.

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

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

Hours with the most cancellations: 6 a.m. (1)

Latest cancelled trips

Wed, Nov 4, scheduled 06:25

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: 1 of 49 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.

When this route is usually busy	Anokii-giizhigadoon	Samdi	Anamiegìjigad
Before 6 am	Usually seats0% of 30 trips	Not enough readings	Not enough readings
6 to 9 am	Usually busy69.9% of 143 trips	Not enough readings	Not enough readings
9 am to 3 pm	Usually seats7.7% of 13 trips	Not enough readings	Not enough readings
3 to 6 pm	Usually seats23.5% of 187 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 3.2 min later than the timetable in 2 hours of the day.

Wide prediction spread 17:00: the 95th percentile is 29.6 min later than the median.

18:00 has 59% of predictions within five minutes of the timetable, against 91% the rest of the day.

Scenario: 3 min more running time on 8 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, 8 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: 99.5% of final predictions within five minutes of the timetable, 182 predictions, typically 1.7 min late
06:00: 95.6% of final predictions within five minutes of the timetable, 746 predictions, typically 0.8 min late
07:00: 90.9% of final predictions within five minutes of the timetable, 602 predictions, typically 2.3 min late
08:00: 90% of final predictions within five minutes of the timetable, 221 predictions, typically 0.1 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: not enough data
15:00: 94.8% of final predictions within five minutes of the timetable, 459 predictions, typically 0.1 min late
16:00: 62.2% of final predictions within five minutes of the timetable, 664 predictions, typically 3.2 min late
17:00: 79.5% of final predictions within five minutes of the timetable, 546 predictions, typically 0.8 min late. Provider predictions have a wide spread.
18:00: 59.4% of final predictions within five minutes of the timetable, 217 predictions, typically 3.2 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
prediction spread of 20 min or more between the 95th percentile and median

Findings
What	Aaniin apii	Tibàdjigade	Scenario or next investigation
ProblemPredictions later than timetable	16:00 · 18:00	3.2 min late	More running time
ProblemWide prediction spread	17:00	29.6 min swing	Operations, not the timetable
ProblemOne hour has a lower prediction match	18:00	59%	Operations, not the timetable

Measurements

Predictions later than timetable · 16:00: Measured arrivals 664; Hours affected 1; Spread 17.5 min; Median delay 3.2 min; Suggested running time change 3.2 min
Predictions later than timetable · 18:00: Measured arrivals 217; Hours affected 1; Spread 11.5 min; Median delay 3.2 min; Suggested running time change 3.2 min
Wide prediction spread · 17:00: Measured arrivals 546; Hours affected 1; Spread 29.6 min; Median delay 0.8 min; Suggested running time change 0.8 min
One hour has a lower prediction match · 18:00: Dibaa'igan 18:00; Weweni apii 59.4%; Measured arrivals 217; Shortfall 31.1 pts; Route median on time 90.5%

Open history, reliability and route analysis

Route check

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

77 in 100 eligible predictions were within 5 minutes of the timetable · 6,590 predictions checked

Aaniin minik gikendaasowinan: Larger sample

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

Updated Nov 5, 2026, 10: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.

18–19: 41 in 100 eligible predictions differed from the timetable by more than 5 minutes (217 predictions over 7 days).
16–17: 38 in 100 eligible predictions differed from the timetable by more than 5 minutes (664 predictions over 10 days).

No current official notice matches this route.

Prediction differences by stop

STATION LYON
55 in 100 eligible predictions differed from the timetable by more than 5 minutes (65 predictions over 15 days).
Open this stop
de l'ARÉNA/LOMBARD arrivée
52 in 100 eligible predictions differed from the timetable by more than 5 minutes (96 predictions over 18 days).
Open this stop
ROUTE 148/LOMBARD
49 in 100 eligible predictions differed from the timetable by more than 5 minutes (99 predictions over 18 days).
Open this stop
ROUTE 148/GUY-DUBUC
48 in 100 eligible predictions differed from the timetable by more than 5 minutes (98 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?: 0 of 4Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 2 of 49 checked trips need a closer look2 of 49 trips with enough public-feed evidence had no matching position over 7 days. 11 of 60 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 13.7 min (positive means later; negative means earlier)77 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: 12
Nibawin kà-ozhibiigàdegin: 96
Miikanan gaa-ozhibii'igaadegin: 2
Àpi odàbànag pimosewaad, ozhibii'igaade: 05:45–18:25

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: 12
Nibawin kà-ozhibiigàdegin: 96
Miikanan gaa-ozhibii'igaadegin: 2
Àpi odàbànag pimosewaad, ozhibii'igaade: 05:45–18:25

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 3,610 arrivals over 10 days; after has 454 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: 77.3%
Eligible predictions checked: 6,590
Weekdays with data: 17
95th-percentile predicted delay: 13.7 min late

Patterns by hour (9)

Patterns by hour (9)
Dibaa'igan	Weweni apii	Median	95th percentile	Gikendaasowinan
05:00	99.5%	1.7 min late	3.7 min late	182 · 8 days
06:00	95.6%	0.8 min late	4.6 min late	746 · 8 days
07:00	90.9%	2.3 min late	5.6 min late	602 · 7 days
08:00	90.0%	0.1 min late	6.9 min late	221 · 7 days
14:00	100.0%	0 min late	2.2 min late	20 · 7 days
15:00	94.8%	0.1 min late	3.9 min late	459 · 9 days
16:00	62.2%	3.2 min late	20.7 min late	664 · 10 days
17:00	79.5%	0.8 min late	30.4 min late	546 · 9 days
18:00	59.4%	3.2 min late	14.7 min late	217 · 7 days

2 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

47 / 60 scheduled trips published at least one position across 5 service days (78.3%).

06:006 / 15 trips without a position60.0%
07:002 / 5 trips without a position60.0%
17:002 / 5 trips without a position60.0%
05:001 / 5 trips without a position80.0%
14:001 / 5 trips without a position80.0%
16:001 / 10 trips without a position90.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 · 12 trips in the retained timetable · retained notices; capture coverage unverified

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

05:45– 06:56
Trip sto:63295445Vehicle position matchedFirst / last feed position: 5:48 a.m. EST / 6:59 a.m. EST; not actual start or end times.
06:05– 07:16
Trip sto:63294631Vehicle position matchedFirst / last feed position: 6:02 a.m. EST / 7:22 a.m. EST; not actual start or end times.
06:25– 07:38
Trip sto:63290299Explicit notice: CANCELEDNo matching position; investigate, not a confirmed cancellation
06:55– 08:15
Trip sto:63295713Vehicle position matchedFirst / last feed position: 6:51 a.m. EST / 8:18 a.m. EST; not actual start or end times.
07:25– 08:45
Trip sto:63294677Vehicle position matchedFirst / last feed position: 7:24 a.m. EST / 8:45 a.m. EST; not actual start or end times.
14:50– 15:56
Trip sto:63295856Insufficient coverage or identity; outcome unknown
15:10– 16:16
Trip sto:63296180Vehicle position matchedFirst / last feed position: 4:17 p.m. EST / 4:19 p.m. EST; not actual start or end times.
15:30– 16:37
Trip sto:63295733Vehicle position matchedFirst / last feed position: 4:17 p.m. EST / 4:37 p.m. EST; not actual start or end times.
15:50– 16:57
Trip sto:63295877Vehicle position matchedFirst / last feed position: 4:17 p.m. EST / 4:58 p.m. EST; not actual start or end times.
16:20– 17:27
Trip sto:63295870Vehicle position matchedFirst / last feed position: 4:21 p.m. EST / 5:23 p.m. EST; not actual start or end times.
16:50– 17:55
Trip sto:63290292Vehicle position matchedFirst / last feed position: 4:50 p.m. EST / 5:56 p.m. EST; not actual start or end times.
17:20– 18:25
Trip sto:63295384Vehicle position matchedFirst / last feed position: 5:43 p.m. EST / 6:39 p.m. EST; not actual start or end times.

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