两者 · 日历覆盖完整 · 已冻结的发布内容 · monthly-service-report-settled-v1-days-v15
2026年8月 · both operators
78.4% of 公交车到站预测 were within five minutes. 星期六 were the weak spot.
Partial data · 28 of 31 days
Every calendar day is accounted for: 28 of 31 days were measured and the remaining days, if any, have a recorded explanation. Publication status is shown separately below.
Every day in 八月
Share within five minutes, each day- Weekday
- 星期六
- Sunday or holidaySunday / holiday
- Partial data部分
8月7 至 9日 and 26 are not counted (too few records from either operator). 8月13 至 23日 and 28 至 30 count only the operator with enough records.
Where routes land
The largest group, 60 routes, sits at 80 to 100%. 3 routes fall below 60%.- Under 20%0
- 20 to 40%0
- 40 to 60%3
- 60 至 80%31
- 80 to 100%60
94 routes had enough data to rank. 43 more are listed separately: too little data or special service.
Every prediction, counted
- 五分钟内
- 2,734,141
- Early or late by more
- 752,483
Outside five minutes covers early and late. Missed trips are counted separately, in Cancellations.
Ask about this report
Ask about this report我们如何测量
We check the arrival predictions OC Transpo and STO publish, once each trip has finished, and count how many landed within five minutes, early or late.
This tells you how far to trust the countdown on your screen. It is not an independent check of where the bus really was.
Full method, coverage and original editionFull evidence for this report
Findings by remedy, comparisons, every listed route, coverage, cancellations and how to cite this edition.
日历覆盖完整 · 已冻结的发布内容
两者 · 2026年8月
决策者简报
请用本页向运营商提出有针对性的问题。这些数字说明的是已保存的公交车预测证据，不是对实际到站次数或所有预定班次的审计统计。
待查看的发现
12 of 12 routes with a supported finding point to test more scheduled running time. Review the route-hours and supporting samples below before changing service.
向运营方提出的请求
请提供被标记线路时段的到站或发车记录、对应的时刻表版本，以及运营方面的说明。在采用任何修正方案之前，请先测试对成本、车队、人力和换乘的影响。
数据依据与局限
3,486,624 final eligible bus predictions across 148 routes in this scorecard. Regional calendar coverage: 28 of 31 days with figures. Physical arrival times were not independently verified.
需要记录在案的问题
- 运营方的车辆和调度记录是否证实了这里显示的线路时段规律？
- 哪些按时刻表安排的行程没有运行?公开的取消通知有多完整?
- 可以公开哪些时刻表、车辆位置或到达数据,以验证公交车结果并使铁路报告成为可能?
CSV 导出整月数据，包括两家运营方、覆盖范围和方法。运营方选择器会改变评分卡、取消小计和线路发现；每日序列和日历覆盖范围以及与其他月份的比较仍为全区域数据。
How 整个网络 is doing
这些指标把反复出现的延误与运营方到达预测的波动区分开来。它们可为规划人员和运营人员提供可探讨的问题，但不能确定原因，也不能证明公共汽车何时到达。每个数字都显示其线路时段样本。
Measured over 2,500 route-hours. 134 more were observed too thinly to count, and are excluded rather than assumed good.
排班
如果多次出现预测晚点，可能说明时刻表值得检查。在决定是否调整运行时间之前，请先查看实际到达和发车记录。
- 谁能解决
- 服务规划人员
- 费用
- 在车队、人力、恢复和换乘的影响测试完成之前，成本暂不可知。
与时刻表接近的预测
81.8%
线路小时中，符合条件的到站预测中位数早于实际不到一分钟，且晚于实际不到三分钟。
多次预计晚点的线路时段
399of 2,500
路线小时数：符合条件的到达预测中位数至少晚点三分钟。请对照实际运营记录检查运行时间。
有提前预测的线路小时数
55of 2,500
线路-小时中，符合条件的到站预测中位数至少提前一分钟的部分。这并不能证明公交车提前发车。
典型预测延误
4min
在被标记的线路时段中，预测延误的典型中位数。这不是可直接加到时刻表上的经过验证的数值。
运营
到站预测差异很大，需要进行运营审查。交通状况、调度、上车和时刻表设计都可能有影响。仅凭这些预测，无法确定原因或解决办法。
- 谁能解决
- 运营部门，通常还有道路本身
- 费用
- 在查明运营原因并确定补救办法之前，费用暂不可用。
预测间隔低于二十分钟
97.4%
第95百分位的合格预测值比中位数晚不到二十分钟的线路-小时。
预测误差大的线路时段
64of 2,500
第95百分位的合格预测比中位数晚至少二十分钟的线路时段。需要调查原因。
典型预测偏差
24.3min
在被标记的线路时段中,第 95 百分位符合条件的预计值与中位数之间的典型差距。
按天查看
此每日序列涵盖两家运营方,即使上方选择了其中一家也是如此。每根柱代表一个日历日。如果一个月只报告一个百分比,就无法看出这个月是一直处于平均水平,还是除了糟糕的一周之外都不错。
Bars are scaled between 67% and 86%. 周末日期已标出。服务水平和所含线路可能与工作日不同。 每根柱子下面的细线表示：与本月测量最完整的一天相比，本站点在当天实际测量了多少。线短，说明上方的百分比所依据的数据要少得多。
打开每日数据表
| 服务日期 | 数据依据状态 | 五分钟内 | 符合条件的运营方预测 | 相对覆盖率 | 天气 |
|---|---|---|---|---|---|
| 2026年8月1日 | 已测量 | 69.9% | 173,385 | 65% of the best-measured day | 没有值得注意的天气 |
| 2026年8月2日 | 已测量 | 75.1% | 147,613 | 55% of the best-measured day | Rain 36.1 mm |
| 2026年8月3日 | 已测量 | 77% | 171,272 | 64% of the best-measured day | Rain 15.6 mm |
| 2026年8月4日 | 已测量 | 76.9% | 230,039 | 86% of the best-measured day | 没有值得注意的天气 |
| 2026年8月5日 | 已测量 | 75.1% | 267,740 | 100% of the best-measured day | 没有值得注意的天气 |
| 2026年8月6日 | 已测量 | 78.1% | 268,471 | 100% of the best-measured day | 没有值得注意的天气 |
| 2026年8月7日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | — | 0 | — | 没有值得注意的天气 |
| 2026年8月8日 | 无数据；缺口已说明原因 | — | — | — | Gusts to 61 km/h, Visibility down to 0.2 km |
| 2026年8月9日 | 无数据；缺口已说明原因 | — | — | — | 没有值得注意的天气 |
| 2026年8月10日 | 已测量 | 79.9% | 94,564 | 35% of the best-measured day | Rain 23.5 mm, Gusts to 89 km/h |
| 2026年8月11日 | 已测量 | 79.7% | 197,336 | 74% of the best-measured day | 没有值得注意的天气 |
| 2026年8月12日 | 已测量 | 79.2% | 178,340 | 66% of the best-measured day | Rain 21.9 mm, Gusts to 107 km/h |
| 2026年8月13日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 77.6% | 264,619 | — | Visibility down to 0.2 km |
| 2026年8月14日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 84.2% | 89,175 | — | 没有值得注意的天气 |
| 2026年8月15日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 74.6% | 43,333 | — | 没有值得注意的天气 |
| 2026年8月16日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 86.1% | 43,051 | — | 没有值得注意的天气 |
| 2026年8月17日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 86% | 82,612 | — | 没有值得注意的天气 |
| 2026年8月18日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 80% | 77,859 | — | 没有值得注意的天气 |
| 2026年8月19日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 82.9% | 66,916 | — | 没有值得注意的天气 |
| 2026年8月20日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 81.5% | 88,508 | — | 没有值得注意的天气 |
| 2026年8月21日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 82.4% | 89,850 | — | 没有值得注意的天气 |
| 2026年8月22日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 79.9% | 42,913 | — | 没有值得注意的天气 |
| 2026年8月23日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 87.3% | 27,406 | — | 没有值得注意的天气 |
| 2026年8月24日 | 已测量 | 79.3% | 153,972 | 57% of the best-measured day | 没有值得注意的天气 |
| 2026年8月25日 | 已测量 | 81.8% | 224,970 | 84% of the best-measured day | Visibility down to 0.4 km |
| 2026年8月26日 | 无数据；缺口已说明原因 | — | — | — | 没有值得注意的天气 |
| 2026年8月27日 | 已测量 | 83.4% | 132,906 | 50% of the best-measured day | 没有值得注意的天气 |
| 2026年8月28日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 77% | 25,198 | — | 没有值得注意的天气 |
| 2026年8月29日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 65.2% | 126,206 | — | 没有值得注意的天气 |
| 2026年8月30日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 84.8% | 39,079 | — | 没有值得注意的天气 |
| 2026年8月31日 | 已测量 | 81.5% | 139,291 | 52% of the best-measured day | Visibility down to 0.2 km |
打开每日数据表
| 服务日期 | 数据依据状态 | 五分钟内 | 符合条件的运营方预测 | 相对覆盖率 | 天气 |
|---|---|---|---|---|---|
| 2026年8月1日 | 已测量 | 69.9% | 173,385 | 65% of the best-measured day | 没有值得注意的天气 |
| 2026年8月2日 | 已测量 | 75.1% | 147,613 | 55% of the best-measured day | Rain 36.1 mm |
| 2026年8月3日 | 已测量 | 77% | 171,272 | 64% of the best-measured day | Rain 15.6 mm |
| 2026年8月4日 | 已测量 | 76.9% | 230,039 | 86% of the best-measured day | 没有值得注意的天气 |
| 2026年8月5日 | 已测量 | 75.1% | 267,740 | 100% of the best-measured day | 没有值得注意的天气 |
| 2026年8月6日 | 已测量 | 78.1% | 268,471 | 100% of the best-measured day | 没有值得注意的天气 |
| 2026年8月7日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | — | 0 | — | 没有值得注意的天气 |
| 2026年8月8日 | 无数据；缺口已说明原因 | — | — | — | Gusts to 61 km/h, Visibility down to 0.2 km |
| 2026年8月9日 | 无数据；缺口已说明原因 | — | — | — | 没有值得注意的天气 |
| 2026年8月10日 | 已测量 | 79.9% | 94,564 | 35% of the best-measured day | Rain 23.5 mm, Gusts to 89 km/h |
| 2026年8月11日 | 已测量 | 79.7% | 197,336 | 74% of the best-measured day | 没有值得注意的天气 |
| 2026年8月12日 | 已测量 | 79.2% | 178,340 | 66% of the best-measured day | Rain 21.9 mm, Gusts to 107 km/h |
| 2026年8月13日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 77.6% | 264,619 | — | Visibility down to 0.2 km |
| 2026年8月14日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 84.2% | 89,175 | — | 没有值得注意的天气 |
| 2026年8月15日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 74.6% | 43,333 | — | 没有值得注意的天气 |
| 2026年8月16日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 86.1% | 43,051 | — | 没有值得注意的天气 |
| 2026年8月17日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 86% | 82,612 | — | 没有值得注意的天气 |
| 2026年8月18日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 80% | 77,859 | — | 没有值得注意的天气 |
| 2026年8月19日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 82.9% | 66,916 | — | 没有值得注意的天气 |
| 2026年8月20日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 81.5% | 88,508 | — | 没有值得注意的天气 |
| 2026年8月21日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 82.4% | 89,850 | — | 没有值得注意的天气 |
| 2026年8月22日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 79.9% | 42,913 | — | 没有值得注意的天气 |
| 2026年8月23日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 87.3% | 27,406 | — | 没有值得注意的天气 |
| 2026年8月24日 | 已测量 | 79.3% | 153,972 | 57% of the best-measured day | 没有值得注意的天气 |
| 2026年8月25日 | 已测量 | 81.8% | 224,970 | 84% of the best-measured day | Visibility down to 0.4 km |
| 2026年8月26日 | 无数据；缺口已说明原因 | — | — | — | 没有值得注意的天气 |
| 2026年8月27日 | 已测量 | 83.4% | 132,906 | 50% of the best-measured day | 没有值得注意的天气 |
| 2026年8月28日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 77% | 25,198 | — | 没有值得注意的天气 |
| 2026年8月29日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 65.2% | 126,206 | — | 没有值得注意的天气 |
| 2026年8月30日 | 部分采集；缺少一家运营商，此数字不代表整个网络 | 84.8% | 39,079 | — | 没有值得注意的天气 |
| 2026年8月31日 | 已测量 | 81.5% | 139,291 | 52% of the best-measured day | Visibility down to 0.2 km |
Bars are scaled between 67% and 86%. 周末日期已标出。服务水平和所含线路可能与工作日不同。 每根柱子下面的细线表示：与本月测量最完整的一天相比，本站点在当天实际测量了多少。线短，说明上方的百分比所依据的数据要少得多。
- 最佳日期
- 2026年8月27日 · 83.4%
- 最差的一天
- 2026年8月1日 · 69.9%
- Weather that day: 没有值得注意的天气.
显示天气仅供参考。本页的任何数字都不会因天气而调整、豁免或评分。
来源:加拿大环境与气候变化部,渥太华国际机场的每日和每小时气候数据(气候编号 6106001)。 气候日从午夜到午夜,按当地标准时间计算,所以夏季可能与运营日相差一小时。 历史气候数据 ↗
应改变什么
根据本月符合条件的提供方预测计算得出，并按所影响的样本量排序。每一行都会说明数据源显示了什么、发生在何时，以及哪个运营方可以进行审核。
Test more scheduled running time
Test additional scheduled running time for these hours. This pattern supports the scenario, but fleet, labour, recovery, transfer and cost effects require operator validation.
1210:00 to 23:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
57,797 eligible predictions · 13 hours of the day · typically 4 min late · 95th-percentile prediction 14 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
712:00 to 00:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
54,088 eligible predictions · 12 hours of the day · typically 4 min late · 95th-percentile prediction 15 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
611:00 to 23:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
52,897 eligible predictions · 12 hours of the day · typically 4 min late · 95th-percentile prediction 14 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
1807:00 to 00:00
The median final prediction here is more than 5 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
35,142 eligible predictions · 17 hours of the day · typically 5 min late · 95th-percentile prediction 15 min later than the median · Unvalidated scenario to verify: about 5 min more scheduled running time, derived from the prediction median
2011:00 to 00:00
The median final prediction here is more than 5 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
24,434 eligible predictions · 13 hours of the day · typically 5 min late · 95th-percentile prediction 16 min later than the median · Unvalidated scenario to verify: about 5 min more scheduled running time, derived from the prediction median
1415:00 to 00:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
24,650 eligible predictions · 9 hours of the day · typically 4 min late · 95th-percentile prediction 14 min later than the median · Unvalidated scenario to verify: about 5 min more scheduled running time, derived from the prediction median
1409:00 to 14:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
21,261 eligible predictions · 5 hours of the day · typically 4 min late · 95th-percentile prediction 14 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
1112:00 to 16:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
18,551 eligible predictions · 4 hours of the day · typically 4 min late · 95th-percentile prediction 16 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
1913:00 to 22:00
The median final prediction here is more than 5 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
14,669 eligible predictions · 9 hours of the day · typically 5 min late · 95th-percentile prediction 11 min later than the median · Unvalidated scenario to verify: about 5 min more scheduled running time, derived from the prediction median
6307:00 to 14:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
16,007 eligible predictions · 7 hours of the day · typically 4 min late · 95th-percentile prediction 10 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
7011:00 to 16:00
The median final prediction here is more than 5 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
14,666 eligible predictions · 5 hours of the day · typically 5 min late · 95th-percentile prediction 18 min later than the median · Unvalidated scenario to verify: about 5 min more scheduled running time, derived from the prediction median
6315:00 to 22:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
15,629 eligible predictions · 7 hours of the day · typically 4 min late · 95th-percentile prediction 11 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
5710:00 to 18:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
16,804 eligible predictions · 8 hours of the day · typically 4 min late · 95th-percentile prediction 8 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
5112:00 to 18:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
13,246 eligible predictions · 6 hours of the day · typically 4 min late · 95th-percentile prediction 10 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
5719:00 to 23:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
7,708 eligible predictions · 4 hours of the day · typically 4 min late · 95th-percentile prediction 14 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
2005:00 to 10:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
8,288 eligible predictions · 5 hours of the day · typically 4 min late · 95th-percentile prediction 6 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
1120:00 to 23:00
The median final prediction here is more than 3 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
8,343 eligible predictions · 3 hours of the day · typically 3 min late · 95th-percentile prediction 16 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
1117:00 to 19:00
The median final prediction here is more than 3 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
7,193 eligible predictions · 2 hours of the day · typically 3 min late · 95th-percentile prediction 17 min later than the median · Unvalidated scenario to verify: about 3 min more scheduled running time, derived from the prediction median
5707:00 to 09:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
5,620 eligible predictions · 2 hours of the day · typically 4 min late · 95th-percentile prediction 8 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
7021:00 to 23:00
The median final prediction here is more than 3 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
4,401 eligible predictions · 2 hours of the day · typically 3 min late · 95th-percentile prediction 17 min later than the median · Unvalidated scenario to verify: about 3 min more scheduled running time, derived from the prediction median
5107:00 to 09:00
The median final prediction here is more than 3 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
4,225 eligible predictions · 2 hours of the day · typically 3 min late · 95th-percentile prediction 9 min later than the median · Unvalidated scenario to verify: about 3 min more scheduled running time, derived from the prediction median
700:00
The median final prediction here is more than 3 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
2,398 eligible predictions · 1 hours of the day · typically 3 min late · 95th-percentile prediction 18 min later than the median · Unvalidated scenario to verify: about 3 min more scheduled running time, derived from the prediction median
1909:00
The median final prediction here is more than 3 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
2,048 eligible predictions · 1 hours of the day · typically 3 min late · 95th-percentile prediction 9 min later than the median · Unvalidated scenario to verify: about 3 min more scheduled running time, derived from the prediction median
5123:00
The median final prediction here is more than 4 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
576 eligible predictions · 1 hours of the day · typically 4 min late · 95th-percentile prediction 5 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
1800:00
The median final prediction here is more than 3 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
516 eligible predictions · 1 hours of the day · typically 3 min late · 95th-percentile prediction 6 min later than the median · Unvalidated scenario to verify: about 3 min more scheduled running time, derived from the prediction median
Something other than the timetable
The prediction spread does not support a running-time change by itself. Test traffic, boarding load, crossings, terminal dispatch, vehicle assignment and operator availability against operational records; those cause data are not available here.
2014:00 to 18:00
The 95th-percentile prediction here is about 27 minutes later than the median prediction. Actual arrival spread is not measured.
7,218 eligible predictions · 4 hours of the day · typically 6 min late · 95th-percentile prediction 27 min later than the median
1416:00 to 18:00
The 95th-percentile prediction here is about 22 minutes later than the median prediction. Actual arrival spread is not measured.
6,902 eligible predictions · 2 hours of the day · typically 6 min late · 95th-percentile prediction 22 min later than the median
615:00
The 95th-percentile prediction here is about 23 minutes later than the median prediction. Actual arrival spread is not measured.
5,016 eligible predictions · 1 hours of the day · typically 4 min late · 95th-percentile prediction 23 min later than the median
7014:00
The 95th-percentile prediction here is about 20 minutes later than the median prediction. Actual arrival spread is not measured.
2,617 eligible predictions · 1 hours of the day · typically 5 min late · 95th-percentile prediction 20 min later than the median
5718:00 to 20:00
The 95th-percentile prediction here is about 25 minutes later than the median prediction. Actual arrival spread is not measured.
3,813 eligible predictions · 2 hours of the day · typically 3 min late · 95th-percentile prediction 25 min later than the median
1116:00
The 95th-percentile prediction here is about 24 minutes later than the median prediction. Actual arrival spread is not measured.
3,572 eligible predictions · 1 hours of the day · typically 3 min late · 95th-percentile prediction 24 min later than the median
1817:00
The 95th-percentile prediction here is about 22 minutes later than the median prediction. Actual arrival spread is not measured.
1,828 eligible predictions · 1 hours of the day · typically 3 min late · 95th-percentile prediction 22 min later than the median
7013:00
At 13:00, 50 of predictions are within five minutes of the timetable, against 72 the rest of the day. This identifies a prediction pattern, not a confirmed service failure.
2,526 eligible predictions · 50% against 72% the rest of the day
1821:00
At 21:00, 32 of predictions are within five minutes of the timetable, against 56 the rest of the day. This identifies a prediction pattern, not a confirmed service failure.
2,209 eligible predictions · 32% against 56% the rest of the day
1915:00
At 15:00, 40 of predictions are within five minutes of the timetable, against 65 the rest of the day. This identifies a prediction pattern, not a confirmed service failure.
1,734 eligible predictions · 40% against 65% the rest of the day
Something other than the timetable, at night
The late-hour pattern does not establish a cause. Test terminal holds, prior-trip lateness, vehicle assignment, operator availability and any overnight traffic event against operational records; those records are not available here.
622:00
The 95th-percentile prediction here is about 21 minutes later than the median prediction. Actual arrival spread is not measured.
2,865 eligible predictions · 1 hours of the day · typically 4 min late · 95th-percentile prediction 21 min later than the median
2023:00
The 95th-percentile prediction here is about 24 minutes later than the median prediction. Actual arrival spread is not measured.
1,356 eligible predictions · 1 hours of the day · typically 5 min late · 95th-percentile prediction 24 min later than the median
5122:00
The 95th-percentile prediction here is about 24 minutes later than the median prediction. Actual arrival spread is not measured.
1,601 eligible predictions · 1 hours of the day · typically 1 min late · 95th-percentile prediction 24 min later than the median
2000:00
The 95th-percentile prediction here is about 23 minutes later than the median prediction. Actual arrival spread is not measured.
409 eligible predictions · 1 hours of the day · typically 1 min late · 95th-percentile prediction 23 min later than the median
601:00
The 95th-percentile prediction here is about 45 minutes later than the median prediction. Actual arrival spread is not measured.
724 eligible predictions · 1 hours of the day · 95th-percentile prediction 45 min later than the median
此处未涵盖
- 预定班次是否真的运行。运营方的预测不能证明班次已运行。这需要另外的数据来证明。
- 符合条件的运营商预测是否显示高频线路的发车间隔均匀或扎堆。这是在最近一段滚动时间内测量的,无法为这个已结束的月份重新计算。
与其他月份对比 · 两家运营商
上个月
2026年7月 was not measured by this site.
匹配预测对比
这里将符合条件的最终服务方预测与计划时间进行比较。它不能核实实际到站情况,不能证明原因,也不能说明服务是否相当。
预期服务日使用已存档的线路日历和例外情况。没有预定服务的日期不计入。如果缺少来源记录,则不显示对比。
上一个完整的日历月 · 2026-07-01–2026-07-31
常用线路和工作日权重 · prediction-comparison-v2
当前
符合条件的原始比率: —
匹配对比率: —
— / — 符合条件的预测/在预定阈值内的预测
样本数量未公布；缺失的值不代表零。 缺少对比时段
基准
符合条件的原始比率: —
匹配对比率: —
— / — 符合条件的预测/在预定阈值内的预测
样本数量未公布；缺失的值不代表零。 缺少对比时段
已匹配的差异暂不公布: 缺少对比时段
各线路覆盖情况 · —; 匹配的线路日 · 此方法未使用; 已省略的线路日期 · —; 常用权重 · —
对于这项被拒绝的比较,空的证据列表尚未经过评估。 缺少对比时段
时刻表数据版本: — / —
去年同月
2025年8月 was not measured by this site.
匹配预测对比
这里将符合条件的最终服务方预测与计划时间进行比较。它不能核实实际到站情况,不能证明原因,也不能说明服务是否相当。
预期服务日使用已存档的线路日历和例外情况。没有预定服务的日期不计入。如果缺少来源记录,则不显示对比。
去年同一个完整的日历月 · 2025-08-01–2025-08-31
常用线路和工作日权重 · prediction-comparison-v2
当前
符合条件的原始比率: —
匹配对比率: —
— / — 符合条件的预测/在预定阈值内的预测
样本数量未公布；缺失的值不代表零。 缺少对比时段
基准
符合条件的原始比率: —
匹配对比率: —
— / — 符合条件的预测/在预定阈值内的预测
样本数量未公布；缺失的值不代表零。 缺少对比时段
已匹配的差异暂不公布: 缺少对比时段
各线路覆盖情况 · —; 匹配的线路日 · 此方法未使用; 已省略的线路日期 · —; 常用权重 · —
对于这项被拒绝的比较,空的证据列表尚未经过评估。 缺少对比时段
时刻表数据版本: — / —
Furthest from the timetable in 2026年8月
The routes with the lowest share of eligible final predictions within five minutes of the timetable. A low figure does not establish the cause; inspect the route evidence before drawing conclusions.
- 1852.7%37,924 eligible trip-stop predictions · 15 of 28 days
- 2054.8%35,528 eligible trip-stop predictions · 15 of 28 days
- 1458.9%61,812 eligible trip-stop predictions · 15 of 28 days
- 6362%41,693 eligible trip-stop predictions · 15 of 28 days
- 1962.7%30,211 eligible trip-stop predictions · 15 of 28 days
- 763%88,616 eligible trip-stop predictions · 15 of 28 days
- 1264.6%84,307 eligible trip-stop predictions · 15 of 28 days
- 665.1%82,081 eligible trip-stop predictions · 15 of 28 days
- 6265.2%35,258 eligible trip-stop predictions · 15 of 28 days
- 5766.5%41,290 eligible trip-stop predictions · 15 of 28 days
Closest to the timetable in 2026年8月
The routes with the highest share of eligible final provider predictions within five minutes of the timetable. All use the same route class, evidence threshold and period. This is a relative ranking, not an operator target or measured arrival rate.
- 15395.4%2,779 eligible trip-stop predictions · 15 of 28 days
- 69STO94.9%11,804 eligible trip-stop predictions · 16 of 28 days
- 75STO94.6%21,345 eligible trip-stop predictions · 16 of 28 days
- 9394.1%14,140 eligible trip-stop predictions · 15 of 28 days
- 6793.5%13,092 eligible trip-stop predictions · 15 of 28 days
- 77STO93.5%8,311 eligible trip-stop predictions · 16 of 28 days
- 19793.4%2,251 eligible trip-stop predictions · 15 of 28 days
- 4593.3%9,752 eligible trip-stop predictions · 15 of 28 days
- 78STO93%13,701 eligible trip-stop predictions · 16 of 28 days
- 72STO92.3%2,750 eligible trip-stop predictions · 16 of 28 days
有预测样本，但本月数据不足
本月,这些路线有合格服务方预测的天数不到有预测数据天数的一半。这些预测计入上面的整体网络数字,但由于样本只覆盖本月的一部分,这些路线不列入排名。
- 32STO72.7%30,326 eligible trip-stop predictions · 13 of 28 days
- 35STO85.3%19,557 eligible trip-stop predictions · 11 of 28 days
- 7361.6%15,331 eligible trip-stop predictions · 11 of 28 days
- 62STO92.8%14,338 eligible trip-stop predictions · 11 of 28 days
- 6079.2%12,950 eligible trip-stop predictions · 13 of 28 days
- 1584.5%11,593 eligible trip-stop predictions · 11 of 28 days
- 9278.6%10,917 eligible trip-stop predictions · 11 of 28 days
- 68STO90.6%10,160 eligible trip-stop predictions · 11 of 28 days
- 73STO90.1%8,598 eligible trip-stop predictions · 11 of 28 days
- 4383.6%8,126 eligible trip-stop predictions · 11 of 28 days
- 95STO72.9%8,090 eligible trip-stop predictions · 11 of 28 days
- 1368.9%6,606 eligible trip-stop predictions · 12 of 28 days
- 200STO85.5%6,568 eligible trip-stop predictions · 11 of 28 days
- 87STO90.2%6,444 eligible trip-stop predictions · 11 of 28 days
- 56STO70%6,143 eligible trip-stop predictions · 11 of 28 days
- 85STO83.5%6,085 eligible trip-stop predictions · 11 of 28 days
- 36STO84.4%5,893 eligible trip-stop predictions · 11 of 28 days
- 40STO78.9%5,166 eligible trip-stop predictions · 11 of 28 days
- 45STO63.7%4,667 eligible trip-stop predictions · 11 of 28 days
- 100STO89.6%4,562 eligible trip-stop predictions · 11 of 28 days
- 93STO85.5%4,020 eligible trip-stop predictions · 11 of 28 days
- 41STO77.3%3,817 eligible trip-stop predictions · 10 of 28 days
- 3276.5%3,663 eligible trip-stop predictions · 11 of 28 days
- 25STO72.1%3,648 eligible trip-stop predictions · 11 of 28 days
- 58STO94.3%3,533 eligible trip-stop predictions · 11 of 28 days
- 6669.4%3,307 eligible trip-stop predictions · 11 of 28 days
- 79STO95.4%3,247 eligible trip-stop predictions · 11 of 28 days
- 26STO79.5%2,891 eligible trip-stop predictions · 11 of 28 days
- 27STO76.6%2,822 eligible trip-stop predictions · 10 of 28 days
- 50STO88.9%2,786 eligible trip-stop predictions · 11 of 28 days
- 1768.4%2,737 eligible trip-stop predictions · 11 of 28 days
- 23STO73.3%2,642 eligible trip-stop predictions · 11 of 28 days
- 11776.8%2,485 eligible trip-stop predictions · 11 of 28 days
- 19885.5%2,481 eligible trip-stop predictions · 11 of 28 days
- 2360.3%2,410 eligible trip-stop predictions · 11 of 28 days
- 2692.9%2,348 eligible trip-stop predictions · 11 of 28 days
- 47STO64.4%2,225 eligible trip-stop predictions · 10 of 28 days
- 28STO80.8%1,900 eligible trip-stop predictions · 10 of 28 days
- 29STO69%1,806 eligible trip-stop predictions · 10 of 28 days
- 18788.5%1,450 eligible trip-stop predictions · 11 of 28 days
- 18STO89.1%1,154 eligible trip-stop predictions · 11 of 28 days
- 98STO99.3%1,066 eligible trip-stop predictions · 7 of 28 days
- 20STO70%1,028 eligible trip-stop predictions · 10 of 28 days
已保存的取消记录
这些是已保存的运营方记录，显示某个行程已取消或已删除。对同一行程和同一通知类型的重复更新只计一次。一个行程可以同时有两种类型。之后的更新可能会改变其状态。这与时刻表对比是分开的。
- 保留的记录
- 230
- 渥太华 · OC Transpo
- 182
- 加蒂诺 · STO
- 48
Records were saved on 4 service dates in this month. Daily archive coverage has not been verified, so this is not a complete monthly cancellation total. Earliest saved record in the archive: 2026年8月28日.
仅限公交车结果:O-Train 在哪里?
这些数字不包括 O-Train。本月度成绩单是根据从运营方公开数据源保存的公交车到站时间预测计算得出的。
Otranspo 也会追踪公交车的实时位置、班次更新和取消通知,以便为乘客提供指引。本报告使用范围较窄的历史数据:每个预定公交车停靠记录的最后一条合格服务方预测,并与时刻表对比。这些记录尚未与车辆实际到站情况进行独立核实。
本报告使用的公开数据源没有提供O-Train的到达预测或列车实时位置。要做可比较的轨道交通评分，需要有列车观测数据或预测数据，并附有记录在案的方法。仅凭已发布的列车时刻表无法做到。
日历覆盖完整
Every calendar day is accounted for: 28 of 31 days were measured and the remaining days, if any, have a recorded explanation. Publication status is shown separately below.
发布状态
已冻结的发布内容
Published on 2026年10月4日 15:13 under monthly-service-report-settled-v1-days-v15. This version is stored as a snapshot and will not be recomputed when the method or source data changes.
本月数据来自按 settled-route-histogram-v1 方法生成的线路日数据：每个趟次、每个站点、每个多伦多服务日期，只采用一条最终的提供方预测。较新的 v2 版本会将每个趟次实例分开保存，但无法用于本月，因为本月记录的预测不含趟次实例标识。出于同样的原因，本月不提供与其他月份的比较。
This edition replaces the one published under monthly-service-report-settled-v1-days-v14. Only partly captured days changed: an operator's day captured at under a quarter of its busiest day, or overlapped for an hour or more by a timetable mismatch in its live feed, is now left out of the totals and marked partly captured instead of counted as service. The earlier edition is kept unchanged. 早期版本（CSV）
这些数据落后的天数
- 已测量的天数
- 28 of 31
- 没有符合条件的已结算预测的天数
- 3
- 没有记录的天数
- 0
没有数据的日期
- 2026年8月8日当天没有符合条件的运营方预测已结算，因此没有可统计的内容。
- 2026年8月9日当天没有符合条件的运营方预测已结算，因此没有可统计的内容。
- 2026年8月26日当天没有符合条件的运营方预测已结算，因此没有可统计的内容。
仅限公交车。这里使用的数据源不提供 O-Train 的到站预测或列车实时位置。本页所有数字均不含轨道交通。
引用本页
OTranspo, service report for 2026年8月, settled 2026年10月4日 15:13. https://otranspo.ca/zh-Hans/insights/reports/2026-08
- 数据结算日期
- 2026年10月4日 15:13
- 方法
- monthly-service-report-settled-v1-days-v15
下载文件与本页包含相同的覆盖范围说明和相同的注意事项。