1 trip cancelled now · 5 did not run in 十一月Cancellations →

Previous measure: 80.3% of arrivals were within five minutes of the timetable (120,830 arrivals over 27 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.

线路 44: Billings Bridge ⇄ Hurdman

每 14 至 30 分钟一班

开往 Billings Bridge2 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: 2026年10月28日 – 2026年11月3日

Scheduled trips with cancellation notices

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: 8 trips with qualifying later matching vehicle observations. Trips with any notice: 17.

Trips needing investigation

11 of 802 trips with a usable feed window (1.4%) had no matching position.

These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.

791 with position · 11 to investigate · 0 excluded · 802 scheduled trips

Current feed. 1 distinct trips on this route are explicitly marked cancelled or deleted in the current feed. Observed: 2026年11月4日 13:45.

Coverage, exclusions and sources

0 of 12 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: 791 / 802 (98.6%). 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:20

Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.

What does the evidence show?

Predictions against the timetable

80.3%

of eligible provider predictions were within five minutes of the timetable.

Predictions in the source: 120,830
Weekdays with evidence: 19
Evidence window: 2026年10月6日 – 2026年11月3日

The hours we have evidence for

0时100% · 1,432 predictions · 14 days
1时100% · 80 predictions · 10 days
5时95% · 1,670 predictions · 14 days
6时94% · 3,116 predictions · 14 days
7时91% · 3,641 predictions · 14 days
8时88% · 3,866 predictions · 14 days
9时91% · 4,003 predictions · 14 days
10时91% · 3,813 predictions · 14 days
11时80% · 3,793 predictions · 14 days
12时78% · 3,870 predictions · 14 days
13时71% · 3,899 predictions · 14 days
14时69% · 3,975 predictions · 14 days
15时66% · 4,017 predictions · 14 days
16时69% · 3,933 predictions · 14 days
17时77% · 3,943 predictions · 14 days
18时82% · 3,962 predictions · 14 days
19时76% · 2,651 predictions · 14 days
20时88% · 2,272 predictions · 14 days
21时79% · 2,339 predictions · 14 days
22时89% · 2,288 predictions · 14 days
23时98% · 2,155 predictions · 14 days

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.

What about time of day?

21 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.

Explore the dated evidence Source of this result

公交车扎堆到站

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日.

数值与解读

3% of back-to-back buses on this route arrived bunched together: 3,410 of 106,974 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

2% of pairs (2,105) had a long gap: more than 1.75 times the planned wait between them.

公交车扎堆到站
时段	已检查的配对	扎堆	间隔过长
清晨（凌晨4点至6点）	731	0% (0)	0% (0)
早高峰(上午 6 点至 9 点)	15,935	1% (133)	1% (97)
中午（上午9点至下午3点）	40,166	4% (1,441)	2% (863)
下午高峰(下午3点至6点)	20,820	6% (1,240)	4% (836)
晚间（晚上 6 点至 10 点）	20,245	3% (590)	2% (305)
夜间（晚上10点至凌晨4点）	9,077	0% (6)	0% (4)

测量方式 →How we got this number每条线路的扎堆和缓慢路段 →

这条路线最慢的路段

Slowest: WALKLEY B to HERON / ALTA VISTA, 14.8 km/h actual against 16.4 km/h planned.

这条路线最慢的路段
起点	到	距离	计划速度	实际速度	已测量的行程	缓慢行程
WALKLEY B	HERON / ALTA VISTA	3.9 km	16.4 km/h	14.8 km/h	1,384	5%
HERON / ALTA VISTA	WALKLEY E	3.8 km	15 km/h	15.9 km/h	1,411	0%
HURDMAN D	HERON / ALTA VISTA	4.9 km	21.5 km/h	23.1 km/h	1,407	1%
WALKLEY E	BILLINGS BRIDGE 4D	2.2 km	35.4 km/h	34.4 km/h	21	14%
BILLINGS BRIDGE 3B	WALKLEY B	2.2 km	30.9 km/h	35.2 km/h	1,364	4%

慢行程是指用时至少为计划时间的 1.5 倍。

测量方式 →

此线路附近的市政道路施工

渥太华市已发布的道路施工和活动封路信息，按靠近本线路路径来衡量。靠近不代表巴士一定绕行。请查看运营方自己发布的服务提醒。

目前无法读取市政府的道路施工清单。

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.

31 scheduled trips with counted cancellation notices from 10月7日周三 to 11月3日周二.

Not counted: 16 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.

取消次数最多的时段: 17时 (5), 8时 (4), 13时 (4)

What this route needs

Median provider predictions are 3.2 min later than the timetable in 2 hours of the day.

Provider predictions are about 2.7 min earlier than the timetable, 01:00.

Predicted waits All measured hours are 2.1 min longer than scheduled waits.

15:00 has 66% of predictions within five minutes of the timetable, against 88% the rest of the day.

Only 99% of scheduled trips were seen; the rest are not counted as missed.

Scenario: 3 min more running time on 172 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.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 21 hours with samples

00:00: 99.6% of final predictions within five minutes of the timetable, 1,432 predictions, typically 0.2 min early
01:00: 100% of final predictions within five minutes of the timetable, 80 predictions, typically 2.7 min early
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 95% of final predictions within five minutes of the timetable, 1,670 predictions, typically 0.3 min late
06:00: 94.4% of final predictions within five minutes of the timetable, 3,116 predictions, typically 0.6 min late
07:00: 90.7% of final predictions within five minutes of the timetable, 3,641 predictions, typically 0.2 min late
08:00: 87.5% of final predictions within five minutes of the timetable, 3,866 predictions, typically 0.5 min late
09:00: 90.7% of final predictions within five minutes of the timetable, 4,003 predictions, typically 0.4 min late
10:00: 90.8% of final predictions within five minutes of the timetable, 3,813 predictions, typically 0.5 min late
11:00: 80.1% of final predictions within five minutes of the timetable, 3,793 predictions, typically 1.3 min late
12:00: 77.5% of final predictions within five minutes of the timetable, 3,870 predictions, typically 1.8 min late
13:00: 71.4% of final predictions within five minutes of the timetable, 3,899 predictions, typically 2.2 min late
14:00: 68.8% of final predictions within five minutes of the timetable, 3,975 predictions, typically 2.7 min late
15:00: 65.6% of final predictions within five minutes of the timetable, 4,017 predictions, typically 3.1 min late
16:00: 68.9% of final predictions within five minutes of the timetable, 3,933 predictions, typically 3.4 min late
17:00: 77% of final predictions within five minutes of the timetable, 3,943 predictions, typically 2.1 min late
18:00: 82.2% of final predictions within five minutes of the timetable, 3,962 predictions, typically 2.3 min late
19:00: 75.8% of final predictions within five minutes of the timetable, 2,651 predictions, typically 2.6 min late
20:00: 88% of final predictions within five minutes of the timetable, 2,272 predictions, typically 1.9 min late
21:00: 78.9% of final predictions within five minutes of the timetable, 2,339 predictions, typically 2.2 min late
22:00: 89.1% of final predictions within five minutes of the timetable, 2,288 predictions, typically 1.1 min late
23:00: 97.6% of final predictions within five minutes of the timetable, 2,155 predictions, typically 0.2 min late

90% or more of predictions within five minutes
80 to 90% of predictions within five minutes
under 80% of predictions within five minutes
not enough data

Findings
What	时间	已测量	Scenario or next investigation
ProblemPredictions later than timetable	15:00 to 17:00	3.2 min late	More running time
ProblemPredicted spacing varies	All measured hours	2.1 min extra wait	Manage the headway
ProblemOne hour has a lower prediction match	15:00	66%	Operations, not the timetable
ProblemPredictions earlier than timetable	01:00	2.7 min early	Less running time, or holding points
CaveatCoverage gap	All measured hours	99%	More observation, not a service change

Measurements

Predictions later than timetable · 15:00 to 17:00: Measured arrivals 7,950; Hours affected 2; Spread 12.2 min; Median delay 3.2 min; Suggested running time change 3.2 min
Predicted spacing varies · All measured hours: 站点 20; Extra wait share 29.1%; 已匹配的到达 807; 额外等待 2.1 min; Scheduled wait 7.2 min
One hour has a lower prediction match · 15:00: 小时 15:00; 准点 65.6%; Measured arrivals 4,017; Shortfall 21.9 pts; Route median on time 87.5%
Predictions earlier than timetable · 01:00: Measured arrivals 80; Hours affected 1; Spread 1.8 min; Median delay -2.6 min; Suggested running time change -2.6 min
Coverage gap · All measured hours: 目标 99.5%; Trips with a matching position 98.6%; 运营日 7; Trips with a matching position 791; 时刻表班次 802

打开历史、可靠性和线路分析

线路检查

How route 44 has been running

这是我们所知情况的简短摘要。如果我们无法回答某个问题，会明确说明。

结论

供应商的预测通常与时刻表接近，但请查看下方的问题时段。

80 in 100 eligible predictions were within 5 minutes of the timetable · 120,830 predictions checked

预测样本量: 样本较大

Based on 120,830 eligible provider predictions over 27 measured days, from 2026年10月6日 to 2026年11月3日.

Updated 2026年11月4日 12:32

预测在哪些地点和时间反复出现差异?

这些是预测时间与时刻表之间反复出现的差异，不是独立测得的服务故障。它们使用与上述结果相同的合格预测，但按站点而不是按时段分组，所以两个列表不一定逐行一致。

15时–16时: 34 in 100 eligible predictions differed from the timetable by more than 5 minutes (4,017 predictions over 14 days).
14时–15时: 31 in 100 eligible predictions differed from the timetable by more than 5 minutes (3,975 predictions over 14 days).
16时–17时: 31 in 100 eligible predictions differed from the timetable by more than 5 minutes (3,933 predictions over 14 days).

目前没有与这条线路相符的官方通知。

各站预测差异

TERMINAL / SANDFORD FLEMING
34 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,640 predictions over 30 days).
打开此站点
SANDFORD FLEMING / INDUSTRIAL
33 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,641 predictions over 30 days).
打开此站点

