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

No 400 trips cancelled now · 8 did not run in NovemberCancellations →

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

400

STO route 400: Rapibus 400

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

CENTRE RIDEAU
ALBERT/METCALFE
ALBERT/BANK
KENT / SPARKS
WELLINGTON/LYON
du PORTAGE/AUBRY
du PORTAGE/LAVAL
EDDY/WELLINGTON
MONTCALM/WRIGHT
MONTCALM/GAGNON
Station MONTCALM #3
Station LES GALERIES #2
Station CASINO #2
Station LAC LEAMY #2
Station de la GAPPE #31 min sched.
Station PROMENADES #23 min sched.
Station de la CITÉ #32 min sched.
Station GOUIN #25 min sched.
Station LABROSSE #047 min sched.
Station Lac Beauchamp #210 min sched.
STATION LORRAIN arrêt d'arrivée1 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. Not counted: 1 trips with qualifying later matching vehicle observations; 2 for trips not in the published timetable that day. Trips with any notice: 4.

Trips needing investigation

8 of 1,071 trips with a usable feed window (0.7%) had no matching position.

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

1,063 with position · 8 to investigate · 156 excluded · 1,227 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.

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

Published position coverage: 1,063 / 1,227 (86.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, 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

82.6%

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

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

The hours we have evidence for

0088% · 658 predictions · 10 days
0498% · 50 predictions · 7 days
0595% · 897 predictions · 10 days
0695% · 1,280 predictions · 10 days
0787% · 962 predictions · 9 days
0878% · 1,204 predictions · 10 days
0986% · 2,244 predictions · 11 days
1087% · 2,241 predictions · 11 days
1191% · 2,408 predictions · 12 days
1287% · 2,510 predictions · 12 days
1387% · 2,524 predictions · 12 days
1482% · 2,731 predictions · 13 days
1585% · 2,087 predictions · 12 days
1685% · 1,277 predictions · 13 days
1783% · 1,656 predictions · 12 days
1883% · 2,436 predictions · 11 days
1983% · 1,935 predictions · 11 days
2083% · 1,833 predictions · 10 days
2181% · 1,658 predictions · 10 days
2282% · 1,661 predictions · 10 days
2384% · 1,498 predictions · 10 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?

21 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

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

3% of pairs (1,627) 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
Early morning (4 to 6 a.m.)	1,303	3% (36)	1% (17)
Morning rush (6 to 9 a.m.)	5,756	2% (103)	1% (81)
Midday (9 a.m. to 3 p.m.)	24,964	4% (899)	3% (646)
Afternoon rush (3 to 6 p.m.)	8,394	6% (470)	5% (407)
Evening (6 to 10 p.m.)	13,523	4% (495)	3% (421)
Night (10 p.m. to 4 a.m.)	6,651	1% (62)	1% (55)

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

Where this route is slowest

Slowest: CENTRE RIDEAU to du PORTAGE/AUBRY, 8.6 km/h actual against 13.9 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
CENTRE RIDEAU	du PORTAGE/AUBRY	2.4 km	13.9 km/h	8.6 km/h	1,312	44%
TERRASSES de la CHAUDIÈRE	de l'HÔTEL-de-VILLE/LAURIER	750 m	15.5 km/h	11.9 km/h	1,489	30%
du PORTAGE/AUBRY	EDDY/WELLINGTON	450 m	11 km/h	12 km/h	1,435	8%
MONTCALM/HANSON	TERRASSES de la CHAUDIÈRE	930 m	13.2 km/h	15.8 km/h	1,492	1%
Station de la CITÉ #2	Station PROMENADES #1	1.1 km	15.8 km/h	16.5 km/h	1,490	3%
de l'HÔTEL-de-VILLE/LAURIER	CENTRE RIDEAU	2.5 km	13.2 km/h	16.6 km/h	1,300	0%
STATION LORRAIN	Station LABROSSE #1	2.9 km	42.9 km/h	16.6 km/h	1,361	69%
EDDY/WELLINGTON	Station MONTCALM #3	960 m	16.6 km/h	17.5 km/h	1,437	3%

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

4 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 2 for trips not in that day’s timetable.

Hours with the most cancellations: 5 a.m. (1), 10 a.m. (1), 1 p.m. (1)

Latest cancelled trips

Fri, Oct 30, scheduled 10:06
Tue, Oct 20, scheduled 05:45
Fri, Oct 16, scheduled 13:57
Wed, Oct 7, scheduled 22:03

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: 8 of 1,071 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 seats14.1% of 377 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats18% of 866 trips	Usually seats1.2% of 170 trips	Usually seats0.7% of 146 trips
9 am to 3 pm	Usually seats26.3% of 2,898 trips	Usually seats12.2% of 362 trips	Usually seats5.7% of 335 trips
3 to 6 pm	Usually seats40% of 1,243 trips	Usually seats23.1% of 208 trips	Usually seats9.7% of 196 trips
6 to 10 pm	Usually seats23.2% of 1,645 trips	Usually seats3.6% of 248 trips	Usually seats1.3% of 240 trips
After 10 pm	Usually seats7.3% of 722 trips	Usually seats2.7% of 147 trips	Usually seats0% of 132 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 400 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.

83 in 100 eligible predictions were within 5 minutes of the timetable · 67,176 predictions checked

Prediction sample size: Larger sample

Based on 67,176 eligible provider predictions over 22 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.

1 current notice affects this route

• Detour Route 400 South

Prediction differences by stop

STATION LORRAIN
47 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,665 predictions over 24 days).
Open this stop
MONTCALM/WRIGHT
36 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,726 predictions over 24 days).
Open this stop
du PORTAGE/AUBRY
35 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,716 predictions over 24 days).
Open this stop
EDDY/WELLINGTON
31 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,725 predictions over 24 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?: 8 of 1,071 checked trips need a closer look8 of 1,071 trips with enough public-feed evidence had no matching position over 7 days. 156 of 1,227 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 8.3 min (positive means later; negative means earlier)83 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.0 min average predicted wait0.9 min beyond the scheduled wait, based on 25,385 eligible predictions at 43 high-frequency stops over 14 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: 187
Distinct scheduled stops: 43
Distinct published paths: 4
Kahiatónhsera: tsi niió:re ne kà:sere: 04:45–00:45 next day

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 37,179 arrivals over 13 days; after has 5,218 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: 82.6%
Eligible predictions checked: 67,176
Weekdays with data: 17
95th-percentile predicted delay: 8.3 min late

