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

No 400 trips cancelled now · 10 did not run in 十一月Cancellations →

Previous measure: 82.9% of arrivals were within five minutes of the timetable (64,037 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 线路 400: Rapibus 400

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

Next: 8.5 min after the pair

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: 2026年10月29日 – 2026年11月4日

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: 2 trips with qualifying later matching vehicle observations; 2 for trips not in the published timetable that day. Trips with any notice: 5.

Trips needing investigation

10 of 1,036 trips with a usable feed window (1%) had no matching position.

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

1,026 with position · 10 to investigate · 191 excluded · 1,227 scheduled trips

Current feed. Current feed unavailable; no cancellation count is assumed.

Coverage, exclusions and sources

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

Published position coverage: 1,026 / 1,227 (83.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: 2026年11月5日 22:09

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

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

Predictions in the source: 64,037
Weekdays with evidence: 17
Evidence window: 2026年10月7日 – 2026年11月4日

The hours we have evidence for

0时88% · 658 predictions · 10 days
4时96% · 52 predictions · 7 days
5时95% · 1,033 predictions · 11 days
6时95% · 1,475 predictions · 11 days
7时86% · 1,103 predictions · 10 days
8时80% · 1,365 predictions · 11 days
9时87% · 2,417 predictions · 12 days
10时87% · 1,987 predictions · 11 days
11时91% · 2,460 predictions · 13 days
12时87% · 2,357 predictions · 12 days
13时86% · 2,328 predictions · 12 days
14时84% · 2,574 predictions · 13 days
15时85% · 1,946 predictions · 12 days
16时86% · 1,324 predictions · 13 days
17时83% · 1,667 predictions · 13 days
18时84% · 2,643 predictions · 12 days
19时83% · 1,969 predictions · 12 days
20时83% · 1,833 predictions · 10 days
21时81% · 1,658 predictions · 10 days
22时82% · 1,661 predictions · 10 days
23时84% · 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: 2026年11月6日

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

公交车扎堆到站

Last 28 days, 2026年10月8日 to 2026年11月4日: 21 days counted.

2 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: 2026年10月8日, 2026年10月12日.

数值与解读

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

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

公交车扎堆到站
时段	已检查的配对	扎堆	间隔过长
清晨（凌晨4点至6点）	1,219	3% (35)	1% (17)
早高峰(上午 6 点至 9 点)	5,756	2% (94)	1% (67)
中午（上午9点至下午3点）	23,594	4% (827)	3% (622)
下午高峰(下午3点至6点)	7,947	5% (434)	5% (375)
晚间（晚上 6 点至 10 点）	12,656	4% (464)	3% (397)
夜间（晚上10点至凌晨4点）	6,274	1% (60)	1% (55)

测量方式 →How we got this number每条线路的扎堆和缓慢路段 →

这条路线最慢的路段

Slowest: CENTRE RIDEAU to du PORTAGE/AUBRY, 8.7 km/h actual against 13.9 km/h planned.

这条路线最慢的路段
起点	到	距离	计划速度	实际速度	已测量的行程	缓慢行程
CENTRE RIDEAU	du PORTAGE/AUBRY	2.4 km	13.9 km/h	8.7 km/h	1,240	44%
TERRASSES de la CHAUDIÈRE	de l'HÔTEL-de-VILLE/LAURIER	750 m	15.4 km/h	11.9 km/h	1,413	30%
du PORTAGE/AUBRY	EDDY/WELLINGTON	450 m	10.9 km/h	11.9 km/h	1,366	8%
MONTCALM/HANSON	TERRASSES de la CHAUDIÈRE	930 m	13.2 km/h	15.7 km/h	1,416	2%
Station de la CITÉ #2	Station PROMENADES #1	1.1 km	15.8 km/h	16.5 km/h	1,415	3%
STATION LORRAIN	Station LABROSSE #1	2.9 km	42.9 km/h	16.6 km/h	1,288	69%
de l'HÔTEL-de-VILLE/LAURIER	CENTRE RIDEAU	2.5 km	13.2 km/h	16.7 km/h	1,221	0%
EDDY/WELLINGTON	Station MONTCALM #3	960 m	16.5 km/h	17.4 km/h	1,368	3%

慢行程是指用时至少为计划时间的 1.5 倍。

测量方式 →

此线路附近的市政道路施工

渥太华市已发布的道路施工和活动封路信息，按靠近本线路路径来衡量。靠近不代表巴士一定绕行。请查看运营方自己发布的服务提醒。

道路施工
ALBERT between ELGIN and METCALFE
2026年10月29日 00:00 to 2027年1月26日 17:00
ALBERT lane reduction between ELGIN and METCALFE due to construction, from October 29th to January 26th.
市政府标明此项会影响公共交通。
about 0 m from the route
City record updated 2026年11月2日 12:44.
道路施工
Slater between Bay and Lyon
2026年10月30日 00:00 to 2026年11月6日 17:00
Slater lane reduction between Bay and Lyon due to construction, from November 2nd to 6th.
about 0 m from the route
City record updated 2026年10月30日 13:28.
道路施工
ALBERT at LYON
未发布日期
Albert and Lyon off-peak lane reductions at the intersection due to construction.
about 2 m from the route
City record updated 2026年9月9日 18:32.

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.

来源：渥太华市交通事件（道路施工和封闭）。包含根据渥太华市开放政府许可协议授权的信息。渥太华市表示，此列表仅尽力提供，可能不完整。渥太华市交通地图 ↗

此线路的取消班次

这些词是什么意思 →

6 partial-capture days not counted.

3 scheduled trips with counted cancellation notices from 10月8日周四 to 11月4日周三.

Not counted: 2 trips with qualifying later matching vehicle observations and 2 for trips not in that day’s timetable.

取消次数最多的时段: 5时 (1), 10时 (1), 13时 (1)

这条线路通常何时繁忙

依据 STO 公交车报告的载客水平，统计最近八周的数据。如果有读数的班次中至少一半达到站位或更拥挤，该时段就标为通常拥挤。

过去八周内,没有任何时段通常很拥挤。

这条线路通常何时繁忙	工作日	星期六	每周日
早上6点前	通常有座位14.2% of 374 trips	读数不足	读数不足
上午 6 点至 9 点	通常有座位17.8% of 863 trips	通常有座位1.2% of 170 trips	通常有座位0.7% of 146 trips
上午9点至下午3点	通常有座位25.9% of 2,885 trips	通常有座位12.2% of 362 trips	通常有座位5.7% of 335 trips
下午3点至6点	通常有座位40.2% of 1,228 trips	通常有座位23.1% of 208 trips	通常有座位9.7% of 196 trips
晚上 6 点至 10 点	通常有座位23.2% of 1,644 trips	通常有座位3.6% of 248 trips	通常有座位1.3% of 240 trips
晚上10点以后	通常有座位7.2% of 708 trips	通常有座位2.7% of 147 trips	通常有座位0% of 132 trips

Based on 56 computed days.

来源：STO 公开实时车辆数据中的载客状态。STO 根据每辆公交车的载重传感器设定该状态（有座位：满载率低于 60%，有站位：低于 90%，已满：高于 90%）。
每个行程在每个时段只计一次,按其报告的最高载客量计算。
空车报告不计入，因为旧记录无法区分空车和没有传感器的车。
某个时段至少要有 12 趟行程，且分布在至少 4 个不同的日子，才会显示任何内容。节假日按其所属的星期几计算。

打开历史、可靠性和线路分析

线路检查

How route 400 has been running

这是我们所知情况的简短摘要。如果我们无法回答某个问题，会明确说明。

结论

在这个有日期的样本中，运营方的预测通常与时刻表接近。

83 in 100 eligible predictions were within 5 minutes of the timetable · 64,037 predictions checked

预测样本量: 样本较大

Based on 64,037 eligible provider predictions over 22 measured days, from 2026年10月7日 to 2026年11月4日.

Updated 2026年11月5日 22:32

预测在哪些地点和时间反复出现差异?

这些是预测时间与时刻表之间反复出现的差异，不是独立测得的服务故障。它们使用与上述结果相同的合格预测，但按站点而不是按时段分组，所以两个列表不一定逐行一致。

目前还没有重复出现的预测差异时段达到数据门槛。

1 current notice affects this route

• Detour Route 400 South

各站预测差异

STATION LORRAIN
47 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,679 predictions over 25 days).
打开此站点
MONTCALM/WRIGHT
36 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,749 predictions over 25 days).
打开此站点
du PORTAGE/AUBRY
34 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,738 predictions over 25 days).
打开此站点
EDDY/WELLINGTON
31 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,748 predictions over 25 days).
打开此站点

