Extra trips on Route 256 Tunney’s Pasture: September 25 2026 - We’ve added weekday trips on Route 256 Tunney’s Pasture (from Bridlewood) at 6:30 am and 6:58 am. These will help reduce crowding and make your ride more comfortable.

No 256 trips cancelled now · 0 did not run in 十一月Cancellations →

线路 256: Tunney's Pasture ⇄ Bridlewood

每 16 至 27 分钟一班

开往 Tunney's Pasture0 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月27日 – 2026年11月2日

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

Trips needing investigation

0 of 95 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.

95 with position · 0 to investigate · 0 excluded · 95 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 2026年11月3日 15:06.

Coverage, exclusions and sources

0 of 8 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: 95 / 95 (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月3日 13:39

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

No comparable percentage published

This service purpose needs a different method. A general percentage could give a misleading picture.

Predictions in the source: 14,827
Weekdays with evidence: 18
Evidence window: 2026年10月5日 – 2026年11月2日

These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.

Calculated: 2026年11月3日

2 partial-capture days not counted.

What about time of day?

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.

Explore the dated evidence Source of this result

公交车扎堆到站

Last 28 days, 2026年10月6日 to 2026年11月2日: 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日.

数值与解读

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

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

公交车扎堆到站
时段	已检查的配对	扎堆	间隔过长
早高峰(上午 6 点至 9 点)	5,822	3% (153)	5% (268)
中午（上午9点至下午3点）	37	0% (0)	0% (0)
下午高峰(下午3点至6点)	2,436	1% (27)	2% (44)
晚间（晚上 6 点至 10 点）	1,321	0% (1)	0% (0)

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

这条路线最慢的路段

Slowest: COPE / TEMPLEFORD to BRIDGESTONE / FOXHALL, 24.8 km/h actual against 29 km/h planned.

这条路线最慢的路段
起点	到	距离	计划速度	实际速度	已测量的行程	缓慢行程
COPE / TEMPLEFORD	BRIDGESTONE / FOXHALL	5 km	29 km/h	24.8 km/h	149	6%
BRIDGESTONE / FOXHALL	OLD RICHMOND / WEST HUNT CLUB	5.1 km	27.6 km/h	26.5 km/h	165	0%
TUNNEY'S PASTURE A	BRIDGESTONE / FOXHALL	20.5 km	23.4 km/h	28.2 km/h	133	0%

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

测量方式 →

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

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

道路施工
Moodie between Hadley cir and Roberston
2026年10月15日 00:00 to 2026年11月13日 17:00
Moodie off-peak lane reductions between Hadley cir and Roberston due to construction, from October 15th to November 13th.
市政府标明此项会影响公共交通。
about 0 m from the route
City record updated 2026年10月16日 13:08.
道路施工
CARLING E/B between Kichi Zibi Mikan on Ramp and EDGEWORTH
2026年10月30日 00:00 to 2026年11月13日 15:00
CARLING eastbound reduced to 1 lane between Kichi Zibi Mikan on Ramp and EDGEWORTH due to construction, from November 2nd to 13th between 9:30am and 3:00pm.
about 0 m from the route
City record updated 2026年10月30日 11:40.
道路施工
Kichi Zibi Mikan between ISLAND PARK and WOODROFFE
2026年10月30日 09:30 to 2026年11月20日 15:00
Kichi Zibi Mikan reduced to 1 lane in each direction between ISLAND PARK and WOODROFFE due to construction, from November 2nd to 20th between 9:30am and 3:00pm.
about 0 m from the route
City record updated 2026年10月30日 09:28.
道路施工
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.
道路施工
COPE between TERRY FOX and TEMPLEFORD
2026年11月3日 07:00 to 2026年11月16日 17:00
COPE closed between TERRY FOX and TEMPLEFORD due to construction, from November 6th to 16th. Follow the signed detour.
市政府标明此项会影响公共交通。
about 0 m from the route
City record updated 2026年11月3日 06: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.

来源：渥太华市交通事件（道路施工和封闭）。包含根据渥太华市开放政府许可协议授权的信息。渥太华市表示，此列表仅尽力提供，可能不完整。渥太华市交通地图 ↗

此线路的取消班次

这些词是什么意思 →

2 partial-capture days not counted.

1 scheduled trips with counted cancellation notices from 10月6日周二 to 11月2日周一.

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

取消次数最多的时段: 15时 (1)

What this route needs

Median provider predictions are 4.8 to 5 min later than the timetable in 2 hours of the day.

Predictions near the start are about 3.4 min later than the timetable, with a similar difference near the end. This does not establish the cause.

Provider predictions are about 6.8 min earlier than the timetable, 15:00 to 20:00.

19:00 has 2% of predictions within five minutes of the timetable, against 41% the rest of the day.

Matched public positions cover 100% of scheduled trips. This is a lower bound on operated service, not an audited delivery result.

Next investigation: test terminal recovery and the preceding trip against operational records. Predictions alone do not establish the cause.

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

00:00: not enough data
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 52.4% of final predictions within five minutes of the timetable, 746 predictions, typically 4.8 min late
06:00: 84.8% of final predictions within five minutes of the timetable, 1,462 predictions, typically 2.2 min late
07:00: 82.8% of final predictions within five minutes of the timetable, 1,633 predictions, typically 1.3 min late
08:00: 49.2% of final predictions within five minutes of the timetable, 826 predictions, typically 5 min late
09:00: not enough data
10:00: not enough data
11:00: not enough data
12:00: not enough data
13:00: not enough data
14:00: not enough data
15:00: 25.3% of final predictions within five minutes of the timetable, 459 predictions, typically 6.8 min early
16:00: 40.9% of final predictions within five minutes of the timetable, 946 predictions, typically 4.8 min early
17:00: 31.1% of final predictions within five minutes of the timetable, 1,152 predictions, typically 6.8 min early
18:00: 31.5% of final predictions within five minutes of the timetable, 801 predictions, typically 6.7 min early
19:00: 2.3% of final predictions within five minutes of the timetable, 265 predictions, typically 13.3 min early
20:00: not enough data
21:00: not enough data
22:00: not enough data
23:00: not enough data

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 earlier than timetable	15:00 to 20:00	6.8 min early	Less running time, or holding points
ProblemPredictions later than timetable	05:00 · 08:00	4.8 min late · 5 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	19:00	2%	Operations, not the timetable
StrengthObserved-position lower bound	All measured hours	100%	Keep what works

Measurements

Predictions earlier than timetable · 15:00 to 20:00: Measured arrivals 3,623; Hours affected 5; Spread 10.8 min; Median delay -6.8 min; Suggested running time change -6.8 min
Predictions later than timetable · 08:00: Measured arrivals 826; Hours affected 1; Spread 15.4 min; Median delay 5 min; Suggested running time change 5 min
Predictions later than timetable · 05:00: Measured arrivals 746; Hours affected 1; Spread 4.7 min; Median delay 4.8 min; Suggested running time change 4.8 min
One hour has a lower prediction match · 19:00: 小时 19:00; 准点 2.3%; Measured arrivals 265; Shortfall 38.6 pts; Route median on time 40.9%
Observed-position lower bound · All measured hours: 目标 99.5%; Trips with a matching position 100%; 运营日 5; Trips with a matching position 95; 时刻表班次 95

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

线路检查

How route 256 has been running

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

结论

我们需要先知道这条快线在哪里上客，才能给它评级。

预测样本量: 样本较大

Based on 14,827 eligible provider predictions over 18 measured days, from 2026年10月5日 to 2026年11月2日.

Updated 2026年11月3日 14:32

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

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

由于此服务需要针对特定用途的测试,问题时段未进行排名。

1 current notice affects this route

• Extra trips on Route 256 Tunney’s Pasture

各站预测差异

我们还没有足够的各线路各站点历史数据，无法指出反复出问题的站点。乘客的报告只作为线索，不作为证据。

查看每个行程和日期

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

乘客想知道什么

现在有班次被取消吗？: 0 of 8检查未来4小时内从线路起终点开始的行程。这不是历史取消率。
排除数据缺口后，可能的未出车情况？: 0 of 95 checked trips need a closer look0 of 95 trips with enough public-feed evidence had no matching position over 7 days. 0 of 95 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
运营方的预测与时刻表有何不同?: 证据还不够
运营方的预测意味着需要等多久？: 目前还没有路线级别的结果达到数据依据的门槛。这并不表示没有出现过服务间隔。

时刻表变更检查

已发布时刻表：变更前后

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

Current published schedule began 2026年10月30日

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

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

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

之前

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

时刻表班次: 19
不同的预定站点: 93
已发布的不同路径: 2
已公布的服务时段: 5:14–19:38

Operator calendar-date records: 0 added · 2 removed

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

新时刻表

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

时刻表班次: 19
不同的预定站点: 93
已发布的不同路径: 2
已公布的服务时段: 5:14–19:38

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月5日 to 2026年11月2日

已核查的合格预测: 14,827
有数据的工作日: 18

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

95 / 95 scheduled trips published at least one position across 5 service days (100.0%).

05:000 / 10 trips without a position100.0%
06:000 / 20 trips without a position100.0%
07:000 / 15 trips without a position100.0%
08:000 / 5 trips without a position100.0%
14:000 / 5 trips without a position100.0%
15:000 / 5 trips without a position100.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

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 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026 October 27, 2026

November 2, 2026 · 19 trips in the retained timetable · retained notices; capture coverage unverified

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

05:14– 06:08
Trip 6850020Vehicle position matchedFirst / last feed position: 5:18 a.m. EST / 6:16 a.m. EST; not actual start or end times.
05:50– 06:38
Trip 30198020Vehicle position matchedFirst / last feed position: 5:07 a.m. EST / 6:42 a.m. EST; not actual start or end times.
06:17– 07:08
Trip 2518020Vehicle position matchedFirst / last feed position: 6:15 a.m. EST / 7:08 a.m. EST; not actual start or end times.
06:30– 07:25
Trip 19650020Vehicle position matchedFirst / last feed position: 6:04 a.m. EST / 7:19 a.m. EST; not actual start or end times.
06:43– 07:38
Trip 5633020Vehicle position matchedFirst / last feed position: 6:37 a.m. EST / 7:38 a.m. EST; not actual start or end times.
06:58– 07:53
Trip 17366020Vehicle position matchedFirst / last feed position: 6:16 a.m. EST / 7:47 a.m. EST; not actual start or end times.
07:13– 08:08
Trip 14874020Vehicle position matchedFirst / last feed position: 6:45 a.m. EST / 8:14 a.m. EST; not actual start or end times.
07:42– 08:39
Trip 169020Vehicle position matchedFirst / last feed position: 7:09 a.m. EST / 8:40 a.m. EST; not actual start or end times.
07:50– 08:43
Trip 28008020Vehicle position matchedFirst / last feed position: 7:14 a.m. EST / 8:43 a.m. EST; not actual start or end times.
08:17– 09:10
Trip 7684020Vehicle position matchedFirst / last feed position: 8:10 a.m. EST / 9:13 a.m. EST; not actual start or end times.
14:59– 15:54
Trip 17023020Vehicle position matchedFirst / last feed position: 2:29 p.m. EST / 3:51 p.m. EST; not actual start or end times.
15:30– 16:33
Trip 27575020Vehicle position matchedFirst / last feed position: 2:50 p.m. EST / 4:30 p.m. EST; not actual start or end times.

· Open all evidence for this day

线路 256: Tunney's Pasture ⇄ Bridlewood

Did the scheduled service run?

Scheduled trips with cancellation notices

Trips needing investigation

What does the evidence show?

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?

What about time of day?

公交车扎堆到站

这条路线最慢的路段

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

此线路的取消班次

最近取消的班次

What this route needs

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

查看每个行程和日期

乘客想知道什么

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

之前

新时刻表

变更后服务有改善吗？

此结果背后的数据

Trips scheduled that day