No 43 trips cancelled now · 1 did not run in 十一月Cancellations →

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

线路 43: Karsh ⇄ Greenboro

每 30 至 60 分钟一班

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

GREENBORO B36 min sched.
SOUTH KEYS C39 min
HUNT CLUB LOOP - STOP 1A40 min
DAZE / MALL ENTRANCE43 min
CAHILL / SOUTHGATE44 min
SOUTHGATE / AD. 329542 min sched.
JOHNSTON / SOUTHGATE43 min sched.
JOHNSTON / ALBION44 min sched.
TAPIOLA / JOHNSTON44 min sched.
TAPIOLA / GREENBORO45 min sched.
TAPIOLA / GREENBORO45 min sched.
TAPIOLA / CRIMSON46 min sched.
TAPIOLA / WINGALE46 min sched.
TAPIOLA / SOMERO46 min sched.
TAPIOLA / RUSHFORD47 min sched.
JOHNSTON / TAPIOLA48 min sched.
JOHNSTON / PENNARD50 min sched.
JOHNSTON / ZAIDAN50 min sched.
JOHNSTON / ALLANFORD51 min sched.
JOHNSTON / ALLANFORD53 min sched.
JOHNSTON / CONROY54 min sched.
JOHNSTON / EWING55 min sched.
JOHNSTON / AD. 200255 min sched.
JOHNSTON / BASLAW56 min sched.
JOHNSTON / BASLAW57 min sched.
BLOHM / REUBENS58 min sched.
BLOHM / AD. 157959 min sched.
KARSH / BLOHM59 min sched.
KARSH / CLAUDET0 min sched.
KARSH / TOPLEY1 min sched.
KARSH / EWING1 min sched.
LORRY GREENBERG / CONROY2 min 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: 3 trips with qualifying later matching vehicle observations. Trips with any notice: 3.

Trips needing investigation

1 of 185 trips with a usable feed window (0.5%) had no matching position.

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

184 with position · 1 to investigate · 0 excluded · 185 scheduled trips

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

Coverage, exclusions and sources

0 of 9 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: 184 / 185 (99.5%). 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: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.

What does the evidence show?

Predictions against the timetable

83.2%

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

Predictions in the source: 20,157
Weekdays with evidence: 18
Evidence window: 2026年10月6日 – 2026年11月3日

The hours we have evidence for

6时100% · 300 predictions · 10 days
7时56% · 600 predictions · 10 days
8时94% · 615 predictions · 10 days
9时81% · 610 predictions · 10 days
10时84% · 607 predictions · 10 days
11时91% · 610 predictions · 10 days
12时98% · 610 predictions · 10 days
13时95% · 610 predictions · 10 days
14时84% · 610 predictions · 10 days
15时83% · 862 predictions · 10 days
16时45% · 647 predictions · 10 days
17时79% · 586 predictions · 10 days
18时81% · 910 predictions · 10 days
19时76% · 575 predictions · 10 days
20时100% · 610 predictions · 10 days
21时88% · 610 predictions · 10 days
22时84% · 610 predictions · 10 days
23时92% · 579 predictions · 10 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?

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

数值与解读

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

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

公交车扎堆到站
时段	已检查的配对	扎堆	间隔过长
早高峰(上午 6 点至 9 点)	495	0% (0)	0% (0)
下午高峰(下午3点至6点)	2,012	1% (17)	1% (12)
晚间（晚上 6 点至 10 点）	1,028	0% (0)	0% (5)

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

这条路线最慢的路段

Slowest: TAPIOLA / RUSHFORD to JOHNSTON / CONROY, 22.9 km/h actual against 14.3 km/h planned.

这条路线最慢的路段
起点	到	距离	计划速度	实际速度	已测量的行程	缓慢行程
TAPIOLA / RUSHFORD	JOHNSTON / CONROY	1.6 km	14.3 km/h	22.9 km/h	302	0%
GREENBORO B	TAPIOLA / RUSHFORD	4.4 km	24.8 km/h	23 km/h	298	4%
LORRY GREENBERG / CONROY	JOHNSTON / CONROY	2.5 km	40.5 km/h	25.2 km/h	319	63%
JOHNSTON / CONROY	TAPIOLA / BRANDO	1.4 km	20.9 km/h	25.9 km/h	320	4%

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

测量方式 →

此线路的取消班次

这些词是什么意思 →

2 partial-capture days not counted.

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

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

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

What this route needs

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

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

