Detour Route 371 South: Route 371 diverted from Laval to Station Lyon.

No 371 trips cancelled now · 4 did not run in NovemberCancellations →

STO route 371: Cgp G-Roy/Mutchmore

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

CENTRE RIDEAU4 min sched.
ALBERT/METCALFE7 min sched.
ALBERT/BANK9 min sched.
KENT / SPARKS11 min sched.
WELLINGTON/LYON12 min sched.
du PORTAGE/AUBRY18 min sched.
du PORTAGE/LAVAL19 min sched.
LAURIER/EDDY0 min sched.
ALEXANDRE-TACHÉ/MILLAR4 min sched.
ALEXANDRE-TACHÉ/SAINT-JOSEPH6 min sched.
SAINT-JOSEPH/RENÉ-ROGER7 min sched.
SAINT-JOSEPH/DUQUESNE8 min sched.
SAINT-JOSEPH/SAINT-JEAN-BOSCO9 min sched.
SAINT-JOSEPH/MONTCALM11 min sched.
SAINT-JOSEPH/DALPÉ12 min sched.
SAINT-JOSEPH/WìGWÀS13 min sched.
SAINT-JOSEPH/BRODEUR13 min sched.
SAINT-JOSEPH/NICOLET14 min sched.
SAINT-JOSEPH/SAINTE-MARIE15 min sched.
SAINT-JOSEPH/GAMELIN17 min sched.
SAINT-JOSEPH/CHARLES-CHURCH19 min sched.
MUTCHMORE/RENÉ-MARENGÈRE20 min sched.
MUTCHMORE/ABIGAIL21 min sched.
MUTCHMORE/LOUIS-HÉBERT21 min sched.
MUTCHMORE/LESAGE22 min sched.
MUTCHMORE/MEUNIER24 min sched.
MUTCHMORE/SAINT-JOSEPH0 min sched.
ISABELLE/RICHARD1 min sched.
ISABELLE/WILFRID-LATOUR1 min sched.
JOLICOEUR/CHOUINARD2 min sched.
PHILIAS-FORTIN/du MONT-BLEU4 min sched.
GEORGES-BILODEAU/LUCIEN-BRAULT4 min sched.
CHARLES-ALBANEL/LE BRETON6 min sched.
CHARLES-ALBANEL/JUMONVILLE7 min sched.
DANIEL-JOHNSON/JUMONVILLE8 min sched.
DANIEL-JOHNSON/LUCIEN-BRAULT8 min sched.
du MONT-BLEU/GEORGES-BILODEAU9 min sched.
du MONT-BLEU/PÈRE-BÉLAND10 min sched.
du MONT-BLEU/JOLICOEUR10 min sched.
du MONT-BLEU/des MAGNOLIAS11 min sched.
du MONT-BLEU/MARCOUX12 min sched.
du MONT-BLEU/de la CITÉ-DES-JEUNES12 min sched.
CEGEP GABRIELLE-ROY/arrivée13 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

4 of 275 trips with a usable feed window (1.5%) had no matching position.

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

271 with position · 4 to investigate · 53 excluded · 328 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 4, 2026, 4:25 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.

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

Published position coverage: 271 / 328 (82.6%). 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, 3:18 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

No comparable percentage published

This service purpose needs a different method. A general percentage could give a misleading picture.

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

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?

The general hourly comparison is not suitable for this service purpose. Source records remain available.

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

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

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

Buses arriving bunched
Time of day	Pairs checked	Bunched	Long gap
Morning rush (6 to 9 a.m.)	1,952	0% (1)	0% (0)
Midday (9 a.m. to 3 p.m.)	68	0% (0)	0% (0)
Afternoon rush (3 to 6 p.m.)	5,033	1% (38)	2% (102)
Evening (6 to 10 p.m.)	2,595	0% (0)	0% (0)

How this is measured →How we got this numberBunching and slow spots on every route →

Where this route is slowest

Slowest: CENTRE RIDEAU to KENT / SPARKS, 7.8 km/h actual against 13.2 km/h planned.

Where this route is slowest
From	To	Distance	Planned speed	Actual speed	Trips measured	Slow trips
CENTRE RIDEAU	KENT / SPARKS	1.2 km	13.2 km/h	7.8 km/h	378	40%
CEGEP GABRIELLE-ROY	DANIEL-JOHNSON/LUCIEN-BRAULT	1.7 km	15.9 km/h	8.4 km/h	352	55%
KENT / SPARKS	du PORTAGE/AUBRY	1.2 km	11.4 km/h	8.6 km/h	387	32%
TERRASSES de la CHAUDIÈRE	de l'HÔTEL-de-VILLE/LAURIER	750 m	12.2 km/h	11.3 km/h	374	13%
SAINT-JOSEPH/SAINTE-MARIE	SAINT-JOSEPH/NICOLET	410 m	11.1 km/h	12.7 km/h	375	11%
du PORTAGE/AUBRY	LAURIER/EDDY	470 m	12 km/h	13.2 km/h	398	6%
SAINT-JOSEPH/SAINTE-MARIE	SAINT-JOSEPH/CHARLES-CHURCH	830 m	13.3 km/h	13.3 km/h	398	9%
ALEXANDRE-TACHÉ/SAINT-JOSEPH	SAINT-JOSEPH/MONTCALM	850 m	12.4 km/h	14 km/h	396	4%

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