这些是按路线给出的服务方预测，并与时刻表作了对比。它们显示的是某地某时重复出现的预测差异，不是实测到达时间，也不能说明原因。

查看每个行程和日期

展开一个时间段,可查看每个服务日、预定班次、数据缺口、观测到的公开车辆编号,以及本摘要背后的确切数字。

乘客想知道什么

现在有班次被取消吗？: 0 of 12检查未来4小时内从线路起终点开始的行程。这不是历史取消率。
排除数据缺口后，可能的未出车情况？: 11 of 802 checked trips need a closer look11 of 802 trips with enough public-feed evidence had no matching position over 7 days. 0 of 802 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
运营方的预测与时刻表有何不同?: At the 95th percentile, the predicted difference was 11.1 min (positive means later; negative means earlier)80 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
运营方的预测意味着需要等多久？: 9.3 min average predicted wait2.1 min beyond the scheduled wait, based on 807 eligible predictions at 20 high-frequency stops over 14 days.

时刻表变更检查

已发布时刻表：变更前后

这是将当前保留的官方时刻表与上一个保留版本进行比较。时刻表变更说明的是原定计划，并不能证明某个班次确实运行过。

Current published schedule began 2026年10月30日

每份已发布时刻表中所选的服务日

我们会查看新时刻表开始后的第一个星期一，以及提前一周的星期一。所有数字都来自下方列出的、已保留的官方 GTFS 版本。

