Scheduled service and available evidence
Evidence period: 2026年10月29日 – 2026年11月4日
1
Trips in the published timetable marked cancelled without qualifying later matching vehicle observations in our archive. This does not prove the trip did not operate. Trips with any notice: 1.
0
0 of 80 trips with a usable feed window (0%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
80 with position · 0 to investigate · 25 excluded · 105 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 2026年11月5日 上午1:59.
0 of 2 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.
25 scheduled trips were excluded from the position check for feed or identity gaps.
Published position coverage: 80 / 105 (76.2%). This is not a delivered-service rate. 7 service days in this source.
Timetables retained before the service day: 7 / 7 requested days · 0 missing days.
Historical calculation: 2026年11月5日 上午1:08
Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.
Predictions against the timetable
74.1%
of eligible provider predictions were within five minutes of the timetable.
Share of predictions within five minutes of the timetable. Only eligible hours are shown; an absent hour does not mean zero.
These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.
Calculated: 2026年11月5日
6 partial-capture days not counted.
8 hourly cohorts meet the thresholds of 30 predictions and 5 service days. Hourly thresholds are assessed separately from the route-wide aggregate.
Improvement or decline requires comparable periods. This single result cannot establish a trend.
Last 28 days, 2026年10月8日 to 2026年11月4日: 20 days counted.
2 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: 2026年10月8日, 2026年10月12日.
4% of back-to-back buses on this route arrived bunched together: 235 of 6,598 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
3% of pairs (218) had a long gap: more than 1.75 times the planned wait between them.
| 時段 | 已檢查的配對 | 擠成一團 | 間隔過長 |
|---|---|---|---|
| 清晨（上午 4 時至 6 時） | 86 | 0% (0) | 0% (0) |
| 早上繁忙時段(上午 6 時至 9 時) | 2,575 | 0% (7) | 1% (23) |
| 下午繁忙時段(下午3時至6時) | 3,389 | 6% (215) | 5% (160) |
| 晚間（下午 6 時至 10 時） | 548 | 2% (13) | 6% (35) |
Slowest: CENTRE RIDEAU to KENT / SPARKS, 6.5 km/h actual against 12.1 km/h planned.
| 起點 | 目的地 | 距離 | 計劃速度 | 實際速度 | 已量測的行程 | 緩慢班次 |
|---|---|---|---|---|---|---|
| CENTRE RIDEAU | KENT / SPARKS | 1.2 km | 12.1 km/h | 6.5 km/h | 99 | 61% |
| de l'OASIS/de la CITÉ | HÔPITAL DE GATINEAU | 590 m | 17.8 km/h | 10.3 km/h | 70 | 29% |
| de l'HÔPITAL/de l'OASIS | de la CITÉ/la VÉRENDRYE OUEST | 560 m | 8.6 km/h | 10.4 km/h | 108 | 0% |
| KENT / SPARKS | PLACE d'ACCUEIL est | 1.1 km | 10.6 km/h | 11.3 km/h | 113 | 3% |
| PLACE d'ACCUEIL ouest | CENTRE RIDEAU | 2.5 km | 12 km/h | 12.8 km/h | 68 | 1% |
| GRÉBER/de POINTE-GATINEAU | d'ORLÉANS/GRÉBER | 1.6 km | 15.2 km/h | 15.3 km/h | 121 | 3% |
| ERNEST-GABOURY/SAINT-RENÉ OUEST | de l'HÔPITAL/de l'OASIS | 2.3 km | 18 km/h | 17.8 km/h | 119 | 3% |
| ERNEST-GABOURY/SAINT-RENÉ OUEST | d'ORLÉANS/GRÉBER | 1.3 km | 16.5 km/h | 18.1 km/h | 90 | 0% |
慢速行程是指所需時間至少為計畫時間的 1.5 倍。
渥太華市已公布的道路施工和活動封路，以靠近此路線行駛路徑來計算。靠近不代表巴士已改道。請查看營運單位自己的服務通知。
道路施工
ALBERT between ELGIN and METCALFE
2026年10月29日 上午12:00 to 2027年1月26日 下午5:00
ALBERT lane reduction between ELGIN and METCALFE due to construction, from October 29th to January 26th.
市政府標示此項會影響公共交通。
about 0 m from the route
City record updated 2026年11月2日 下午12:44.
道路施工
Slater between Bay and Lyon
2026年10月30日 上午12:00 to 2026年11月6日 下午5:00
Slater lane reduction between Bay and Lyon due to construction, from November 2nd to 6th.
about 0 m from the route
City record updated 2026年10月30日 下午1:28.
道路施工
ALBERT at LYON
未公布日期
Albert and Lyon off-peak lane reductions at the intersection due to construction.
about 2 m from the route
City record updated 2026年9月9日 下午6:32.
A route counts as near when its timetable path passes within 40 m of the City’s mapped closure; a stop counts when it is within 75 m.
來源：渥太華市交通事件（道路施工和封閉）。內含根據開放政府授權（Open Government Licence，City of Ottawa）提供的資訊。市政府表示，此清單已盡力提供，但可能不完整。 渥太華市交通地圖 ↗
6 partial-capture days not counted.
1 scheduled trips with counted cancellation notices from 10月8日週四 to 11月4日週三.
Not counted: 1 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
取消班次最多的時段: 下午3時 (1)
只有當 STO 對該班次發出的服務通知列明原因時，才會顯示原因。
未到(沒看到巴士,也沒有通知),過去 7 天:在我們能查核的班次中,沒有任何一班。
根據 STO 巴士回報的載客量，涵蓋過去八週。如果有讀數的班次中，至少有一半達到站立或更擠，該時段就會標示為通常擁擠。
| 此路線通常何時較擁擠 | 平日 | 星期六 | 逢星期日 |
|---|---|---|---|
| 上午6點前 | 通常有座位6.3% of 64 trips | 讀數不足 | 讀數不足 |
| 上午 6 時至 9 時 | 通常很擠62.5% of 269 trips | 讀數不足 | 讀數不足 |
| 上午 9 時至下午 3 時 | 讀數不足 | 讀數不足 | 讀數不足 |
| 下午 3 時至 6 時 | 通常有座位42.6% of 312 trips | 讀數不足 | 讀數不足 |
| 晚上 6 時至 10 時 | 通常有座位4.8% of 62 trips | 讀數不足 | 讀數不足 |
| 晚上 10 點後 | 讀數不足 | 讀數不足 | 讀數不足 |
Based on 55 computed days.
結論
Median provider predictions are 3.6 to 5.1 min later than the timetable in 2 hours of the day.
Predictions near the start are about 9 min later than the timetable, with a similar difference near the end. This does not establish the cause.
17:00 has 49% of predictions within five minutes of the timetable, against 78% the rest of the day.
Next investigation: test terminal recovery and the preceding trip against operational records. Predictions alone do not establish the cause.
| What | 時間 | 已測量 | Scenario or next investigation |
|---|---|---|---|
| ProblemPredictions later than timetable | 15:00 · 17:00 | 3.6 min late · 5.1 min late | Recovery time at the terminal |
| ProblemOne hour has a lower prediction match | 17:00 | 49% | Operations, not the timetable |
路線檢查
這是我們所知內容的簡短摘要。如果無法回答某個問題，我們會說明。
重點結論
營運機構的預測常與時刻表不同；實際到站時間沒有獨立量測。
74 in 100 eligible predictions were within 5 minutes of the timetable · 10,175 predictions checked預測樣本數: 樣本較大
Based on 10,175 eligible provider predictions over 17 measured days, from 2026年10月6日 to 2026年11月3日.
Updated 2026年11月5日 上午1:32
這些是預測與班表之間反覆出現的差異，並非獨立測得的服務失誤。它們使用與上方結果相同的合格預測，但按站點而非時段分組，因此兩份清單不一定逐行相符。
目前沒有與此路線相符的官方通知。
各站的預測差異
50 in 100 eligible predictions differed from the timetable by more than 5 minutes (162 predictions over 18 days).
開啟此站牌48 in 100 eligible predictions differed from the timetable by more than 5 minutes (160 predictions over 18 days).
開啟此站牌46 in 100 eligible predictions differed from the timetable by more than 5 minutes (161 predictions over 18 days).
開啟此站牌45 in 100 eligible predictions differed from the timetable by more than 5 minutes (161 predictions over 18 days).
開啟此站牌這些是各路線業者提供的預測,並與時刻表比較。它們顯示某個地點和時段反覆出現的預測差異,不是實測的到站時間,也不能說明原因。
打開一個時段,即可查看每個服務日、預定班次、資料空檔、已觀察到的公開車輛編號,以及此摘要背後的確切數字。
時刻表變更檢查
此頁面比較目前保留的官方時刻表與先前保留的版本。時刻表變更只說明原本的計劃,不能證明某個班次已經行駛。
Current published schedule began 2026年11月3日
我們會檢查新時刻表開始後的第一個星期一，以及一週前的星期一。所有數字都來自下列保留的官方 GTFS 版本。
所選日期中，至少有一個日期有新增或取消的特定日期服務。請將此視為假日或特別服務的情況，而不是平日一般的服務增加。
已核對的服務日期: 2026年11月2日
Operator calendar-date records: 1 added · 0 removed
資料串流指紋: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74
已核對的服務日期: 2026年11月9日
Operator calendar-date records: 1 added · 0 removed
資料串流指紋: 64b436d79ab51a76 · 623ad8b0-ad29-4d70-b8e6-e594a396233e
我們會比較變更前後各 14 天已確認的到站紀錄。只有在變更前後兩段時間都至少有 7 個服務日和 200 次到站紀錄時，我們才會公布比較結果。
Still collecting: before has 5,169 arrivals over 10 days; after has 805 arrivals over 2 days. No improvement or decline is claimed yet.
校驗碼可讓任何人核對，是哪一份留存的時刻表產生這些數量。數量有變動，並不能說明原因、取消、營運單位的決定或對乘客的影響。
我們把每個預定到達班次的最後一筆合資格業者預測，與官方時刻表比較。這些不是獨立量測的到達時間。結果至少需要 200 筆合資格預測。這裡採用乘客角度的目標：誤差在 5 分鐘內。
公開資料來源沒有提供可靠的乘客人數，也沒有提供漏載乘客的事件。缺少車輛位置，本身並不能證明班次取消、未出車、中途折返或其原因。
暫定結果，已公布的數據
每個小時都會把某班預定到站的最後一次合格業者預測與時刻表比較。「5 分鐘內」是指預測與時刻表的差距，不是實際量到的到站時間，也不能證明巴士有行駛。
佐證期間: 2026年10月6日 to 2026年11月3日
| 小時 | 準點 | 中位數 | 第 95 百分位 | 證據 |
|---|---|---|---|---|
| 05:00 | 98.9% | 0.7 min late | 3.6 min late | 281 · 8 days |
| 06:00 | 97.1% | 0.6 min late | 3.6 min late | 731 · 8 days |
| 07:00 | 93.6% | 0.7 min late | 5.6 min late | 749 · 7 days |
| 08:00 | 70.5% | 3 min late | 10 min late | 465 · 8 days |
| 15:00 | 63.6% | 3.6 min late | 9 min late | 653 · 9 days |
| 16:00 | 61.8% | 2.8 min late | 19.4 min late | 991 · 10 days |
| 17:00 | 49.0% | 5.1 min late | 20.6 min late | 1,034 · 9 days |
| 18:00 | 86.2% | 1 min late | 13.4 min late | 463 · 8 days |
3 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
80 / 105 scheduled trips published at least one position across 5 service days (76.2%).
這不是已確認的未發車。 找不到車輛位置，可能是班次取消或漏班，也可能是班次編號未指派，或是營運單位的資料來源出現缺口。Otranspo 公布這項缺口，因為這對乘客很重要，同時也會如實處理，不作過度推論。
Prediction check: the last eligible provider prediction no earlier than ten minutes before the scheduled arrival, counted once per trip, stop and scheduled Toronto calendar date. It is compared with the timetable, not an independently measured arrival. Trip-position check: the timetable kept before each service day, matched to recorded positions. Exact IDs are preferred; an OC timetable suffix is matched only to one trip on the same route and date with an overlapping time window. Missing timetables, ambiguous matches and feed gaps stay labelled; they are not confirmed no-shows. 來源與限制.
Dated service
The timetable, notices and what the live feed says are shown apart. Seeing a bus on the map does not prove you can board it.
November 4, 2026 · 21 trips in the retained timetable · retained notices; capture coverage unverified
In short: 19 with a matched position · 0 with no matching position (to investigate) · 2 with an unknown outcome.