这些是按路线给出的服务方预测，并与时刻表作了对比。它们显示的是某地某时重复出现的预测差异，不是实测到达时间，也不能说明原因。

查看每个行程和日期

展开一个时间段,可查看每个服务日、预定班次、数据缺口、观测到的公开车辆编号,以及本摘要背后的确切数字。

乘客想知道什么

现在有班次被取消吗？: 没有实时取消情况的答案STO’s live trip-update feed did not answer this check. That is a feed gap. It does not mean zero cancellations, and it is not proof of a cancellation. Open the evidence to see the schedule, retained explicit cancellation notices, and every labelled data gap.
排除数据缺口后，可能的未出车情况？: 10 of 1,036 checked trips need a closer look10 of 1,036 trips with enough public-feed evidence had no matching position over 7 days. 191 of 1,227 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
运营方的预测与时刻表有何不同?: At the 95th percentile, the predicted difference was 8.2 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.
运营方的预测意味着需要等多久？: 6.0 min average predicted wait0.9 min beyond the scheduled wait, based on 27,520 eligible predictions at 43 high-frequency stops over 16 days.

时刻表变更检查

已发布时刻表：变更前后

这是将当前保留的官方时刻表与上一个保留版本进行比较。时刻表变更说明的是原定计划，并不能证明某个班次确实运行过。

