地图
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.
1
1 of 20 trips with a usable feed window (5%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
19 with position · 1 to investigate · 0 excluded · 20 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 2026年11月4日 14:41.
0 of 2 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: 19 / 20 (95%). 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日 13:19
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
The threshold is 200 eligible predictions. The available sample does not support publishing this result.
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月4日
2 partial-capture days not counted.
2 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月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日.
Too few buses were measured to judge bunching: 0 pairs checked, 30 needed.
Not enough trips yet to measure speed between timepoints (20 trips needed for each segment).
测量方式 →渥太华市已发布的道路施工和活动封路信息，按靠近本线路路径来衡量。靠近不代表巴士一定绕行。请查看运营方自己发布的服务提醒。
道路施工
Moodie S/B at 417 overpass
2026年11月2日 06:00 to 2026年11月9日 14:30
Moodie southbound reduced to 1 lane at 417 overpass due to construction, from November 4th to 9th between 6:00 and 2:30pm.
市政府标明此项会影响公共交通。
about 0 m from the route
City record updated 2026年11月2日 13:12.
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.
来源：渥太华市交通事件（道路施工和封闭）。包含根据渥太华市开放政府许可协议授权的信息。渥太华市表示，此列表仅尽力提供，可能不完整。 渥太华市交通地图 ↗
2 partial-capture days not counted.
过去四周内，这条线路没有计入的取消班次。我们无法核实的通知会列在下方。
未到（没有看到公交车，也没有通知），最近7天：在我们能核查的班次中没有。
结论
Median provider predictions are 3.6 min later than the timetable in 1 hours of the day.
Only 95% of scheduled trips were seen; the rest are not counted as missed.
Scenario: 4 min more running time on 10 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 | 07:00 | 3.6 min late | More running time |
| CaveatCoverage gap | All measured hours | 95% | More observation, not a service change |
线路检查
这是我们所知情况的简短摘要。如果我们无法回答某个问题，会明确说明。
结论
符合条件的预测还不够多，暂时无法发布线路对比。
77 in 100 eligible predictions were within 5 minutes of the timetable · 178 predictions checked预测样本量: 仍在积累数据
Based on 178 eligible provider predictions over 18 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次到站记录时，我们才会发布比较结果。
Still collecting: before has 100 arrivals over 10 days; after has 31 arrivals over 3 days. No improvement or decline is claimed yet.
校验和可让任何人核实是哪份留存的时刻表得出这些数量。数量变化并不能说明原因、取消、运营方的决定或对乘客的影响。
我们将每个预定到达班次的最后一个合格服务方预测与官方时刻表进行比较。这些不是独立测量的到达时间。一项结果至少需要 200 条合格预测。这里采用面向乘客的目标：误差在 5 分钟内。
公开数据源不提供可靠的乘客人数，也不提供乘客被错过的事件。缺少车辆位置本身，并不能证明班次已取消、未出车、提前折返，也不能说明原因。
初步结果,已公布的数据
每个小时，我们都会把某个预定到站班次最后一次符合条件的运营方预测与时刻表进行比较。“5 分钟内”指的是这个预测差异，不是实际测得的到站时间，也不能证明公交车已经运行。
佐证时间段: 2026年10月6日 to 2026年11月3日
| 小时 | 准点 | 中位数 | 第95百分位 | 数据证据 |
|---|---|---|---|---|
| 07:00 | 63.3% | 3.6 min late | 9.4 min late | 30 · 10 days |
| 08:00 | 90.3% | 0.9 min late | 6.2 min late | 31 · 10 days |
| 16:00 | 75.0% | 1.8 min late | 9.2 min late | 20 · 10 days |
| 17:00 | 50.0% | 4.2 min late | 11.2 min late | 20 · 10 days |
2 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
19 / 20 scheduled trips published at least one position across 5 service days (95.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 · 4 trips in the retained timetable · retained notices; capture coverage unverified
In short: 3 with a matched position · 1 with no matching position (to investigate) · 0 with an unknown outcome.