How this is measured →

City road work near this route

Road work and event road closures the City of Ottawa has published, measured as near this route’s path. Near is not proof that the bus is detoured: check the operator’s own alerts for that.

Road work
ALBERT between ELGIN and METCALFE
Oct 29, 2026, 12:00 a.m. to Jan 26, 2027, 5:00 p.m.
ALBERT lane reduction between ELGIN and METCALFE due to construction, from October 29th to January 26th.
The City marks this as affecting transit.
about 0 m from the route
City record updated Nov 2, 2026, 12:44 p.m..
Road work
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..
Road work
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: 1 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. (1)

Latest cancelled trips

Wed, Oct 21, scheduled 16:10

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: 4 of 275 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	Weekdays	Saturdays	Sundays
Before 6 am	Usually seats0% of 55 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats9.7% of 350 trips	Usually seats0% of 31 trips	Usually seats0% of 30 trips
9 am to 3 pm	Usually seats9.4% of 520 trips	Usually seats7.8% of 103 trips	Usually seats8.9% of 90 trips
3 to 6 pm	Usually seats21.5% of 531 trips	Usually seats35.2% of 54 trips	Usually seats18.4% of 49 trips
6 to 10 pm	Usually seats5.6% of 483 trips	Usually seats12.2% of 74 trips	Usually seats3.1% of 65 trips
After 10 pm	Usually seats3.5% of 143 trips	Usually seats0% of 36 trips	Usually seats0% of 28 trips

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 371 has been running

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

Bottom line

We need to confirm how this service is meant to work before rating it.

Prediction sample size: Larger sample

Based on 35,533 eligible provider predictions over 22 measured days, from Oct 6, 2026 to Nov 3, 2026.

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

Problem times are not ranked because this service needs a purpose-specific test.

1 current notice affects this route

• Detour Route 371 South

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 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?: 4 of 275 checked trips need a closer look4 of 275 trips with enough public-feed evidence had no matching position over 7 days. 53 of 328 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?: Not enough evidence yet
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 the first Monday after the new schedule began and the Monday one week earlier. Every figure comes from the retained 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.

Before

Service date checked: October 26, 2026

Scheduled trips: 0
Distinct scheduled stops: 0
Distinct published paths: 0
Published service span: —–—

Feed fingerprint: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

New schedule

Service date checked: November 2, 2026

Scheduled trips: 52
Distinct scheduled stops: 86
Distinct published paths: 3
Published service span: 5:18 a.m.–12:31 a.m. next day

Operator calendar-date records: 1 added · 0 removed

Feed fingerprint: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

Did service improve after the change?

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.

Ordinary on-time scoring does not fit this route’s service purpose. The schedule counts remain visible, but the result waits for the purpose-specific evidence described below.

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: School route

No grade is shown until a purpose-specific completion and pickup measure is available.

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

Data behind this result

An ordinary on-time grade is not appropriate for this service without checking its purpose. The route check above explains the pickup, community-service or event evidence needed. You can still inspect the recorded trips and data gaps below.

Evidence window: October 6, 2026 to November 3, 2026

Eligible predictions checked: 35,533
Weekdays with data: 17

Scheduled bus, but not observed in realtime

271 / 328 scheduled trips published at least one position across 5 service days (82.6%).

22:004 / 9 trips without a position55.6%
19:007 / 19 trips without a position63.2%
23:005 / 14 trips without a position64.3%
06:005 / 15 trips without a position66.7%
07:008 / 24 trips without a position66.7%
05:003 / 10 trips without a position70.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 · 52 trips in the retained timetable · retained notices; capture coverage unverified

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

05:18– 06:02
Trip sto:63295371Insufficient coverage or identity; outcome unknown
05:49– 06:35
Trip sto:63295840Insufficient coverage or identity; outcome unknown
06:19– 07:08
Trip sto:63295099Insufficient coverage or identity; outcome unknown
06:45– 07:29
Trip sto:63295196Insufficient coverage or identity; outcome unknown
06:47– 07:38
Trip sto:63295210Insufficient coverage or identity; outcome unknown
07:16– 08:04
Trip sto:63295096Insufficient coverage or identity; outcome unknown
07:18– 08:13
Trip sto:63296393Insufficient coverage or identity; outcome unknown
07:46– 08:34
Trip sto:63294756Insufficient coverage or identity; outcome unknown
07:48– 08:43
Trip sto:63296388Insufficient coverage or identity; outcome unknown
08:15– 09:01
Trip sto:63294576Insufficient coverage or identity; outcome unknown
08:18– 09:09
Trip sto:63295739Insufficient coverage or identity; outcome unknown
08:50– 09:41
Trip sto:63294636Vehicle position matchedFirst / last feed position: 9:23 a.m. EST / 9:35 a.m. EST; not actual start or end times.

· Open all evidence for this day