16:00 has 45% of predictions within five minutes of the timetable, against 84% the rest of the day.

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

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, 18 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: not enough data
06:00: 100% of final predictions within five minutes of the timetable, 300 predictions, typically 1.8 min late
07:00: 55.5% of final predictions within five minutes of the timetable, 600 predictions, typically 3.2 min late
08:00: 93.7% of final predictions within five minutes of the timetable, 615 predictions, typically 1.9 min late
09:00: 80.5% of final predictions within five minutes of the timetable, 610 predictions, typically 2.9 min late
10:00: 83.9% of final predictions within five minutes of the timetable, 607 predictions, typically 1.8 min late
11:00: 91.1% of final predictions within five minutes of the timetable, 610 predictions, typically 1.5 min late
12:00: 97.7% of final predictions within five minutes of the timetable, 610 predictions, typically 0.5 min late
13:00: 95.1% of final predictions within five minutes of the timetable, 610 predictions, typically 0.8 min late
14:00: 84.3% of final predictions within five minutes of the timetable, 610 predictions, typically 1.3 min late
15:00: 82.7% of final predictions within five minutes of the timetable, 862 predictions, typically 1.1 min late
16:00: 44.5% of final predictions within five minutes of the timetable, 647 predictions, typically 5 min late
17:00: 78.8% of final predictions within five minutes of the timetable, 586 predictions, typically 1.2 min late
18:00: 81.3% of final predictions within five minutes of the timetable, 910 predictions, typically 2.1 min late
19:00: 75.8% of final predictions within five minutes of the timetable, 575 predictions, typically 2.9 min late
20:00: 99.5% of final predictions within five minutes of the timetable, 610 predictions, typically 2.5 min late
21:00: 87.5% of final predictions within five minutes of the timetable, 610 predictions, typically 2.2 min late
22:00: 84.3% of final predictions within five minutes of the timetable, 610 predictions, typically 1.8 min late
23:00: 92.4% of final predictions within five minutes of the timetable, 579 predictions, typically 1.3 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	07:00 · 16:00	3.2 min late · 5 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	16:00	45%	Operations, not the timetable
CaveatCoverage gap	All measured hours	100%	More observation, not a service change

Measurements

Predictions later than timetable · 16:00: Measured arrivals 647; Hours affected 1; Spread 14.5 min; Median delay 5 min; Suggested running time change 5 min
Predictions later than timetable · 07:00: Measured arrivals 600; Hours affected 1; Spread 10.9 min; Median delay 3.2 min; Suggested running time change 3.2 min
One hour has a lower prediction match · 16:00: 小时 16:00; 准点 44.5%; Measured arrivals 647; Shortfall 39.8 pts; Route median on time 84.3%
Coverage gap · All measured hours: 目标 99.5%; Trips with a matching position 99.5%; 运营日 5; Trips with a matching position 184; 时刻表班次 185

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

线路检查

How route 43 has been running

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

结论

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

83 in 100 eligible predictions were within 5 minutes of the timetable · 20,157 predictions checked

预测样本量: 样本较大

Based on 20,157 eligible provider predictions over 18 measured days, from 2026年10月6日 to 2026年11月3日.

Updated 2026年11月4日 12:32

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

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

16时–17时: 56 in 100 eligible predictions differed from the timetable by more than 5 minutes (647 predictions over 10 days).
7时–8时: 45 in 100 eligible predictions differed from the timetable by more than 5 minutes (600 predictions over 10 days).

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

各站预测差异

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

查看每个行程和日期

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

乘客想知道什么

现在有班次被取消吗？: 0 of 9检查未来4小时内从线路起终点开始的行程。这不是历史取消率。
排除数据缺口后，可能的未出车情况？: 1 of 185 checked trips need a closer look1 of 185 trips with enough public-feed evidence had no matching position over 7 days. 0 of 185 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 8.9 min (positive means later; negative means earlier)83 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
运营方的预测意味着需要等多久？: 目前还没有路线级别的结果达到数据依据的门槛。这并不表示没有出现过服务间隔。

时刻表变更检查

已发布时刻表：变更前后

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

Current published schedule began 2026年10月30日

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

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

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

之前

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

时刻表班次: 37
不同的预定站点: 63
已发布的不同路径: 2
已公布的服务时段: 6:05–23:44

Operator calendar-date records: 0 added · 2 removed

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

新时刻表

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

时刻表班次: 37
不同的预定站点: 63
已发布的不同路径: 2
已公布的服务时段: 6:05–23:44

