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

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

STO 线路 93: Masson

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

—

No retained notice returned; this does not prove zero cancellations.

Trips needing investigation

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

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

49 with position · 1 to investigate · 10 excluded · 60 scheduled trips

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

Coverage, exclusions and sources

10 scheduled trips were excluded from the position check for feed or identity gaps.

Published position coverage: 49 / 60 (81.7%). 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日 20:38

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

75.8%

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

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

The hours we have evidence for

5时99% · 158 predictions · 7 days
6时95% · 662 predictions · 7 days
7时91% · 516 predictions · 6 days
8时88% · 187 predictions · 6 days
15时95% · 459 predictions · 9 days
16时62% · 664 predictions · 10 days
17时80% · 546 predictions · 9 days
18时59% · 217 predictions · 7 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月5日

6 partial-capture days not counted.

What about time of day?

8 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日: 21 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月12日.

数值与解读

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

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

公交车扎堆到站
时段	已检查的配对	扎堆	间隔过长
早高峰(上午 6 点至 9 点)	1,672	0% (1)	0% (0)
下午高峰(下午3点至6点)	2,109	2% (37)	4% (92)
晚间（晚上 6 点至 10 点）	325	0% (0)	19% (61)

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

这条路线最慢的路段

Slowest: BANK/QUEEN to PLACE d'ACCUEIL est, 8.5 km/h actual against 10.8 km/h planned.

这条路线最慢的路段
起点	到	距离	计划速度	实际速度	已测量的行程	缓慢行程
BANK/QUEEN	PLACE d'ACCUEIL est	1.4 km	10.8 km/h	8.5 km/h	63	17%
PLACE d'ACCUEIL est	Station MONTCALM bretelle dir nord #2	1.3 km	9.8 km/h	10.5 km/h	79	0%
PLACE d'ACCUEIL ouest	STATION LYON	1.6 km	16.6 km/h	13 km/h	48	25%
de l'ARÉNA/LOMBARD	PARC-O-BUS GEORGES/ROUTE 148	2 km	23.8 km/h	14.5 km/h	48	50%
PARC-O-BUS GEORGES/ROUTE 148	de l'ARÉNA/LOMBARD arrivée	2.1 km	20.5 km/h	17.6 km/h	78	15%
Station CASINO #2	Station LAC LEAMY #2	800 m	17.5 km/h	17.9 km/h	83	7%
du PROGRÈS/de GENÈVE	de NEUVILLE/de CHAVILLE	2.8 km	19.3 km/h	18.6 km/h	42	0%
Station MONTCALM bretelle dir sud #1	PLACE d'ACCUEIL ouest	2 km	17.3 km/h	19.4 km/h	54	0%

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

测量方式 →

此线路的取消班次

这些词是什么意思 →

6 partial-capture days not counted.

过去四周内，这条线路没有计入的取消班次。我们无法核实的通知会列在下方。

Did not come (no bus seen, no notice), last 7 days: 1 of 50 trips we could check.

这条线路通常何时繁忙

依据 STO 公交车报告的载客水平，统计最近八周的数据。如果有读数的班次中至少一半达到站位或更拥挤，该时段就标为通常拥挤。

这条线路通常何时繁忙	工作日	星期六	每周日
早上6点前	通常有座位0% of 31 trips	读数不足	读数不足
上午 6 点至 9 点	通常很拥挤68.8% of 144 trips	读数不足	读数不足
上午9点至下午3点	通常有座位7.7% of 13 trips	读数不足	读数不足
下午3点至6点	通常有座位23.9% of 188 trips	读数不足	读数不足
晚上 6 点至 10 点	通常有座位0% of 44 trips	读数不足	读数不足
晚上10点以后	读数不足	读数不足	读数不足

Based on 56 computed days.

来源：STO 公开实时车辆数据中的载客状态。STO 根据每辆公交车的载重传感器设定该状态（有座位：满载率低于 60%，有站位：低于 90%，已满：高于 90%）。
每个行程在每个时段只计一次,按其报告的最高载客量计算。
空车报告不计入，因为旧记录无法区分空车和没有传感器的车。
某个时段至少要有 12 趟行程，且分布在至少 4 个不同的日子，才会显示任何内容。节假日按其所属的星期几计算。