所选日期中，至少有一个日期采用了新增或取消的按日历日期安排的服务。请将其视为节假日或特别服务的情况，而不是普通工作日的增长。

之前

已核对的服务日期: 2026年10月26日

时刻表班次: 132
不同的预定站点: 85
已发布的不同路径: 3
已公布的服务时段: 5:00–1:06 next day

Operator calendar-date records: 0 added · 2 removed

数据源指纹: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

新时刻表

已核对的服务日期: 2026年11月2日

时刻表班次: 132
不同的预定站点: 85
已发布的不同路径: 3
已公布的服务时段: 5:00–1:06 next day

Operator calendar-date records: 0 added · 2 removed

数据源指纹: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

变更后服务有改善吗？

我们会比较变更前后各14天内已确认的到站情况。只有变更前后两边都至少有7个服务日和200次到站记录时，我们才会发布比较结果。

Still collecting: before has 64,594 arrivals over 14 days; after has 21,789 arrivals over 5 days. No improvement or decline is claimed yet.

校验和可让任何人核实是哪份留存的时刻表得出这些数量。数量变化并不能说明原因、取消、运营方的决定或对乘客的影响。

如何评价这条线路: 普通站站停靠线路

我们将每个预定到达班次的最后一个合格服务方预测与官方时刻表进行比较。这些不是独立测量的到达时间。一项结果至少需要 200 条合格预测。这里采用面向乘客的目标：误差在 5 分钟内。

