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

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

STO ᐊᖁᑎᖓ 54: Parc Champlain

ᑐᕌᖓᔪᖅHochelaga0 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)

PARC-O-BUS RIVERMEAD63 min sched.
JEAN-DE LA FONTAINE/ÉMILE-ZOLA65 min sched.
JEAN-DE LA FONTAINE/PIERRE-DE RONSARD66 min sched.
JEAN-DE LA FONTAINE/MCCONNELL67 min sched.
MCCONNELL/des MANOIRS68 min sched.
d'HOCHELAGA/ATHOLL DOUNE76 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

1 of 22 trips with a usable feed window (4.5%) had no matching position.

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

21 with position · 1 to investigate · 8 excluded · 30 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 21 / 30 (70%). 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:28 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

84.2%

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

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

The hours we have evidence for

0680% · 39 predictions · 6 days
0788% · 49 predictions · 6 days
0871% · 38 predictions · 6 days
1595% · 39 predictions · 7 days
17100% · 39 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 4, 2026

6 partial-capture days not counted.

What about time of day?

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

Too few buses were measured to judge bunching: 0 pairs checked, 30 needed.

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

Where this route is slowest

Slowest: PARC-O-BUS RIVERMEAD to JEAN-DE LA FONTAINE/MCCONNELL, 7.5 km/h actual against 17.9 km/h planned.

Where this route is slowest
ᐱᒋᐊᕐᕕᒃ	ᑐᕌᕐᕕᒃ	ᐅᖓᓯᒋᓂᖓ	Planned speed	Actual speed	Trips measured	Slow trips
PARC-O-BUS RIVERMEAD	JEAN-DE LA FONTAINE/MCCONNELL	1.2 km	17.9 km/h	7.5 km/h	29	69%
d'HOCHELAGA/ATHOLL DOUNE	JEAN-DE LA FONTAINE/ALEXANDRE-DUMAS	2.4 km	16.2 km/h	8 km/h	28	82%
JEAN-DE LA FONTAINE/MCCONNELL	d'HOCHELAGA/ATHOLL DOUNE	1.9 km	12.8 km/h	13.5 km/h	26	0%
JEAN-DE LA FONTAINE/ALEXANDRE-DUMAS	PARC-O-BUS RIVERMEAD arrivée RIVERMEAD	1.1 km	16.6 km/h	17.9 km/h	28	0%

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 →

6 partial-capture days not counted.

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

Latest cancelled trips

Thu, Oct 29, scheduled 16:46
Thu, Oct 22, scheduled 16:46
Mon, Oct 19, scheduled 17:46
Wed, Oct 14, scheduled 17:46

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	ᐱᓇᓱᐊᕈᓰᑦ	ᓈᑦᓰᓈᕐᕕᒃᑯᑦ	ᓈᑦᑏᖑᔭᕐᓂ
Before 6 am	Not enough readings	Not enough readings	Not enough readings
6 to 9 am	Usually seats0% of 75 trips	Not enough readings	Not enough readings
9 am to 3 pm	Not enough readings	Not enough readings	Not enough readings
3 to 6 pm	Usually seats0% of 89 trips	Not enough readings	Not enough readings
6 to 10 pm	Not enough readings	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 history, reliability and route analysis

Route check

How route 54 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, but check the problem times below.

84 in 100 eligible predictions were within 5 minutes of the timetable · 532 predictions checked

Prediction sample size: Moderate sample

Based on 532 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.

16–17: 30 in 100 eligible predictions differed from the timetable by more than 5 minutes (23 predictions over 5 days).

No current official notice matches this route.

Prediction differences by stop

We do not yet have enough route-by-stop history to name a recurring problem stop. Rider reports are used as leads, not proof.

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 3Checks 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 22 checked trips need a closer look1 of 22 trips with enough public-feed evidence had no matching position over 7 days. 8 of 30 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 6.0 min (positive means later; negative means earlier)84 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.

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

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

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

Current published schedule began November 2, 2026

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

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

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

ᓯᕗᓂᐊᓂ

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

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 0
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 0
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 0
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: —–—

ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᓯᒋᐊᕈᑎᖓ: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

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

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

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 6
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 16
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 2
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 06:48–17:59

Operator calendar-date records: 1 added · 0 removed

ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᓯᒋᐊᕈᑎᖓ: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

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

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

Still collecting: before has 266 arrivals over 10 days; after has 34 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: 84.2%
Eligible predictions checked: 532
Weekdays with data: 17
95th-percentile predicted delay: 6 min late

Patterns by hour (6)

Patterns by hour (6)
ᐃᑲᕐᕋᖅ	ᐱᕕᒃᓴᖓᓂ	Median	95th percentile	ᓇᓗᓇᐃᖅᓯᔾᔪᑎᑦ
06:00	79.5%	1.7 min late	6 min late	39 · 6 days
07:00	87.8%	1.4 min late	5.8 min late	49 · 6 days
08:00	71.1%	0.7 min late	5.9 min late	38 · 6 days
15:00	94.9%	0.6 min late	3 min late	39 · 7 days
16:00	69.6%	0.7 min late	12 min late	23 · 5 days
17:00	100.0%	0.8 min late	3.9 min late	39 · 7 days

1 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

21 / 30 scheduled trips published at least one position across 5 service days (70.0%).

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

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

06:48– 07:01
Trip sto:63296282Insufficient coverage or identity; outcome unknown
07:44– 07:57
Trip sto:63296280Insufficient coverage or identity; outcome unknown
08:48– 09:01
Trip sto:63296283Insufficient coverage or identity; outcome unknown
15:46– 15:59
Trip sto:63296278Vehicle position matchedFirst / last feed position: 3:43 p.m. EST / 3:49 p.m. EST; not actual start or end times.
16:46– 16:59
Trip sto:63296279Vehicle position matchedFirst / last feed position: 4:40 p.m. EST / 4:53 p.m. EST; not actual start or end times.
17:46– 17:59
Trip sto:63296281Vehicle position matchedFirst / last feed position: 5:32 p.m. EST / 5:58 p.m. EST; not actual start or end times.

ᑐᕌᕝᑦ

ᑖᓐᓇ ᐅᖃᐅᓯᒧᑦ ᐊᓯᔾᔨᖅᓯᒪᔪᖅ ᑐᕌᕝᑦᐅᕗᖅ.

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