Current published schedule began 2026年11月3日

每份已发布时刻表中所选的服务日

我们会查看新时刻表开始后的第一个星期一，以及提前一周的星期一。所有数字都来自下方列出的、已保留的官方 GTFS 版本。

所选日期中，至少有一个日期采用了新增或取消的按日历日期安排的服务。请将其视为节假日或特别服务的情况，而不是普通工作日的增长。

之前

已核对的服务日期: 2026年11月2日

时刻表班次: 187
不同的预定站点: 43
已发布的不同路径: 4
已公布的服务时段: 4:45–0:45 next day

Operator calendar-date records: 1 added · 0 removed

数据源指纹: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

新时刻表

已核对的服务日期: 2026年11月9日

时刻表班次: 187
不同的预定站点: 43
已发布的不同路径: 4
已公布的服务时段: 4:45–0:45 next day

Operator calendar-date records: 1 added · 0 removed

数据源指纹: 64b436d79ab51a76 · 623ad8b0-ad29-4d70-b8e6-e594a396233e

变更后服务有改善吗？

我们会比较变更前后各14天内已确认的到站情况。只有变更前后两边都至少有7个服务日和200次到站记录时，我们才会发布比较结果。

Still collecting: before has 35,967 arrivals over 13 days; after has 3,901 arrivals over 2 days. No improvement or decline is claimed yet.

校验和可让任何人核实是哪份留存的时刻表得出这些数量。数量变化并不能说明原因、取消、运营方的决定或对乘客的影响。

如何评价这条线路: Rapibus 快速公交

我们将每个预定到达班次的最后一个合格服务方预测与官方时刻表进行比较。这些不是独立测量的到达时间。一项结果至少需要 200 条合格预测。这里采用面向乘客的目标：误差在 5 分钟内。

这些数据无法证明的事

公开数据源不提供可靠的乘客人数，也不提供乘客被错过的事件。缺少车辆位置本身，并不能证明班次已取消、未出车、提前折返，也不能说明原因。

查看定义、阈值和数据依据的顺序

官方实时数据：明确的取消、跳过的站点和当前有效的通知。
匹配的观测数据:与官方时刻表相关联的车辆位置和已确定的预测。
官方时刻表：计划的内容，与实际观测到的内容分开显示。
乘客和运营方的报告：这些是关于线路、时间和地点的线索，供进一步调查，本身不能作为数字证明。

初步结果,已公布的数据

预测与时刻表相比如何?

每个小时，我们都会把某个预定到站班次最后一次符合条件的运营方预测与时刻表进行比较。“5 分钟内”指的是这个预测差异，不是实际测得的到站时间，也不能证明公交车已经运行。

佐证时间段: 2026年10月7日 to 2026年11月4日

与时刻表相差不超过5分钟: 82.9%
已核查的合格预测: 64,037
有数据的工作日: 17
第95百分位预测延误: 8.2 min late

Patterns by hour (21)

