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

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

STO route 100: Rapibus 100

Toward Lorrain2 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)

des ALLUMETTIÈRES/SAINT-RÉDEMPTEUR0 min sched.
des ALLUMETTIÈRES/LAVAL2 min sched.
MAISONNEUVE/des ALLUMETTIÈRES3 min sched.
MAISONNEUVE/PAPINEAU4 min sched.
PLACE d'ACCUEIL ouest5 min sched.
LAVAL/LAURIER7 min sched.
LAURIER/EDDY9 min sched.
EDDY/WELLINGTON10 min sched.
MONTCALM/WRIGHT0 min sched.
MONTCALM/GAGNON1 min sched.
Station MONTCALM #33 min sched.
Station LES GALERIES #26 min sched.
Station CASINO #27 min sched.
Station LAC LEAMY #21 min sched.
Station de la GAPPE #36 min sched.
Station PROMENADES #29 min sched.
Station de la CITÉ #313 min sched.
Station GOUIN #216 min sched.
Station LABROSSE #0418 min sched.
Station Lac Beauchamp #221 min sched.
STATION LORRAIN arrêt d'arrivée23 min sched.

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 28, 2026 – Nov 3, 2026

Scheduled trips with cancellation notices

—

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

Trips needing investigation

0 of 121 trips with a usable feed window (0%) had no matching position.

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

121 with position · 0 to investigate · 34 excluded · 155 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 121 / 155 (78.1%). 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 4, 2026, 2:38 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

86.1%

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

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

The hours we have evidence for

0695% · 435 predictions · 7 days
0795% · 517 predictions · 6 days
0897% · 493 predictions · 7 days
1595% · 708 predictions · 9 days
1673% · 802 predictions · 10 days
1782% · 633 predictions · 9 days
1875% · 32 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 4, 2026

6 partial-capture days not counted.

What about time of day?

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

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

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

Buses arriving bunched
Tó: nikahwistá:ke	Pairs checked	Bunched	Long gap
Morning rush (6 to 9 a.m.)	2,660	1% (30)	2% (49)
Midday (9 a.m. to 3 p.m.)	10	Not enough buses
Afternoon rush (3 to 6 p.m.)	3,535	8% (290)	4% (148)
Evening (6 to 10 p.m.)	50	0% (0)	0% (0)

Tsi ní:ioht →How we got this numberBunching and slow spots on every route →

Where this route is slowest

Slowest: PLACE d'ACCUEIL ouest to LAURIER/EDDY, 8 km/h actual against 7.1 km/h planned.

Where this route is slowest
Tsi nón:we	Tsi nón:we	Tsi niió:re (distance)	Planned speed	Actual speed	Trips measured	Slow trips
PLACE d'ACCUEIL ouest	LAURIER/EDDY	470 m	7.1 km/h	8 km/h	173	2%
des ALLUMETTIÈRES/SAINT-RÉDEMPTEUR	MAISONNEUVE/des ALLUMETTIÈRES	650 m	13.1 km/h	8.4 km/h	134	28%
PLACE d'ACCUEIL ouest	EDDY/WELLINGTON	600 m	11.2 km/h	11.3 km/h	126	5%
LAURIER/EDDY	Station MONTCALM #3	1.1 km	13.8 km/h	12.3 km/h	188	7%
MAISONNEUVE/PAPINEAU	PLACE d'ACCUEIL ouest	340 m	20.6 km/h	16.2 km/h	171	26%
Station PROMENADES #2	Station de la CITÉ #3	1.2 km	18 km/h	17.6 km/h	199	1%
MAISONNEUVE/PAPINEAU	PLACE d'ACCUEIL ouest	340 m	20.6 km/h	17.9 km/h	141	7%
Station MONTCALM bretelle dir sud #1	MAISONNEUVE/PAPINEAU	1.6 km	19.4 km/h	18.5 km/h	141	2%

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

Tsi ní:ioht →

Cancellations on this route

What these words mean →

6 partial-capture days not counted.

1 scheduled trips with counted cancellation notices from Wed, Oct 7 to Tue, Nov 3.

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: 7 a.m. (1)

Latest cancelled trips

Wed, Oct 21, scheduled 07:55

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	Wísk niwenhniserá:ke	Entákta	Awentatokentì:ke
Before 6 am	Usually seats0% of 21 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats25.2% of 460 trips	Not enough readings	Not enough readings
9 am to 3 pm	Usually seats0% of 18 trips	Not enough readings	Not enough readings
3 to 6 pm	Usually seats39.7% of 509 trips	Not enough readings	Not enough readings
6 to 10 pm	Usually seats0% of 37 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

Ka' nikarihò:ten

What this route needs

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

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

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 7 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: 94.5% of final predictions within five minutes of the timetable, 435 predictions, typically 0.4 min late
07:00: 94.8% of final predictions within five minutes of the timetable, 517 predictions, typically 0.3 min late
08:00: 96.6% of final predictions within five minutes of the timetable, 493 predictions, typically 0.7 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, 708 predictions, typically 0.6 min late
16:00: 72.6% of final predictions within five minutes of the timetable, 802 predictions, typically 2.4 min late
17:00: 82.3% of final predictions within five minutes of the timetable, 633 predictions, typically 2.3 min late
18:00: 75% of final predictions within five minutes of the timetable, 32 predictions, typically 0.4 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	Ó:nen	Tewaterièn:tare	Scenario or next investigation
ProblemPredicted spacing varies	All measured hours	1.3 min extra wait	Manage the headway
ProblemOne hour has a lower prediction match	16:00	73%	Operations, not the timetable

Measurements

