Detour Route 23 South: Route 23 diverted from CLSC Hull to Terrasses.+3 more notice

No 23 trips cancelled now · 2 did not run in NovemberCancellations →

Previous measure: 64.6% of arrivals were within five minutes of the timetable (4,703 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 23: Le Plateau

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

STATION LYON44 min sched.
SLATER/KENT45 min sched.
BANK/WELLINGTON49 min sched.
WELLINGTON/LYON51 min sched.
du PORTAGE/AUBRY57 min sched.
du PORTAGE/LAVAL58 min sched.
EDDY/WELLINGTON60 min sched.
MONTCALM/WRIGHT62 min sched.
MONTCALM/GAGNON63 min sched.
Station MONTCALM #365 min sched.
MONTCALM/LOIS66 min sched.
des ALLUMETTIÈRES/SAINT-JOSEPH67 min sched.
des ALLUMETTIÈRES/DEMONTIGNY67 min sched.
des ALLUMETTIÈRES/LABELLE68 min sched.
du PLATEAU/SAINT-RAYMOND74 min sched.
du PLATEAU/des CÈDRES75 min sched.
de l'ATMOSPHÈRE/du PLATEAU76 min sched.
de l'ATMOSPHÈRE/de l'ASTROLABE76 min sched.
de l'ATMOSPHÈRE/de la SAPINIÈRE77 min sched.
de l'ATMOSPHÈRE/de L'ÉCLIPSE78 min sched.
de l'ATMOSPHÈRE/de l'ÉQUATEUR79 min sched.
de l'ATMOSPHÈRE/du FIRMAMENT80 min sched.
de l'ATMOSPHÈRE/des GRIVES81 min sched.
de l'ATMOSPHÈRE/du PRINTEMPS82 min sched.
de l'ATMOSPHÈRE/de la NÉBULEUSE83 min sched.
de l'ATMOSPHÈRE/du TROPIQUE84 min sched.
AGORA85 min sched.
PLATEAU/EUROPE86 min sched.
du PLATEAU/du PRADO87 min sched.
du PLATEAU/de l'AMÉRIQUE-FRANÇAISE87 min sched.
du PLATEAU/d'AMSTERDAM88 min sched.
d'AMSTERDAM/de STOCKHOLM89 min sched.
d'AMSTERDAM/de BARCELONE89 min sched.
d'AMSTERDAM/de BARCELONE90 min sched.
d'AMSTERDAM/LIVERPOOL91 min sched.
d'AMSTERDAM/VANIER91 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

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 43 trips with a usable feed window (4.7%) had no matching position.

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

41 with position · 2 to investigate · 12 excluded · 55 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 41 / 55 (74.5%). 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, 1:37 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

64.6%

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

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

The hours we have evidence for

0699% · 326 predictions · 7 days
0792% · 318 predictions · 6 days
0861% · 246 predictions · 7 days
1585% · 138 predictions · 8 days
1666% · 363 predictions · 10 days
1766% · 609 predictions · 9 days
1884% · 254 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

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

0% of pairs (1) 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.)	835	0% (0)	0% (1)
Afternoon rush (3 to 6 p.m.)	997	2% (16)	0% (0)
Evening (6 to 10 p.m.)	325	0% (0)	0% (0)

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

Where this route is slowest

Slowest: STATION LYON to WELLINGTON/LYON, 6.3 km/h actual against 8 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
STATION LYON	WELLINGTON/LYON	890 m	8 km/h	6.3 km/h	49	22%
WELLINGTON/LYON	du PORTAGE/AUBRY	1 km	11.7 km/h	7.8 km/h	64	56%
du PORTAGE/AUBRY	EDDY/WELLINGTON	450 m	9.6 km/h	9.6 km/h	69	7%
d'AMSTERDAM/VANIER	PLATEAU/EUROPE	1.9 km	15.9 km/h	11.2 km/h	47	21%
de l'HÔTEL-de-VILLE/LAURIER	BANK/WELLINGTON	1.7 km	7.9 km/h	11.6 km/h	46	0%
EDDY/WELLINGTON	Station MONTCALM #3	960 m	12 km/h	13 km/h	73	4%
du PLATEAU/SAINT-RAYMOND	de l'HÔTEL-de-VILLE/LAURIER	4.9 km	17.8 km/h	16 km/h	47	0%
de l'ATMOSPHÈRE/des GRIVES	PLATEAU/EUROPE	1.1 km	14.6 km/h	17.4 km/h	68	4%

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