打开带日期的预测分析

结论

What this route needs

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

Wide prediction spread 17:00: the 95th percentile is 29.6 min later than the median.

18:00 has 59% of predictions within five minutes of the timetable, against 90% the rest of the day.

Scenario: 3 min more running time on 8 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, 8 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: 99.4% of final predictions within five minutes of the timetable, 158 predictions, typically 1.4 min late
06:00: 95.3% of final predictions within five minutes of the timetable, 662 predictions, typically 0.7 min late
07:00: 91.3% of final predictions within five minutes of the timetable, 516 predictions, typically 2.1 min late
08:00: 88.2% of final predictions within five minutes of the timetable, 187 predictions, typically 0.2 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: 94.8% of final predictions within five minutes of the timetable, 459 predictions, typically 0.1 min late
16:00: 62.2% of final predictions within five minutes of the timetable, 664 predictions, typically 3.2 min late
17:00: 79.5% of final predictions within five minutes of the timetable, 546 predictions, typically 0.8 min late. Provider predictions have a wide spread.
18:00: 59.4% of final predictions within five minutes of the timetable, 217 predictions, typically 3.2 min late
19:00: not enough data
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
prediction spread of 20 min or more between the 95th percentile and median

Findings
What	时间	已测量	Scenario or next investigation
ProblemPredictions later than timetable	16:00 · 18:00	3.2 min late	More running time
ProblemWide prediction spread	17:00	29.6 min swing	Operations, not the timetable
ProblemOne hour has a lower prediction match	18:00	59%	Operations, not the timetable

Measurements

Predictions later than timetable · 16:00: Measured arrivals 664; Hours affected 1; Spread 17.5 min; Median delay 3.2 min; Suggested running time change 3.2 min
Predictions later than timetable · 18:00: Measured arrivals 217; Hours affected 1; Spread 11.5 min; Median delay 3.2 min; Suggested running time change 3.2 min
Wide prediction spread · 17:00: Measured arrivals 546; Hours affected 1; Spread 29.6 min; Median delay 0.8 min; Suggested running time change 0.8 min
One hour has a lower prediction match · 18:00: 小时 18:00; 准点 59.4%; Measured arrivals 217; Shortfall 30.4 pts; Route median on time 89.8%

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

线路检查

How route 93 has been running

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

结论

服务方的预测常与时刻表不同；实际到达时间没有经过独立测量。

76 in 100 eligible predictions were within 5 minutes of the timetable · 6,918 predictions checked

预测样本量: 样本较大

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

Updated 2026年11月4日 20:32

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

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

18时–19时: 41 in 100 eligible predictions differed from the timetable by more than 5 minutes (217 predictions over 7 days).
16时–17时: 38 in 100 eligible predictions differed from the timetable by more than 5 minutes (664 predictions over 10 days).

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

各站预测差异

STATION LYON
57 in 100 eligible predictions differed from the timetable by more than 5 minutes (61 predictions over 14 days).
打开此站点
de l'ARÉNA/LOMBARD arrivée
52 in 100 eligible predictions differed from the timetable by more than 5 minutes (96 predictions over 18 days).
打开此站点
ROUTE 148/LOMBARD
49 in 100 eligible predictions differed from the timetable by more than 5 minutes (99 predictions over 18 days).
打开此站点
ROUTE 148/GUY-DUBUC
48 in 100 eligible predictions differed from the timetable by more than 5 minutes (98 predictions over 18 days).
打开此站点

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

查看每个行程和日期

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

乘客想知道什么