这些数据无法证明的事

公开数据源不提供可靠的乘客人数，也不提供乘客被错过的事件。缺少车辆位置本身，并不能证明班次已取消、未出车、提前折返，也不能说明原因。

查看定义、阈值和数据依据的顺序

官方实时数据：明确的取消、跳过的站点和当前有效的通知。
匹配的观测数据:与官方时刻表相关联的车辆位置和已确定的预测。
官方时刻表：计划的内容，与实际观测到的内容分开显示。
乘客和运营方的报告：这些是关于线路、时间和地点的线索，供进一步调查，本身不能作为数字证明。

初步结果,已公布的数据

预测与时刻表相比如何?

每个小时，我们都会把某个预定到站班次最后一次符合条件的运营方预测与时刻表进行比较。“5 分钟内”指的是这个预测差异，不是实际测得的到站时间，也不能证明公交车已经运行。

佐证时间段: 2026年10月6日 to 2026年11月3日

与时刻表相差不超过5分钟: 80.3%
已核查的合格预测: 120,830
有数据的工作日: 19
第95百分位预测延误: 11.1 min late

Patterns by hour (21)

Patterns by hour (21)
小时	准点	中位数	第95百分位	数据证据
00:00	99.6%	0.2 min early	2.6 min late	1,432 · 14 days
01:00	100.0%	2.7 min early	0.9 min early	80 · 10 days
05:00	95.0%	0.3 min late	5.4 min late	1,670 · 14 days
06:00	94.4%	0.6 min late	5.4 min late	3,116 · 14 days
07:00	90.7%	0.2 min late	6.3 min late	3,641 · 14 days
08:00	87.5%	0.5 min late	7.6 min late	3,866 · 14 days
09:00	90.7%	0.4 min late	5.9 min late	4,003 · 14 days
10:00	90.8%	0.5 min late	6.4 min late	3,813 · 14 days
11:00	80.1%	1.3 min late	9.9 min late	3,793 · 14 days
12:00	77.5%	1.8 min late	12.6 min late	3,870 · 14 days
13:00	71.4%	2.2 min late	16.3 min late	3,899 · 14 days
14:00	68.8%	2.7 min late	14.4 min late	3,975 · 14 days
15:00	65.6%	3.1 min late	18.2 min late	4,017 · 14 days
16:00	68.9%	3.4 min late	12.6 min late	3,933 · 14 days
17:00	77.0%	2.1 min late	11.8 min late	3,943 · 14 days
18:00	82.2%	2.3 min late	8.8 min late	3,962 · 14 days
19:00	75.8%	2.6 min late	10.8 min late	2,651 · 14 days
20:00	88.0%	1.9 min late	6.2 min late	2,272 · 14 days
21:00	78.9%	2.2 min late	8 min late	2,339 · 14 days
22:00	89.1%	1.1 min late	7.3 min late	2,288 · 14 days
23:00	97.6%	0.2 min late	4.3 min late	2,155 · 14 days

