兩者 · 日曆涵蓋範圍完整 · 已凍結的發布內容 · monthly-service-report-settled-v1-days-v15
2026年9月 · both operators
77% of 巴士到站預測 were within five minutes. 星期六 were the weak spot.
Every day in 9月
Share within five minutes, each day- Weekday
- 星期六
- Sunday or holidaySunday / holiday
- Partial data部分
9月3日 is not counted (too few records from either operator). 9月2日 and 4 至 6 count only the operator with enough records.
Where routes land
The largest group, 69 routes, sits at 80 to 100%. 9 routes fall below 60%.- Under 20%0
- 20 to 40%0
- 40 to 60%9
- 60 至 80%62
- 80 to 100%69
140 routes had enough data to rank.
Every prediction, counted
- 五分鐘內
- 6,185,355
- Early or late by more
- 1,845,442
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年9月
決策者簡報
請利用本頁向營運商提出具體問題。這些數字描述的是已儲存的巴士預測證據，並非對實際到站次數或所有預定班次的審核計數。
待查證的發現
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.
向營運單位提出的要求
請提供被標記路線時段的到站或調度紀錄、對應的時刻表版本，以及營運上的說明。在採用任何修正方案前，請先測試成本、車隊、人力和轉乘方面的影響。
數據證據與限制
8,030,797 final eligible bus predictions across 148 routes in this scorecard. Regional calendar coverage: 30 of 30 days with figures. Physical arrival times were not independently verified.
紀錄中的問題
- 營運單位的車輛和調度紀錄，是否證實此處顯示的路線時段模式？
- 哪些預定行程沒有行駛?公開的取消通知有多完整?
- 可以公開哪些時刻表、車輛位置或到站資料,以驗證巴士結果並使鐵路報告成為可能?
CSV 會匯出整個月的資料,包括兩個營運單位、覆蓋範圍和方法。營運單位選擇器會改變評分表、取消小計和路線結果。每日數列和日曆覆蓋範圍,以及與其他月份的比較,仍然以整個地區為準。
How 整個路網 is doing
這些指標可區分重複出現的延誤,以及營運單位到站預測的變動。它們可為規劃人員和營運人員提供問題方向,但不能確定原因,也不能證明公車實際何時到達。每項數字都會顯示其路線時段的樣本數。
Measured over 2,822 route-hours. 52 more were observed too thinly to count, and are excluded rather than assumed good.
排班
預測一再延遲，可能表示這個時刻表值得檢討。在決定是否要調整行駛時間之前，請先查核實際到達和發車的記錄。
- 誰能解決
- 服務規劃人員
- 費用
- 在車輛、人力、回收和轉乘影響經過測試前，成本無法提供。
與時刻表接近的預測
79%
路線時段中，符合資格的到站預測中位數，早到不足一分鐘，且晚到不足三分鐘。
多次預測late的路線時段
534of 2,822
符合條件的到站預測中位數至少晚三分鐘的路線時段。請對照實際營運記錄，檢視行車時間。
有提早預測的路線時數
58of 2,822
路線小時數中，符合條件的到站預測中位數至少提早一分鐘。這不能證明巴士提早發車。
一般預測延誤
4min
被標記路線時段中預測延誤的典型中位數;這不是可加到時刻表上的已驗證數值。
營運
到站預測差異很大，需要進行營運檢討。交通、調度、上下車和時刻表設計都可能有影響。光靠這些預測，無法找出原因或解決辦法。
- 誰能解決
- 營運部門，通常也包括道路本身
- 費用
- 在確定營運原因和補救方法之前,無法提供費用。
預測間隔不足二十分鐘
98.8%
第95百分位的合格預測，比中位數晚不到二十分鐘的路線時段。
預測落差大的路線時段
34of 2,822
第95百分位的合格預測時間比中位數晚至少二十分鐘的路線時段。需要調查原因。
一般預測差距
23min
在被標記的路線時段中，第 95 百分位的合格預測與中位數之間的一般差距。
逐日
此每日系列涵蓋兩個營運單位,即使上方已選擇其中一個。每個長條代表一個日曆日。若一個月只以單一百分比表示,就無法知道該月是整體表現平均,還是除了某一個糟糕的星期之外都很好。
Bars are scaled between 63% and 86%. 週末日期已標示。服務水準和涵蓋的路線可能與平日不同。 每根長條下方的細線，表示本網站當天實際量測到的資料量，並與當月量測最完整的一天相比。線條短，代表上方的百分比所依據的資料少得多。
開啟逐日資料表
| 服務日期 | 數據證據狀態 | 五分鐘內 | 符合條件的營運單位預測 | 相對涵蓋率 | 天氣 |
|---|---|---|---|---|---|
| 2026年9月1日 | 已測量 | 78.8% | 149,964 | 41% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月2日 | 只擷取到部分資料；少了一個營運單位，這個數字不代表整個網絡 | 81.1% | 77,114 | — | Rain 29.1 mm, Visibility down to 0.8 km |
| 2026年9月3日 | 只擷取到部分資料；少了一個營運單位，這個數字不代表整個網絡 | — | 0 | — | Visibility down to 0.2 km |
| 2026年9月4日 | 只擷取到部分資料；少了一個營運單位，這個數字不代表整個網絡 | 78.7% | 81,375 | — | 沒有值得注意的天氣 |
| 2026年9月5日 | 只擷取到部分資料；少了一個營運單位，這個數字不代表整個網絡 | 81.3% | 43,558 | — | 沒有值得注意的天氣 |
| 2026年9月6日 | 只擷取到部分資料；少了一個營運單位，這個數字不代表整個網絡 | 85.1% | 43,142 | — | 沒有值得注意的天氣 |
| 2026年9月7日 | 已測量 | 83.5% | 183,398 | 50% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月8日 | 已測量 | 76% | 361,305 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月9日 | 已測量 | 74.1% | 362,596 | 99% of the best-measured day | Rain 19.6 mm |
| 2026年9月10日 | 已測量 | 74.2% | 360,549 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月11日 | 已測量 | 78.9% | 365,971 | 100% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月12日 | 已測量 | 66.4% | 234,160 | 64% of the best-measured day | Visibility down to 0.8 km |
| 2026年9月13日 | 已測量 | 75.6% | 189,557 | 52% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月14日 | 已測量 | 80.6% | 361,665 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月15日 | 已測量 | 77.4% | 359,355 | 98% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月16日 | 已測量 | 76.8% | 365,074 | 100% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月17日 | 已測量 | 76.1% | 363,752 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月18日 | 已測量 | 80.2% | 360,767 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月19日 | 已測量 | 69.1% | 233,527 | 64% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月20日 | 已測量 | 74.9% | 206,301 | 56% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月21日 | 已測量 | 81.1% | 360,349 | 98% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月22日 | 已測量 | 76.5% | 361,553 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月23日 | 已測量 | 76% | 360,784 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月24日 | 已測量 | 74.9% | 363,439 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月25日 | 已測量 | 78.2% | 358,753 | 98% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月26日 | 已測量 | 65.5% | 231,998 | 63% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月27日 | 已測量 | 74.9% | 205,422 | 56% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月28日 | 已測量 | 82.3% | 360,289 | 98% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月29日 | 已測量 | 78.2% | 362,074 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月30日 | 已測量 | 83.6% | 363,006 | 99% of the best-measured day | 沒有值得注意的天氣 |
開啟逐日資料表
| 服務日期 | 數據證據狀態 | 五分鐘內 | 符合條件的營運單位預測 | 相對涵蓋率 | 天氣 |
|---|---|---|---|---|---|
| 2026年9月1日 | 已測量 | 78.8% | 149,964 | 41% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月2日 | 只擷取到部分資料；少了一個營運單位，這個數字不代表整個網絡 | 81.1% | 77,114 | — | Rain 29.1 mm, Visibility down to 0.8 km |
| 2026年9月3日 | 只擷取到部分資料；少了一個營運單位，這個數字不代表整個網絡 | — | 0 | — | Visibility down to 0.2 km |
| 2026年9月4日 | 只擷取到部分資料；少了一個營運單位，這個數字不代表整個網絡 | 78.7% | 81,375 | — | 沒有值得注意的天氣 |
| 2026年9月5日 | 只擷取到部分資料；少了一個營運單位，這個數字不代表整個網絡 | 81.3% | 43,558 | — | 沒有值得注意的天氣 |
| 2026年9月6日 | 只擷取到部分資料；少了一個營運單位，這個數字不代表整個網絡 | 85.1% | 43,142 | — | 沒有值得注意的天氣 |
| 2026年9月7日 | 已測量 | 83.5% | 183,398 | 50% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月8日 | 已測量 | 76% | 361,305 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月9日 | 已測量 | 74.1% | 362,596 | 99% of the best-measured day | Rain 19.6 mm |
| 2026年9月10日 | 已測量 | 74.2% | 360,549 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月11日 | 已測量 | 78.9% | 365,971 | 100% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月12日 | 已測量 | 66.4% | 234,160 | 64% of the best-measured day | Visibility down to 0.8 km |
| 2026年9月13日 | 已測量 | 75.6% | 189,557 | 52% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月14日 | 已測量 | 80.6% | 361,665 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月15日 | 已測量 | 77.4% | 359,355 | 98% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月16日 | 已測量 | 76.8% | 365,074 | 100% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月17日 | 已測量 | 76.1% | 363,752 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月18日 | 已測量 | 80.2% | 360,767 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月19日 | 已測量 | 69.1% | 233,527 | 64% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月20日 | 已測量 | 74.9% | 206,301 | 56% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月21日 | 已測量 | 81.1% | 360,349 | 98% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月22日 | 已測量 | 76.5% | 361,553 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月23日 | 已測量 | 76% | 360,784 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月24日 | 已測量 | 74.9% | 363,439 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月25日 | 已測量 | 78.2% | 358,753 | 98% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月26日 | 已測量 | 65.5% | 231,998 | 63% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月27日 | 已測量 | 74.9% | 205,422 | 56% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月28日 | 已測量 | 82.3% | 360,289 | 98% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月29日 | 已測量 | 78.2% | 362,074 | 99% of the best-measured day | 沒有值得注意的天氣 |
| 2026年9月30日 | 已測量 | 83.6% | 363,006 | 99% of the best-measured day | 沒有值得注意的天氣 |
Bars are scaled between 63% and 86%. 週末日期已標示。服務水準和涵蓋的路線可能與平日不同。 每根長條下方的細線，表示本網站當天實際量測到的資料量，並與當月量測最完整的一天相比。線條短，代表上方的百分比所依據的資料少得多。
- 最佳日子
- 2026年9月30日 · 83.6%
- 最差的一天
- 2026年9月26日 · 65.5%
- 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.
708: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.
159,721 eligible predictions · 15 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
1214: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.
84,779 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 4 min more scheduled running time, derived from the prediction median
1114: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.
67,816 eligible predictions · 8 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
1909: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.
55,912 eligible predictions · 13 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
2014: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.
43,993 eligible predictions · 10 hours of the day · typically 4 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
1208:00 to 13: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.
53,876 eligible predictions · 5 hours of the day · typically 3 min late · 95th-percentile prediction 12 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
5314:00 to 19: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.
40,569 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
7014: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.
45,043 eligible predictions · 5 hours of the day · typically 3 min late · 95th-percentile prediction 11 min later than the median · Unvalidated scenario to verify: about 3 min more scheduled running time, derived from the prediction median
59STO14:00 to 20: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.
38,299 eligible predictions · 6 hours of the day · typically 4 min late · 95th-percentile prediction 9 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
2414: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.
31,913 eligible predictions · 4 hours of the day · typically 4 min late · 95th-percentile prediction 12 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
1812: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.
30,271 eligible predictions · 6 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
5612:00 to 18:00
The median final prediction here is more than 6 minutes later than the timetable. Test whether scheduled running time explains this; actual arrivals and the cause are not established.
19,749 eligible predictions · 6 hours of the day · typically 6 min late · 95th-percentile prediction 15 min later than the median · Unvalidated scenario to verify: about 6 min more scheduled running time, derived from the prediction median
1108:00 to 11: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.
30,307 eligible predictions · 3 hours of the day · typically 4 min late · 95th-percentile prediction 12 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
52STO14:00 to 21: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.
21,834 eligible predictions · 7 hours of the day · typically 5 min late · 95th-percentile prediction 17 min later than the median · Unvalidated scenario to verify: about 5 min more scheduled running time, derived from the prediction median
5308:00 to 11: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.
22,103 eligible predictions · 3 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
5608:00 to 11: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.
12,753 eligible predictions · 3 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
1808: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.
9,684 eligible predictions · 2 hours of the day · typically 4 min late · 95th-percentile prediction 12 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
1819:00 to 21: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.
10,634 eligible predictions · 2 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
52STO07: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.
9,186 eligible predictions · 3 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
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.
9,943 eligible predictions · 2 hours of the day · typically 3 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
2408: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,476 eligible predictions · 1 hours of the day · typically 3 min late · 95th-percentile prediction 11 min later than the median · Unvalidated scenario to verify: about 3 min more scheduled running time, derived from the prediction median
5312: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.
5,548 eligible predictions · 1 hours of the day · typically 3 min late · 95th-percentile prediction 13 min later than the median · Unvalidated scenario to verify: about 3 min more scheduled running time, derived from the prediction median
59STO09: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.
5,182 eligible predictions · 1 hours of the day · typically 3 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
2008: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.
4,338 eligible predictions · 1 hours of the day · typically 4 min late · 95th-percentile prediction 12 min later than the median · Unvalidated scenario to verify: about 4 min more scheduled running time, derived from the prediction median
2422: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.
3,414 eligible predictions · 1 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
1822: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,421 eligible predictions · 1 hours of the day · typically 3 min late · 95th-percentile prediction 11 min later than the median · Unvalidated scenario to verify: about 3 min more scheduled running time, derived from the prediction median
52STO12: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.
3,109 eligible predictions · 1 hours of the day · typically 3 min late · 95th-percentile prediction 12 min later than the median · Unvalidated scenario to verify: about 3 min more scheduled running time, derived from the prediction median
5619: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.
1,812 eligible predictions · 1 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
2000: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.
747 eligible predictions · 1 hours of the day · typically 3 min late · 95th-percentile prediction 10 min later than the median · Unvalidated scenario to verify: about 3 min more scheduled running time, derived from the prediction median
52STO00: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.
270 eligible predictions · 1 hours of the day · typically 5 min late · 95th-percentile prediction 8 min later than the median · Unvalidated scenario to verify: about 5 min more scheduled running time, derived from the prediction median
5601: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.
174 eligible predictions · 1 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
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.
2016:00 to 18:00
The 95th-percentile prediction here is about 23 minutes later than the median prediction. Actual arrival spread is not measured.
8,684 eligible predictions · 2 hours of the day · typically 5 min late · 95th-percentile prediction 23 min later than the median
2416:00
The 95th-percentile prediction here is about 26 minutes later than the median prediction. Actual arrival spread is not measured.
7,822 eligible predictions · 1 hours of the day · typically 5 min late · 95th-percentile prediction 26 min later than the median
52STO16:00 to 18:00
The 95th-percentile prediction here is about 21 minutes later than the median prediction. Actual arrival spread is not measured.
6,044 eligible predictions · 2 hours of the day · typically 6 min late · 95th-percentile prediction 21 min later than the median
59STO16:00
At 16:00, 45 of predictions are within five minutes of the timetable, against 74 the rest of the day. This identifies a prediction pattern, not a confirmed service failure.
7,518 eligible predictions · 45% against 74% the rest of the day
2415:00
At 15:00, 50 of predictions are within five minutes of the timetable, against 75 the rest of the day. This identifies a prediction pattern, not a confirmed service failure.
8,333 eligible predictions · 50% against 75% the rest of the day
5308:00
At 08: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.
8,386 eligible predictions · 50% against 72% the rest of the day
5615:00
At 15:00, 29 of predictions are within five minutes of the timetable, against 68 the rest of the day. This identifies a prediction pattern, not a confirmed service failure.
4,599 eligible predictions · 29% against 68% the rest of the day
7015:00
At 15:00, 49 of predictions are within five minutes of the timetable, against 73 the rest of the day. This identifies a prediction pattern, not a confirmed service failure.
7,148 eligible predictions · 49% against 73% the rest of the day
此處未涵蓋
- 預定班次是否真的有行駛。業者預測無法證明班次已執行。這需要另外的數據來證明。
- 符合條件的供應商預測是否顯示班距平均或有扎堆現象，適用於班次頻密的路線。這是以近期滾動時段測量，無法為這個已結束的月份重新計算。
與其他月份比較 · 兩家營運商
上個月
2026年8月: 78.4% of eligible provider predictions within five minutes
28 of 31 calendar days with evidence · 3,486,624 eligible provider predictions · 148 routes
配對預測比較
這是將符合條件的最終業者預測與預定時間作比較。它不能驗證實際到站情況,不能證明原因,也不能確定服務相當。
預期服務日使用已存檔的路線日曆和例外情況。沒有預定服務的日期不計算在內;如果缺少來源紀錄,就不會提供比較。
上一個完整的曆月 · 2026-08-01–2026-08-31
常用的路線和平日權重 · prediction-comparison-v2
目前
符合條件的原始比率: —
配對比較比率: —
— / — 符合資格的預測/在預定時間門檻內的預測
樣本數量不公開。缺少的數值不等於零。 缺少時刻表的來源紀錄
基準
符合條件的原始比率: —
配對比較比率: —
— / — 符合資格的預測/在預定時間門檻內的預測
樣本數量不公開。缺少的數值不等於零。 缺少時刻表的來源紀錄
相符的差異不予公布: 缺少時刻表的來源紀錄
各路線涵蓋範圍 · —; 已配對的路線日數 · 此方法未使用; 已略過的路線日數 · —; 常用權重 · —
此次被拒絕的比較，其空白的證據清單尚未經過評估。 缺少時刻表的來源紀錄
時刻表資料版本: — / —
去年同月
2025年9月 was not measured by this site.
配對預測比較
這是將符合條件的最終業者預測與預定時間作比較。它不能驗證實際到站情況,不能證明原因,也不能確定服務相當。
預期服務日使用已存檔的路線日曆和例外情況。沒有預定服務的日期不計算在內;如果缺少來源紀錄,就不會提供比較。
去年同一個完整曆月 · 2025-09-01–2025-09-30
常用的路線和平日權重 · prediction-comparison-v2
目前
符合條件的原始比率: —
配對比較比率: —
— / — 符合資格的預測/在預定時間門檻內的預測
樣本數量不公開。缺少的數值不等於零。 缺少比較期間
基準
符合條件的原始比率: —
配對比較比率: —
— / — 符合資格的預測/在預定時間門檻內的預測
樣本數量不公開。缺少的數值不等於零。 缺少比較期間
相符的差異不予公布: 缺少比較期間
各路線涵蓋範圍 · —; 已配對的路線日數 · 此方法未使用; 已略過的路線日數 · —; 常用權重 · —
此次被拒絕的比較，其空白的證據清單尚未經過評估。 缺少比較期間
時刻表資料版本: — / —
Furthest from the timetable in 2026年9月
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.
- 45STO44.8%11,025 eligible trip-stop predictions · 19 of 30 days
- 1751.1%7,874 eligible trip-stop predictions · 19 of 30 days
- 3254.2%10,006 eligible trip-stop predictions · 19 of 30 days
- 1355.1%16,145 eligible trip-stop predictions · 19 of 30 days
- 29STO56.7%4,286 eligible trip-stop predictions · 19 of 30 days
- 2357.2%6,159 eligible trip-stop predictions · 19 of 30 days
- 5657.7%55,181 eligible trip-stop predictions · 26 of 30 days
- 23STO58.6%6,745 eligible trip-stop predictions · 19 of 30 days
- 56STO58.6%13,523 eligible trip-stop predictions · 19 of 30 days
- 47STO60.6%5,665 eligible trip-stop predictions · 19 of 30 days
Closest to the timetable in 2026年9月
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.
- 98STO97.8%2,882 eligible trip-stop predictions · 19 of 30 days
- 8496.2%2,347 eligible trip-stop predictions · 19 of 30 days
- 9395%33,174 eligible trip-stop predictions · 26 of 30 days
- 75STO94.2%47,988 eligible trip-stop predictions · 28 of 30 days
- 17393.5%45,546 eligible trip-stop predictions · 26 of 30 days
- 77STO93.2%18,301 eligible trip-stop predictions · 28 of 30 days
- 72STO92.1%5,888 eligible trip-stop predictions · 28 of 30 days
- 79STO91.9%8,135 eligible trip-stop predictions · 19 of 30 days
- 19791.7%6,487 eligible trip-stop predictions · 26 of 30 days
- 6791.6%31,030 eligible trip-stop predictions · 26 of 30 days
已儲存的取消紀錄
這些是已儲存的營運單位記錄,顯示某個行程已被取消或刪除。同一行程和同一通知類型的重複更新只算一次。一個行程可以同時有兩種類型。之後的更新可能會改變其狀態。這與時刻表比較是分開的。
- 保留的記錄
- 1,673
- 渥太華 · OC Transpo
- 1,439
- 加蒂諾 · STO
- 234
Records were saved on 30 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: 30 of 30 days were measured and the remaining days, if any, have a recorded explanation. Publication status is shown separately below.
發布狀態
已凍結的發布內容
Published on 2026年10月4日 下午5:14 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. The cancellation count was recounted. The rule is the same: a retained notice for a trip in the published timetable counts only when no qualifying later matching vehicle observations were retained (matching observations covering at least ten minutes after the recorded notice time). Notices with those observations are excluded; the observations do not establish that a notice was withdrawn or that the whole trip was completed. Partly captured operator-days are now also left out of the totals. The earlier edition counted 1,688 cancellations and is kept unchanged. 較早版本（CSV）
這些數字落後的天數
- 已量測的天數
- 30 of 30
- 沒有符合條件的已結算預測的日子
- 0
- 沒有紀錄的日子
- 0
僅限巴士。此處使用的資料來源不提供 O-Train 到站預測或列車即時位置。本頁所有數字均不包含軌道運輸。
引用本頁
OTranspo, service report for 2026年9月, settled 2026年10月4日 下午5:14. https://otranspo.ca/zh-Hant/insights/reports/2026-09
- 數字已結算
- 2026年10月4日 下午5:14
- 方法
- monthly-service-report-settled-v1-days-v15
下載檔案附有與本頁相同的涵蓋範圍說明和相同的注意事項。