Patterns by hour (21)
小时	准点	中位数	第95百分位	数据证据
00:00	88.4%	0.4 min late	6.6 min late	658 · 10 days
04:00	96.2%	0.1 min late	2 min late	52 · 7 days
05:00	95.0%	0.4 min late	3.9 min late	1,033 · 11 days
06:00	95.2%	0.5 min late	4.5 min late	1,475 · 11 days
07:00	86.1%	1.6 min late	6.6 min late	1,103 · 10 days
08:00	79.8%	2 min late	8.4 min late	1,365 · 11 days
09:00	86.5%	1.1 min late	7.2 min late	2,417 · 12 days
10:00	87.2%	1.2 min late	6.5 min late	1,987 · 11 days
11:00	90.8%	0.6 min late	5.5 min late	2,460 · 13 days
12:00	87.2%	1 min late	7.6 min late	2,357 · 12 days
13:00	85.8%	1.5 min late	7.7 min late	2,328 · 12 days
14:00	84.0%	1.4 min late	7.5 min late	2,574 · 13 days
15:00	85.4%	1.1 min late	8.7 min late	1,946 · 12 days
16:00	85.7%	1 min late	8.3 min late	1,324 · 13 days
17:00	82.7%	1.7 min late	7.4 min late	1,667 · 13 days
18:00	84.1%	1.5 min late	8 min late	2,643 · 12 days
19:00	83.2%	2.1 min late	7.6 min late	1,969 · 12 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

至少三个服务日内，还没有确认低于 70% 的重复模式。

有时刻表的巴士，但没有实时观测记录

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

23:0024 / 51 trips without a position52.9%
00:006 / 14 trips without a position57.1%
04:004 / 10 trips without a position60.0%
22:0022 / 56 trips without a position60.7%
20:0019 / 61 trips without a position68.9%
21:0017 / 56 trips without a position69.6%

这不是已确认的未发车。 缺少位置可能表示公交车被取消或漏班，也可能表示行程编号未分配，或运营方数据源有缺口。Otranspo 公布这一缺口，因为它对乘客很重要，同时我们会如实说明，不下定论。

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. 来源和局限.

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

November 4, 2026 · 187 trips in the retained timetable · retained notices; capture coverage unverified

In short: 148 with a matched position · 2 with no matching position (to investigate) · 37 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:63296008Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 5:46 a.m. EST; not actual start or end times.
05:15– 05:59
Trip sto:63296009Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 5:50 a.m. EST; not actual start or end times.
05:25– 06:09
Trip sto:63296010Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 6:06 a.m. EST; not actual start or end times.
05:30– 06:13
Trip sto:63290293Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 6:12 a.m. EST; not actual start or end times.
05:35– 06:21
Trip sto:63296011Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 6:20 a.m. EST; not actual start or end times.
05:40– 06:26
Trip sto:63296012Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 6:20 a.m. EST; not actual start or end times.
05:45– 06:28
Trip sto:63294599Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 6:25 a.m. EST; not actual start or end times.
05:45– 06:31
Trip sto:63296013Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 6:29 a.m. EST; not actual start or end times.
05:49– 06:35
Trip sto:63296014Vehicle position matchedFirst / last feed position: 5:48 a.m. EST / 6:31 a.m. EST; not actual start or end times.
05:55– 06:41
Trip sto:63296098Vehicle position matchedFirst / last feed position: 5:55 a.m. EST / 6:38 a.m. EST; not actual start or end times.

· Open all evidence for this day

STO 线路 400: Rapibus 400

Did the scheduled service run?

Scheduled trips with cancellation notices

Trips needing investigation

What does the evidence show?

The hours we have evidence for

What about time of day?

公交车扎堆到站

这条路线最慢的路段

此线路附近的市政道路施工

此线路的取消班次

最近取消的班次

这条线路通常何时繁忙

预测在哪些地点和时间反复出现差异?

查看每个行程和日期

乘客想知道什么

每份已发布时刻表中所选的服务日

之前

新时刻表

变更后服务有改善吗？

预测与时刻表相比如何?

Trips scheduled that day

Did the scheduled service run?

Scheduled trips with cancellation notices

Trips needing investigation

What does the evidence show?

The hours we have evidence for

What about time of day?

公交车扎堆到站

这条路线最慢的路段

此线路附近的市政道路施工

此线路的取消班次

最近取消的班次

这条线路通常何时繁忙

预测在哪些地点和时间反复出现差异?

查看每个行程和日期

乘客想知道什么

每份已发布时刻表中所选的服务日

之前

新时刻表

变更后服务有改善吗？

预测与时刻表相比如何?

Trips scheduled that day