Scheduled service and available evidence
Evidence period: 2026年10月28日 – 2026年11月3日
0
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. Not counted: 1 trips with qualifying later matching vehicle observations. Trips with any notice: 1.
2
2 of 50 trips with a usable feed window (4%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
48 with position · 2 to investigate · 0 excluded · 50 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 2026年11月4日 14:01.
0 of 6 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: 48 / 50 (96%). 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日 12:48
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日.
15% of back-to-back buses on this route arrived bunched together: 56 of 376 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
24% of pairs (90) had a long gap: more than 1.75 times the planned wait between them.
| 时段 | 已检查的配对 | 扎堆 | 间隔过长 |
|---|---|---|---|
| 早高峰(上午 6 点至 9 点) | 376 | 15% (56) | 24% (90) |
Slowest: BLAIR H to ST JOSEPH / R.R. 174, 23.9 km/h actual against 30.5 km/h planned.
| 起点 | 到 | 距离 | 计划速度 | 实际速度 | 已测量的行程 | 缓慢行程 |
|---|---|---|---|---|---|---|
| BLAIR H | ST JOSEPH / R.R. 174 | 3 km | 30.5 km/h | 23.9 km/h | 60 | 13% |
| HURDMAN E | BLAIR H | 5.1 km | 30.8 km/h | 32.1 km/h | 62 | 8% |
慢行程是指用时至少为计划时间的 1.5 倍。
2 partial-capture days not counted.
11 scheduled trips with counted cancellation notices from 10月7日周三 to 11月3日周二.
Not counted: 3 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
取消次数最多的时段: 15时 (7), 8时 (4)
OC Transpo 不提供单个班次的原因，因此不显示原因。
Did not come (no bus seen, no notice), last 7 days: 2 of 50 trips we could check.
结论
Only 96% of scheduled trips were seen; the rest are not counted as missed.
| What | 时间 | 已测量 | Scenario or next investigation |
|---|---|---|---|
| CaveatCoverage gap | All measured hours | 96% | More observation, not a service change |
线路检查
这是我们所知情况的简短摘要。如果我们无法回答某个问题，会明确说明。
结论
在评级之前,我们需要先确认这项服务应如何运行。
预测样本量: 样本较大
Based on 1,131 eligible provider predictions over 17 measured days, from 2026年10月6日 to 2026年11月3日.
Updated 2026年11月4日 13: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次到站记录时，我们才会发布比较结果。
Ordinary on-time scoring does not fit this route’s service purpose. The schedule counts remain visible, but the result waits for the purpose-specific evidence described below.
校验和可让任何人核实是哪份留存的时刻表得出这些数量。数量变化并不能说明原因、取消、运营方的决定或对乘客的影响。
在有针对该用途的完成率和接客指标之前，不显示评级。
公开数据源不提供可靠的乘客人数，也不提供乘客被错过的事件。缺少车辆位置本身，并不能证明班次已取消、未出车、提前折返，也不能说明原因。
初步结果,已公布的数据
未核实该服务的用途,就不适合使用普通的准点评级。上方的路线核查说明了所需的接送、社区服务或活动方面的数据证据。您仍然可以查看下方记录的行程和数据缺口。
佐证时间段: 2026年10月6日 to 2026年11月3日
48 / 50 scheduled trips published at least one position across 5 service days (96.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 · 10 trips in the retained timetable · retained notices; capture coverage unverified
In short: 10 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.