3 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.

有时刻表的巴士，但没有实时观测记录

791 / 802 scheduled trips published at least one position across 7 service days (98.6%).

11:002 / 48 trips without a position95.8%
13:002 / 48 trips without a position95.8%
20:001 / 28 trips without a position96.4%
15:001 / 43 trips without a position97.7%
16:001 / 43 trips without a position97.7%
06:001 / 46 trips without a position97.8%

这不是已确认的未发车。 缺少位置可能表示公交车被取消或漏班，也可能表示行程编号未分配，或运营方数据源有缺口。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

Trips scheduled that day

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.

Service day

November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

November 3, 2026 · 132 trips in the retained timetable · retained notices; capture coverage unverified

In short: 132 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.

05:00– 05:22
Trip 35060030Vehicle position matchedFirst / last feed position: 4:40 a.m. EST / 5:33 a.m. EST; not actual start or end times.
05:00– 05:24
Trip 36108030Vehicle position matchedFirst / last feed position: 4:47 a.m. EST / 5:28 a.m. EST; not actual start or end times.
05:30– 05:54
Trip 30006030Vehicle position matchedFirst / last feed position: 4:46 a.m. EST / 6:13 a.m. EST; not actual start or end times.
05:30– 05:57
Trip 4366030Vehicle position matchedFirst / last feed position: 5:29 a.m. EST / 6:06 a.m. EST; not actual start or end times.
06:00– 06:28
Trip 26275030Vehicle position matchedFirst / last feed position: 5:59 a.m. EST / 6:31 a.m. EST; not actual start or end times.
06:00– 06:28
Trip 35930030Vehicle position matchedFirst / last feed position: 6:07 a.m. EST / 6:44 a.m. EST; not actual start or end times.
06:15– 06:43
Trip 29133030Vehicle position matchedFirst / last feed position: 6:14 a.m. EST / 6:52 a.m. EST; not actual start or end times.
06:20– 06:49
Trip 4522030Vehicle position matchedFirst / last feed position: 6:07 a.m. EST / 6:58 a.m. EST; not actual start or end times.
06:30– 06:58
Trip 16167030Vehicle position matchedFirst / last feed position: 6:09 a.m. EST / 7:07 a.m. EST; not actual start or end times.
06:36– 07:06
Trip 14848030Vehicle position matchedFirst / last feed position: 6:28 a.m. EST / 7:13 a.m. EST; not actual start or end times.
06:45– 07:15
Trip 9178030Vehicle position matchedFirst / last feed position: 6:45 a.m. EST / 7:24 a.m. EST; not actual start or end times.
06:51– 07:22
Trip 17945030Vehicle position matchedFirst / last feed position: 6:53 a.m. EST / 7:55 a.m. EST; not actual start or end times.

· Open all evidence for this day

线路 44: Billings Bridge ⇄ Hurdman

Did the scheduled service run?

Scheduled trips with cancellation notices

Trips needing investigation

What does the evidence show?

The hours we have evidence for

What about time of day?

公交车扎堆到站

这条路线最慢的路段

此线路附近的市政道路施工

此线路的取消班次

最近取消的班次

What this route needs

预测在哪些地点和时间反复出现差异?

查看每个行程和日期

乘客想知道什么

每份已发布时刻表中所选的服务日

之前

新时刻表

变更后服务有改善吗？

预测与时刻表相比如何?

Trips scheduled that day

Did the scheduled service run?

Scheduled trips with cancellation notices

Trips needing investigation

What does the evidence show?

The hours we have evidence for

What about time of day?

公交车扎堆到站

这条路线最慢的路段

此线路附近的市政道路施工

此线路的取消班次

最近取消的班次

What this route needs

预测在哪些地点和时间反复出现差异?

查看每个行程和日期

乘客想知道什么

每份已发布时刻表中所选的服务日

之前

新时刻表

变更后服务有改善吗？

预测与时刻表相比如何?

Trips scheduled that day