Scheduled service and available evidence
Evidence period: 2026年10月28日 – 2026年11月3日
—
No retained notice returned; this does not prove zero cancellations.
0
0 of 30 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.
30 with position · 0 to investigate · 0 excluded · 30 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 2026年11月4日 下午2:23.
0 of 4 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.
0 scheduled trips were excluded from the position check for feed or identity gaps.
Published position coverage: 30 / 30 (100%). 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月4日 下午1:37
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
No comparable percentage published
This service purpose needs a different method. A general percentage could give a misleading picture.
These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.
Calculated: 2026年11月4日
2 partial-capture days not counted.
The general hourly comparison is not suitable for this service purpose. Source records remain available.
Improvement or decline requires comparable periods. This single result cannot establish a trend.
Last 28 days, 2026年10月7日 to 2026年11月3日: 26 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月15日.
4% of back-to-back buses on this route arrived bunched together: 8 of 189 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
4% of pairs (7) had a long gap: more than 1.75 times the planned wait between them.
| 時段 | 已檢查的配對 | 擠成一團 | 間隔過長 |
|---|---|---|---|
| 早上繁忙時段(上午 6 時至 9 時) | 105 | 0% (0) | 6% (6) |
| 下午繁忙時段(下午3時至6時) | 84 | 10% (8) | 1% (1) |
Not enough trips yet to measure speed between timepoints (20 trips needed for each segment).
此數據如何計算 →渥太華市已公布的道路施工和活動封路，以靠近此路線行駛路徑來計算。靠近不代表巴士已改道。請查看營運單位自己的服務通知。
道路施工
YORK between DALHOUSIE and CUMBERLAND
2026年10月30日 上午7:00 to 2026年11月13日 下午5:00
YORK closed between DALHOUSIE and CUMBERLAND due to construction, from November 2nd to 13th. Access for local traffic maintained.
about 0 m from the route
City record updated 2026年10月30日 上午6:56.
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）提供的資訊。市政府表示，此清單已盡力提供，但可能不完整。 渥太華市交通地圖 ↗
2 partial-capture days not counted.
7 scheduled trips with counted cancellation notices from 10月7日週三 to 11月3日週二.
Not counted: 0 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
取消班次最多的時段: 下午3時 (5), 上午8時 (2)
OC Transpo 不提供單一班次的原因，因此不顯示。
未到(沒看到巴士,也沒有通知),過去 7 天:在我們能查核的班次中,沒有任何一班。
結論
Median provider predictions are 3.1 min later than the timetable in 1 hours of the day.
Provider predictions are about 1.9 min earlier than the timetable, 15:00.
Matched public positions cover 100% of scheduled trips. This is a lower bound on operated service, not an audited delivery result.
Scenario: 3 min more running time on 20 trips. The schedule-block model adds no buses; fleet and workforce feasibility are unverified.
Assumptions: published departure times, trip blocks and service pattern stay fixed while running time changes. A scheduler must test headways, transfers, recovery, fleet circulation, operator shifts, labour rules and cost before use.
| What | 時間 | 已測量 | Scenario or next investigation |
|---|---|---|---|
| ProblemPredictions later than timetable | 08:00 | 3.1 min late | More running time |
| ProblemPredictions earlier than timetable | 15:00 | 1.9 min early | Less running time, or holding points |
| StrengthObserved-position lower bound | All measured hours | 100% | Keep what works |
路線檢查
這是我們所知內容的簡短摘要。如果無法回答某個問題，我們會說明。
重點結論
在評分之前,我們需要先確認這項服務原本應如何運作。
預測樣本數: 樣本量中等
Based on 556 eligible provider predictions over 17 measured days, from 2026年10月6日 to 2026年11月3日.
Updated 2026年11月4日 下午1:32
這些是預測與班表之間反覆出現的差異，並非獨立測得的服務失誤。它們使用與上方結果相同的合格預測，但按站點而非時段分組，因此兩份清單不一定逐行相符。
由於此服務需要針對特定目的進行測試,因此不會為問題時段排名。
目前沒有與此路線相符的官方通知。
各站的預測差異
我們目前還沒有足夠的各路線各站點歷史資料,無法指出經常出問題的站點。乘客回報只作為線索,不作為證明。
打開一個時段,即可查看每個服務日、預定班次、資料空檔、已觀察到的公開車輛編號,以及此摘要背後的確切數字。
時刻表變更檢查
此頁面比較目前保留的官方時刻表與先前保留的版本。時刻表變更只說明原本的計劃,不能證明某個班次已經行駛。
Current published schedule began 2026年10月30日
我們會檢查新時刻表開始後的第一個星期一，以及一週前的星期一。所有數字都來自下列保留的官方 GTFS 版本。
所選日期中，至少有一個日期有新增或取消的特定日期服務。請將此視為假日或特別服務的情況，而不是平日一般的服務增加。
已核對的服務日期: 2026年10月26日
Operator calendar-date records: 0 added · 2 removed
資料串流指紋: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad
已核對的服務日期: 2026年11月2日
Operator calendar-date records: 0 added · 2 removed
資料串流指紋: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945
我們會比較變更前後各 14 天已確認的到站紀錄。只有在變更前後兩段時間都至少有 7 個服務日和 200 次到站紀錄時，我們才會公布比較結果。
一般的準點評分不適用於此路線的服務目的。班表數量仍然會顯示，但結果要等下文所述、符合此服務目的的數據證據。
校驗碼可讓任何人核對，是哪一份留存的時刻表產生這些數量。數量有變動，並不能說明原因、取消、營運單位的決定或對乘客的影響。
在有針對此用途的完成率和接載量測資料之前，不會顯示評等。
公開資料來源沒有提供可靠的乘客人數，也沒有提供漏載乘客的事件。缺少車輛位置，本身並不能證明班次取消、未出車、中途折返或其原因。
暫定結果，已公布的數據
未先確認此服務的用途,就不適合給予一般的準點評級。上方的路線檢查說明了所需的接送、社區服務或活動方面的證據。您仍可在下方查看已記錄的行程和資料缺口。
佐證期間: 2026年10月6日 to 2026年11月3日
30 / 30 scheduled trips published at least one position across 5 service days (100.0%).
這不是已確認的未發車。 找不到車輛位置，可能是班次取消或漏班，也可能是班次編號未指派，或是營運單位的資料來源出現缺口。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 3, 2026 · 6 trips in the retained timetable · retained notices; capture coverage unverified
In short: 6 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.