Predicted spacing varies · All measured hours: Tsi nón:we tkatkétskwas 41; Extra wait share 26.2%; Matched arrivals 2,439; Ó:ia tsi nikarì:wes 1.3 min; Scheduled wait 5 min
One hour has a lower prediction match · 16:00: Hour 16:00; Ioiánere tsi nikarì:wes 72.6%; Measured arrivals 802; Shortfall 21.9 pts; Route median on time 94.5%

Open history, reliability and route analysis

Route check

How route 100 has been running

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

Bottom line

Provider predictions were usually close to schedule in this dated sample.

86 in 100 eligible predictions were within 5 minutes of the timetable · 7,632 predictions checked

Prediction sample size: Larger sample

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

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

No repeated prediction-difference period has cleared the evidence threshold yet.

No current official notice matches this route.

Prediction differences by stop

STATION LORRAIN arrêt d'arrivée
30 in 100 eligible predictions differed from the timetable by more than 5 minutes (216 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?: 0 of 12Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 0 of 121 checked trips need a closer look0 of 121 trips with enough public-feed evidence had no matching position over 7 days. 34 of 155 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 7.8 min (positive means later; negative means earlier)86 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.3 min average predicted wait1.3 min beyond the scheduled wait, based on 2,439 eligible predictions at 41 high-frequency stops over 13 days.

Schedule change check

Published schedule: before and after

This compares the current retained official schedule with the prior retained version. Schedule changes are facts about what was planned. They do not prove that a trip ran.

Current published schedule began November 2, 2026

Selected service day from each published schedule

We check ne first Monday after ne á:se schedule began, tánon ne Monday one week earlier. Akwé:kon figures, official GTFS versions named below.

At least one selected date uses added or removed calendar-date service. Treat this as holiday or special-service context, not ordinary weekday growth.

Ohén:ton

Wenhniserá:te wahatkáhtho: October 26, 2026

Schedule trips: 0
Distinct scheduled stops: 0
Distinct published paths: 0
Kahiatónhsera: tsi niió:re ne kà:sere: —–—

Kahiatónhsera: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

New schedule

Wenhniserá:te wahatkáhtho: November 2, 2026

Schedule trips: 31
Distinct scheduled stops: 41
Distinct published paths: 2
Kahiatónhsera: tsi niió:re ne kà:sere: 06:01–18:08

Operator calendar-date records: 1 added · 0 removed

Kahiatónhsera: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

Did service improve after the change?

Enkwatkáhtho' ne arrivals 14 wenhniserá:tens tsi niió:re aorí:wa ne change tánon' ohnà:ken. Ne tsi enkwatkáhtho' entewahró:ri' tsi nikarì:wes ne 7 wenhniserá:tens tánon' 200 arrivals iá:ken'.

Still collecting: before has 4,147 arrivals over 10 days; after has 484 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: Rapibus rapid transit

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: 86.1%
Eligible predictions checked: 7,632
Weekdays with data: 17
95th-percentile predicted delay: 7.8 min late

Patterns by hour (7)

Patterns by hour (7)
Hour	Ioiánere tsi nikarì:wes	Median	95th percentile	Tsi tó:kenske
06:00	94.5%	0.4 min late	3.7 min late	435 · 7 days
07:00	94.8%	0.3 min late	6 min late	517 · 6 days
08:00	96.6%	0.7 min late	4.6 min late	493 · 7 days
15:00	94.8%	0.6 min late	4.6 min late	708 · 9 days
16:00	72.6%	2.4 min late	12.8 min late	802 · 10 days
17:00	82.3%	2.3 min late	7.6 min late	633 · 9 days
18:00	75.0%	0.4 min late	10.3 min late	32 · 8 days

No repeated pattern below 70% is yet established across at least three service days.

Scheduled bus, but not observed in realtime

121 / 155 scheduled trips published at least one position across 5 service days (78.1%).

07:0012 / 30 trips without a position60.0%
06:0010 / 30 trips without a position66.7%
08:004 / 15 trips without a position73.3%
15:005 / 35 trips without a position85.7%
17:002 / 15 trips without a position86.7%
16:001 / 30 trips without a position96.7%

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 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

November 3, 2026 · 31 trips in the retained timetable · retained notices; capture coverage unverified

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

06:01– 06:38
Trip sto:63296040Insufficient coverage or identity; outcome unknown
06:11– 06:48
Trip sto:63296018Insufficient coverage or identity; outcome unknown
06:21– 06:58
Trip sto:63296015Insufficient coverage or identity; outcome unknown
06:31– 07:08
Trip sto:63296006Insufficient coverage or identity; outcome unknown
06:40– 07:17
Trip sto:63296023Insufficient coverage or identity; outcome unknown
06:51– 07:28
Trip sto:63296284Insufficient coverage or identity; outcome unknown
07:01– 07:38
Trip sto:63296285Insufficient coverage or identity; outcome unknown
07:11– 07:48
Trip sto:63296286Insufficient coverage or identity; outcome unknown
07:20– 07:57
Trip sto:63296287Insufficient coverage or identity; outcome unknown
07:31– 08:08
Trip sto:63296288Insufficient coverage or identity; outcome unknown
07:45– 08:22
Trip sto:63296289Insufficient coverage or identity; outcome unknown
07:55– 08:32
Trip sto:63296290Insufficient coverage or identity; outcome unknown

· Open all evidence for this day

Draft

This translation is a draft.

Help improve it

About 23% 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 Mohawk (Kanien’kéha), the language of the Kanien’kehá:ka (Mohawk) communities. 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 mohawk (kanien’kéha), la langue des communautés kanien’kehá:ka (mohawks). 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).