兩者 · 日曆涵蓋範圍完整 · 已凍結的發布內容 · 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 8月
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%
路線時段中，符合資格的到站預測中位數，早到不足一分鐘，且晚到不足三分鐘。
多次預測late的路線時段
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日 下午3: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日 下午3:13. https://otranspo.ca/zh-Hant/insights/reports/2026-08
- 數字已結算
- 2026年10月4日 下午3:13
- 方法
- monthly-service-report-settled-v1-days-v15
下載檔案附有與本頁相同的涵蓋範圍說明和相同的注意事項。