Patterns by hour (21)

Patterns by hour (21)
Hour	Ioiánere tsi nikarì:wes	Median	95th percentile	Tsi tó:kenske
00:00	88.4%	0.4 min late	6.6 min late	658 · 10 days
04:00	98.0%	0.1 min late	2 min late	50 · 7 days
05:00	94.6%	0.4 min late	4 min late	897 · 10 days
06:00	95.3%	0.6 min late	4.3 min late	1,280 · 10 days
07:00	87.0%	1.5 min late	6.6 min late	962 · 9 days
08:00	77.7%	2.1 min late	8.5 min late	1,204 · 10 days
09:00	86.1%	1 min late	8 min late	2,244 · 11 days
10:00	86.8%	1.2 min late	6.8 min late	2,241 · 11 days
11:00	90.6%	0.5 min late	5.5 min late	2,408 · 12 days
12:00	87.3%	1 min late	7.9 min late	2,510 · 12 days
13:00	86.5%	1.4 min late	7.4 min late	2,524 · 12 days
14:00	81.6%	1.5 min late	8.4 min late	2,731 · 13 days
15:00	84.9%	1.3 min late	9.2 min late	2,087 · 12 days
16:00	85.3%	1.1 min late	8.3 min late	1,277 · 13 days
17:00	82.7%	1.7 min late	7.4 min late	1,656 · 12 days
18:00	83.1%	1.4 min late	8.3 min late	2,436 · 11 days
19:00	82.9%	2.1 min late	7.7 min late	1,935 · 11 days
20:00	83.0%	2.1 min late	8.1 min late	1,833 · 10 days
21:00	80.6%	2.1 min late	7.8 min late	1,658 · 10 days
22:00	82.1%	2.1 min late	8.2 min late	1,661 · 10 days
23:00	84.2%	1.6 min late	7.9 min late	1,498 · 10 days

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

Scheduled bus, but not observed in realtime

1,063 / 1,227 scheduled trips published at least one position across 7 service days (86.6%).

23:0017 / 51 trips without a position66.7%
22:0018 / 56 trips without a position67.9%
21:0017 / 56 trips without a position69.6%
20:0018 / 61 trips without a position70.5%
19:0019 / 66 trips without a position71.2%
00:004 / 14 trips without a position71.4%

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 · 187 trips in the retained timetable · retained notices; capture coverage unverified

In short: 153 with a matched position · 6 with no matching position (to investigate) · 28 with an unknown outcome.

04:45– 05:29
Trip sto:63296005Insufficient coverage or identity; outcome unknown
04:55– 05:39
Trip sto:63296007Insufficient coverage or identity; outcome unknown
05:05– 05:49
Trip sto:63296008Insufficient coverage or identity; outcome unknown
05:15– 05:59
Trip sto:63296009Insufficient coverage or identity; outcome unknown
05:25– 06:09
Trip sto:63296010Insufficient coverage or identity; outcome unknown
05:30– 06:13
Trip sto:63290293Insufficient coverage or identity; outcome unknown
05:35– 06:21
Trip sto:63296011Insufficient coverage or identity; outcome unknown
05:40– 06:26
Trip sto:63296012Insufficient coverage or identity; outcome unknown
05:45– 06:28
Trip sto:63294599Insufficient coverage or identity; outcome unknown
05:45– 06:31
Trip sto:63296013Insufficient coverage or identity; outcome unknown
05:49– 06:35
Trip sto:63296014Insufficient coverage or identity; outcome unknown
05:55– 06:41
Trip sto:63296098Insufficient 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).