Tsi ní:ioht →

City road work, kí:ken route

Road work tánon event road closures, City of Ottawa published. Measured near ne route. Near iah proof tsi bus detoured. Check ne operator alerts.

Oháha: kaio'tén:sera
Slater between Bay and Lyon
Oct 30, 2026, 12:00 a.m. to Nov 6, 2026, 5:00 p.m.
Slater lane reduction between Bay and Lyon due to construction, from November 2nd to 6th.
about 0 m from the route
City record updated Oct 30, 2026, 1:28 p.m..
Oháha: kaio'tén:sera
ALBERT at LYON
Dates not published
Albert and Lyon off-peak lane reductions at the intersection due to construction.
about 2 m from the route
City record updated Sep 9, 2026, 6:32 p.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.

Source: City of Ottawa traffic events (road work and closures). Contains information licensed under the Open Government Licence, City of Ottawa. The City says this list is best effort and may be incomplete. City of Ottawa traffic map ↗

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

Latest cancelled trips

Fri, Oct 30, scheduled 15:22

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: 2 of 43 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	Not enough readings	Not enough readings	Not enough readings
6 to 9 am	Usually seats45.7% of 127 trips	Not enough readings	Not enough readings
9 am to 3 pm	Usually seats5.9% of 17 trips	Not enough readings	Not enough readings
3 to 6 pm	Usually seats20.6% of 141 trips	Not enough readings	Not enough readings
6 to 10 pm	Usually seats2.2% of 46 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

Median provider predictions are 4 to 4.5 min later than the timetable in 2 hours of the day.

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

Scenario: 4 to 5 min more running time on 12 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, 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: 99.1% of final predictions within five minutes of the timetable, 326 predictions, typically 2.5 min late
07:00: 91.5% of final predictions within five minutes of the timetable, 318 predictions, typically 1.3 min late
08:00: 61% of final predictions within five minutes of the timetable, 246 predictions, typically 4.5 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: 84.8% of final predictions within five minutes of the timetable, 138 predictions, typically 2.3 min late
16:00: 66.4% of final predictions within five minutes of the timetable, 363 predictions, typically 4 min late
17:00: 66% of final predictions within five minutes of the timetable, 609 predictions, typically 2.9 min late
18:00: 84.3% of final predictions within five minutes of the timetable, 254 predictions, typically 0.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	Ó:nen	Tewaterièn:tare	Scenario or next investigation
ProblemPredictions later than timetable	08:00 · 16:00	4.5 min late · 4 min late	More running time
ProblemOne hour has a lower prediction match	08:00	61%	Operations, not the timetable

Measurements

Predictions later than timetable · 16:00: Measured arrivals 363; Hours affected 1; Spread 9 min; Median delay 4 min; Suggested running time change 4 min
Predictions later than timetable · 08:00: Measured arrivals 246; Hours affected 1; Spread 4 min; Median delay 4.5 min; Suggested running time change 4.5 min
One hour has a lower prediction match · 08:00: Hour 08:00; Ioiánere tsi nikarì:wes 61%; Measured arrivals 246; Shortfall 23.3 pts; Route median on time 84.3%

Open history, reliability and route analysis

Route check

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

65 in 100 eligible predictions were within 5 minutes of the timetable · 4,703 predictions checked

Prediction sample size: Larger sample

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

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

08–09: 39 in 100 eligible predictions differed from the timetable by more than 5 minutes (246 predictions over 7 days).
17–18: 34 in 100 eligible predictions differed from the timetable by more than 5 minutes (609 predictions over 9 days).
16–17: 34 in 100 eligible predictions differed from the timetable by more than 5 minutes (363 predictions over 10 days).