现在有班次被取消吗？: 没有实时取消情况的答案STO’s live trip-update feed did not answer this check. That is a feed gap. It does not mean zero cancellations, and it is not proof of a cancellation. Open the evidence to see the schedule, retained explicit cancellation notices, and every labelled data gap.
排除数据缺口后，可能的未出车情况？: 1 of 50 checked trips need a closer look1 of 50 trips with enough public-feed evidence had no matching position over 7 days. 10 of 60 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 13.6 min (positive means later; negative means earlier)76 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
运营方的预测意味着需要等多久？: 目前还没有路线级别的结果达到数据依据的门槛。这并不表示没有出现过服务间隔。

时刻表变更检查

已发布时刻表：变更前后

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

Current published schedule began 2026年11月2日

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

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

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

之前

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

时刻表班次: 0
不同的预定站点: 0
已发布的不同路径: 0
已公布的服务时段: —–—

数据源指纹: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

新时刻表

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

时刻表班次: 12
不同的预定站点: 96
已发布的不同路径: 2
已公布的服务时段: 5:45–18:25

Operator calendar-date records: 1 added · 0 removed

数据源指纹: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

变更后服务有改善吗？

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

Still collecting: before has 3,849 arrivals over 10 days; after has 379 arrivals over 2 days. No improvement or decline is claimed yet.

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

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

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

这些数据无法证明的事

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

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

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

初步结果,已公布的数据

预测与时刻表相比如何?

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

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

与时刻表相差不超过5分钟: 75.8%
已核查的合格预测: 6,918
有数据的工作日: 17
第95百分位预测延误: 13.6 min late

Patterns by hour (9)

Patterns by hour (9)
小时	准点	中位数	第95百分位	数据证据
05:00	99.4%	1.4 min late	3.6 min late	158 · 7 days
06:00	95.3%	0.7 min late	4.6 min late	662 · 7 days
07:00	91.3%	2.1 min late	5.5 min late	516 · 6 days
08:00	88.2%	0.2 min late	7.2 min late	187 · 6 days
14:00	100.0%	0 min late	2.2 min late	20 · 7 days
15:00	94.8%	0.1 min late	3.9 min late	459 · 9 days
16:00	62.2%	3.2 min late	20.7 min late	664 · 10 days
17:00	79.5%	0.8 min late	30.4 min late	546 · 9 days
18:00	59.4%	3.2 min late	14.7 min late	217 · 7 days

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

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

49 / 60 scheduled trips published at least one position across 5 service days (81.7%).

07:002 / 5 trips without a position60.0%
17:002 / 5 trips without a position60.0%
06:005 / 15 trips without a position66.7%
05:001 / 5 trips without a position80.0%
16:001 / 10 trips without a position90.0%
14: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 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

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

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

05:45– 06:56
Trip sto:63295445Insufficient coverage or identity; outcome unknown
06:05– 07:16
Trip sto:63294631Insufficient coverage or identity; outcome unknown
06:25– 07:38
Trip sto:63290299Insufficient coverage or identity; outcome unknown
06:55– 08:15
Trip sto:63295713Insufficient coverage or identity; outcome unknown
07:25– 08:45
Trip sto:63294677Insufficient coverage or identity; outcome unknown
14:50– 15:56
Trip sto:63295856Vehicle position matchedFirst / last feed position: 2:49 p.m. EST / 3:53 p.m. EST; not actual start or end times.
15:10– 16:16
Trip sto:63296180Vehicle position matchedFirst / last feed position: 3:08 p.m. EST / 4:12 p.m. EST; not actual start or end times.
15:30– 16:37
Trip sto:63295733Vehicle position matchedFirst / last feed position: 3:27 p.m. EST / 4:41 p.m. EST; not actual start or end times.
15:50– 16:57
Trip sto:63295877Vehicle position matchedFirst / last feed position: 3:57 p.m. EST / 5:10 p.m. EST; not actual start or end times.
16:20– 17:27
Trip sto:63295870No matching position; investigate, not a confirmed cancellation
16:50– 17:55
Trip sto:63290292Vehicle position matchedFirst / last feed position: 5:19 p.m. EST / 6:23 p.m. EST; not actual start or end times.
17:20– 18:25
Trip sto:63295384Vehicle position matchedFirst / last feed position: 5:32 p.m. EST / 6:32 p.m. EST; not actual start or end times.