Operator calendar-date records: 0 added · 2 removed

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

变更后服务有改善吗？

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

Still collecting: before has 11,187 arrivals over 10 days; after has 3,351 arrivals over 3 days. No improvement or decline is claimed yet.

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

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

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

这些数据无法证明的事

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

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

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

初步结果,已公布的数据

预测与时刻表相比如何?

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

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

与时刻表相差不超过5分钟: 83.2%
已核查的合格预测: 20,157
有数据的工作日: 18
第95百分位预测延误: 8.9 min late

Patterns by hour (18)

Patterns by hour (18)
小时	准点	中位数	第95百分位	数据证据
06:00	100.0%	1.8 min late	3.7 min late	300 · 10 days
07:00	55.5%	3.2 min late	14.1 min late	600 · 10 days
08:00	93.7%	1.9 min late	5.1 min late	615 · 10 days
09:00	80.5%	2.9 min late	6.8 min late	610 · 10 days
10:00	83.9%	1.8 min late	11.1 min late	607 · 10 days
11:00	91.1%	1.5 min late	6.5 min late	610 · 10 days
12:00	97.7%	0.5 min late	4 min late	610 · 10 days
13:00	95.1%	0.8 min late	3.3 min late	610 · 10 days
14:00	84.3%	1.3 min late	9.8 min late	610 · 10 days
15:00	82.7%	1.1 min late	6.2 min late	862 · 10 days
16:00	44.5%	5 min late	19.5 min late	647 · 10 days
17:00	78.8%	1.2 min late	8 min late	586 · 10 days
18:00	81.3%	2.1 min late	8.1 min late	910 · 10 days
19:00	75.8%	2.9 min late	9 min late	575 · 10 days
20:00	99.5%	2.5 min late	4.6 min late	610 · 10 days
21:00	87.5%	2.2 min late	6.2 min late	610 · 10 days
22:00	84.3%	1.8 min late	8.5 min late	610 · 10 days
23:00	92.4%	1.3 min late	10.6 min late	579 · 10 days

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

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

184 / 185 scheduled trips published at least one position across 5 service days (99.5%).

17:001 / 10 trips without a position90.0%
06:000 / 5 trips without a position100.0%
07:000 / 10 trips without a position100.0%
08:000 / 10 trips without a position100.0%
09:000 / 10 trips without a position100.0%
10:000 / 10 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 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

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

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

06:05– 06:24
Trip 9288030Vehicle position matchedFirst / last feed position: 5:47 a.m. EST / 6:26 a.m. EST; not actual start or end times.
07:00– 07:19
Trip 35181030Vehicle position matchedFirst / last feed position: 6:59 a.m. EST / 7:24 a.m. EST; not actual start or end times.
07:35– 07:54
Trip 21774030Vehicle position matchedFirst / last feed position: 7:46 a.m. EST / 8:06 a.m. EST; not actual start or end times.
08:06– 08:25
Trip 580030Vehicle position matchedFirst / last feed position: 8:02 a.m. EST / 9:18 a.m. EST; not actual start or end times.
08:36– 08:55
Trip 12630030Vehicle position matchedFirst / last feed position: 8:14 a.m. EST / 8:53 a.m. EST; not actual start or end times.
09:00– 09:22
Trip 32430030Vehicle position matchedFirst / last feed position: 9:09 a.m. EST / 9:25 a.m. EST; not actual start or end times.
09:35– 09:52
Trip 30061030Vehicle position matchedFirst / last feed position: 9:26 a.m. EST / 10:07 a.m. EST; not actual start or end times.
10:00– 10:22
Trip 3098030Explicit notice: CANCELEDVehicle position matchedFirst / last feed position: 10:00 a.m. EST / 10:37 a.m. EST; not actual start or end times.
10:35– 10:52
Trip 17969030Vehicle position matchedFirst / last feed position: 10:18 a.m. EST / 11:00 a.m. EST; not actual start or end times.
11:00– 11:23
Trip 20144030Vehicle position matchedFirst / last feed position: 11:01 a.m. EST / 11:20 a.m. EST; not actual start or end times.
11:35– 11:51
Trip 22033030Vehicle position matchedFirst / last feed position: 11:21 a.m. EST / 12:01 p.m. EST; not actual start or end times.
12:00– 12:23
Trip 4520030Vehicle position matchedFirst / last feed position: 12:02 p.m. EST / 12:23 p.m. EST; not actual start or end times.

· Open all evidence for this day

线路 43: Karsh ⇄ Greenboro

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