2 current notices affect this route

• Detour Route 23 South
• Detour Route 23 South

Prediction differences by stop

des ALLUMETTIÈRES/LABELLE
64 in 100 eligible predictions differed from the timetable by more than 5 minutes (85 predictions over 18 days).
Open this stop
d'AMSTERDAM/de BARCELONE
56 in 100 eligible predictions differed from the timetable by more than 5 minutes (81 predictions over 17 days).
Open this stop
du PLATEAU/des CÈDRES
54 in 100 eligible predictions differed from the timetable by more than 5 minutes (85 predictions over 18 days).
Open this stop
des ALLUMETTIÈRES/DEMONTIGNY
54 in 100 eligible predictions differed from the timetable by more than 5 minutes (85 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 6Checks 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 43 checked trips need a closer look2 of 43 trips with enough public-feed evidence had no matching position over 7 days. 12 of 55 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.2 min (positive means later; negative means earlier)65 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.

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: 11
Distinct scheduled stops: 70
Distinct published paths: 2
Kahiatónhsera: tsi niió:re ne kà:sere: 06:09–18:27

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 2,644 arrivals over 10 days; after has 232 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 6, 2026 to November 3, 2026

Within 5 minutes of schedule: 64.6%
Eligible predictions checked: 4,703
Weekdays with data: 17
95th-percentile predicted delay: 13.2 min late

Patterns by hour (7)

Patterns by hour (7)
Hour	Ioiánere tsi nikarì:wes	Median	95th percentile	Tsi tó:kenske
06:00	99.1%	2.5 min late	3.9 min late	326 · 7 days
07:00	91.5%	1.3 min late	5.4 min late	318 · 6 days
08:00	61.0%	4.5 min late	8.5 min late	246 · 7 days
15:00	84.8%	2.3 min late	6.2 min late	138 · 8 days
16:00	66.4%	4 min late	13 min late	363 · 10 days
17:00	66.0%	2.9 min late	14.8 min late	609 · 9 days
18:00	84.3%	0.9 min late	6.4 min late	254 · 8 days

3 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

41 / 55 scheduled trips published at least one position across 5 service days (74.5%).

07:004 / 10 trips without a position60.0%
06:003 / 10 trips without a position70.0%
15:003 / 10 trips without a position70.0%
17:003 / 10 trips without a position70.0%
08:001 / 5 trips without a position80.0%
16: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 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

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

In short: 4 with a matched position · 2 with no matching position (to investigate) · 5 with an unknown outcome.

06:09– 06:52
Trip sto:63295933Insufficient coverage or identity; outcome unknown
06:39– 07:22
Trip sto:63294569Insufficient coverage or identity; outcome unknown
07:09– 07:56
Trip sto:63296138Insufficient coverage or identity; outcome unknown
07:43– 08:30
Trip sto:63295547Insufficient coverage or identity; outcome unknown
08:09– 08:59
Trip sto:63295529Insufficient coverage or identity; outcome unknown
15:22– 16:09
Trip sto:63296186No matching position; investigate, not a confirmed cancellation
15:50– 16:37
Trip sto:63294901Vehicle position matchedFirst / last feed position: 3:51 p.m. EST / 4:41 p.m. EST; not actual start or end times.
16:24– 17:11
Trip sto:63294724Vehicle position matchedFirst / last feed position: 4:26 p.m. EST / 5:24 p.m. EST; not actual start or end times.
16:50– 17:36
Trip sto:63294732Vehicle position matchedFirst / last feed position: 4:59 p.m. EST / 5:45 p.m. EST; not actual start or end times.
17:18– 17:59
Trip sto:63295725No matching position; investigate, not a confirmed cancellation
17:50– 18:27
Trip sto:63294721Vehicle position matchedFirst / last feed position: 5:59 p.m. EST / 6:27 p.m. EST; not actual start or end times.

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