Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.

Route 25

Trip service evidence

Open the totals. See the day, scheduled trip, public feed vehicle ID, and the data gaps that were excluded.

Verifiable timetables for 25 of 30 days

Each date uses an official timetable retained before that service day began. Days without that timetable are not counted as zero trips or as no-shows.

See excluded dates

2026-08-20, 2026-08-21, 2026-08-22, 2026-08-23, 2026-08-24

The JSON download includes source versions, checksums and retrieval times.

Open the route scorecard and map Open source data (JSON)Download trip evidence (CSV)

Operator-confirmed cancellations right now

Only trips explicitly marked CANCELED or DELETED by the current operator feed appear here. This is a current snapshot, not a historical cancellation rate.

OC Transpo live trip updates checked Sep 19, 2026, 3:33 p.m..

The current feed does not explicitly mark a trip cancelled or deleted.

Operator cancellation notices saved for this period

These rows record when the operator published CANCELED or DELETED. A notice does not prove the trip stayed cancelled; any later matching vehicle observation is flagged below. Collection starts with this feature’s release, so an empty earlier day means “not retained,” not zero cancellations.

135601002026-09-18 · Cancelled by the operator · None publishedSep 18, 2026, 12:48 p.m.
230291002026-09-16 · Cancelled by the operator · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Sep 16, 2026, 8:33 a.m.
205540302026-09-15 · Cancelled by the operator · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Sep 15, 2026, 8:31 a.m.
41460302026-09-15 · Cancelled by the operator · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Sep 15, 2026, 8:05 p.m.
119870202026-09-14 · Cancelled by the operator · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Sep 14, 2026, 7:17 p.m.
205540202026-09-14 · Cancelled by the operator · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Sep 14, 2026, 8:32 a.m.
114530102026-09-13 · Cancelled by the operator · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Sep 13, 2026, 8:44 p.m.
107640702026-09-12 · Cancelled by the operator · None publishedSep 12, 2026, 3:24 p.m.
180540702026-09-12 · Cancelled by the operator · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Sep 12, 2026, 2:57 p.m.
119870502026-09-10 · Cancelled by the operator · None publishedSep 10, 2026, 7:27 p.m.
142990502026-09-10 · Cancelled by the operator · None publishedSep 10, 2026, 8:33 p.m.
195630502026-09-10 · Cancelled by the operator · None publishedSep 10, 2026, 6:49 p.m.
26310502026-09-10 · Cancelled by the operator · None publishedSep 10, 2026, 8:36 p.m.
36610502026-09-10 · Cancelled by the operator · None publishedSep 10, 2026, 5:40 p.m.
92320502026-09-10 · Cancelled by the operator · None publishedSep 10, 2026, 10:45 a.m.
277330402026-09-09 · Cancelled by the operator · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Sep 9, 2026, 6:17 p.m.
171890302026-09-08 · Cancelled by the operator · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Sep 8, 2026, 3:26 p.m.
79740902026-09-05 · Cancelled by the operator · None publishedSep 5, 2026, 12:24 p.m.
285910602026-09-04 · Cancelled by the operator · None publishedSep 4, 2026, 11:45 p.m.
95810402026-09-02 · Cancelled by the operator · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Sep 2, 2026, 11:19 a.m.
15150302026-09-01 · Cancelled by the operator · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Sep 1, 2026, 8:09 p.m.
91950802026-08-30 · Cancelled by the operator · None publishedAug 30, 2026, 9:26 p.m.
182251302026-08-28 · Cancelled by the operator · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Aug 28, 2026, 7:40 p.m.

Open a service day to load its exact settled-arrival timing. The weekly and monthly views keep trip visibility, feed gaps, and vehicle IDs fast instead of making every rider wait for a large archive scan.

Service date	Scheduled trips	Trips with a position	No-position candidates	Excluded for feed gaps	Position coverage	Public feed vehicle IDs	Arrivals checked	Arrivals within 5 minutes	Average delay (+ late, − early)	How late the worst 5 in 100 were
Sep 18, 2026123 of 123 trip windows had enough operator-feed evidence	123	0	123	0	0%	0	Open this day	Open this day	Open this day	Open this day
Sep 17, 2026123 of 123 trip windows had enough operator-feed evidence	123	122	1	0	99.2%	31	Open this day	Open this day	Open this day	Open this day
Sep 16, 2026123 of 123 trip windows had enough operator-feed evidence	123	123	0	0	100%	31	Open this day	Open this day	Open this day	Open this day
Sep 15, 2026121 of 123 trip windows had enough operator-feed evidence	123	123	0	0	100%	31	Open this day	Open this day	Open this day	Open this day
Sep 14, 2026123 of 123 trip windows had enough operator-feed evidence	123	123	0	0	100%	32	Open this day	Open this day	Open this day	Open this day
Sep 13, 202667 of 67 trip windows had enough operator-feed evidence	67	67	0	0	100%	11	Open this day	Open this day	Open this day	Open this day
Sep 12, 202675 of 78 trip windows had enough operator-feed evidence	78	77	1	0	98.7%	22	Open this day	Open this day	Open this day	Open this day
Sep 11, 2026123 of 123 trip windows had enough operator-feed evidence	123	123	0	0	100%	32	Open this day	Open this day	Open this day	Open this day
Sep 10, 2026123 of 123 trip windows had enough operator-feed evidence	123	3	120	0	2.4%	1	Open this day	Open this day	Open this day	Open this day
Sep 9, 2026123 of 123 trip windows had enough operator-feed evidence	123	123	0	0	100%	30	Open this day	Open this day	Open this day	Open this day
Sep 8, 2026123 of 123 trip windows had enough operator-feed evidence	123	122	1	0	99.2%	30	Open this day	Open this day	Open this day	Open this day
Sep 7, 202663 of 67 trip windows had enough operator-feed evidence	67	2	61	4	3%	2	Open this day	Open this day	Open this day	Open this day
Sep 6, 202663 of 67 trip windows had enough operator-feed evidence	67	2	61	4	3%	2	Open this day	Open this day	Open this day	Open this day
Sep 5, 202676 of 78 trip windows had enough operator-feed evidence	78	0	76	2	0%	0	Open this day	Open this day	Open this day	Open this day
Sep 4, 2026113 of 123 trip windows had enough operator-feed evidence	123	3	110	10	2.4%	3	Open this day	Open this day	Open this day	Open this day
Sep 3, 202612 of 123 trip windows had enough operator-feed evidence	123	109	0	14	88.6%	29	Open this day	Open this day	Open this day	Open this day
Sep 2, 202613 of 123 trip windows had enough operator-feed evidence	123	103	0	20	83.7%	30	Open this day	Open this day	Open this day	Open this day
Sep 1, 202642 of 123 trip windows had enough operator-feed evidence	123	123	0	0	100%	31	Open this day	Open this day	Open this day	Open this day
Aug 31, 202656 of 123 trip windows had enough operator-feed evidence	123	123	0	0	100%	30	Open this day	Open this day	Open this day	Open this day
Aug 30, 202657 of 67 trip windows had enough operator-feed evidence	67	66	1	0	98.5%	11	Open this day	Open this day	Open this day	Open this day
Aug 29, 202642 of 63 trip windows had enough operator-feed evidence	63	57	0	6	90.5%	17	Open this day	Open this day	Open this day	Open this day
Aug 28, 20263 of 123 trip windows had enough operator-feed evidence	123	47	0	76	38.2%	23	Open this day	Open this day	Open this day	Open this day
Aug 27, 202615 of 123 trip windows had enough operator-feed evidence	123	69	0	54	56.1%	24	Open this day	Open this day	Open this day	Open this day
Aug 26, 20260 of 123 trip windows had enough operator-feed evidence	123	0	0	123	0%	0	Open this day	Open this day	Open this day	Open this day
Aug 25, 202644 of 123 trip windows had enough operator-feed evidence	123	80	0	43	65%	28	Open this day	Open this day	Open this day	Open this day

Scheduled-trip detail

Choose a date in the table to see every scheduled trip. Until then, the list focuses on cases that need investigation.

Trip	Scheduled service	What the public evidence says	Vehicle ID(s) published by the feed	First / last observed	Feed evidence during this trip
168890602026-09-18	04:25–04:52	No matching position; investigate	None published	—	10 of 12 expected snapshots · 83.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
180890602026-09-18	04:55–05:22	No matching position; investigate	None published	—	11 of 12 expected snapshots · 91.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
159900602026-09-18	05:25–05:53	No matching position; investigate	None published	—	12 of 12 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
41010602026-09-18	05:38–06:25	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
82600602026-09-18	05:41–06:15	No matching position; investigate	None published	—	13 of 13 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
209780602026-09-18	05:55–06:45	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
152890602026-09-18	05:57–06:45	No matching position; investigate	None published	—	15 of 16 expected snapshots · 93.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
116740602026-09-18	06:10–07:02	No matching position; investigate	None published	—	15 of 17 expected snapshots · 88.2%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
195010602026-09-18	06:25–07:19	No matching position; investigate	None published	—	14 of 17 expected snapshots · 82.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
234300602026-09-18	06:29–07:20	No matching position; investigate	None published	—	14 of 17 expected snapshots · 82.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
34710602026-09-18	06:40–07:36	No matching position; investigate	None published	—	15 of 18 expected snapshots · 83.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
6770602026-09-18	06:54–07:51	No matching position; investigate	None published	—	15 of 18 expected snapshots · 83.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
110650602026-09-18	06:57–07:49	No matching position; investigate	None published	—	13 of 17 expected snapshots · 76.5%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
211670602026-09-18	07:10–08:07	No matching position; investigate	None published	—	15 of 18 expected snapshots · 83.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
64860602026-09-18	07:25–08:23	No matching position; investigate	None published	—	17 of 18 expected snapshots · 94.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
98880602026-09-18	07:25–08:20	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
225640602026-09-18	07:41–08:39	No matching position; investigate	None published	—	17 of 18 expected snapshots · 94.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
150910602026-09-18	07:55–08:50	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
29030602026-09-18	07:55–08:53	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
93830602026-09-18	08:10–09:07	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
10400602026-09-18	08:25–09:21	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
205540602026-09-18	08:27–09:19	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
223090602026-09-18	08:40–09:35	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
230290602026-09-18	08:55–09:50	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
150610602026-09-18	08:57–09:49	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
49690602026-09-18	09:10–10:05	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
112140602026-09-18	09:12–10:02	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
102750602026-09-18	09:25–10:20	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
154780602026-09-18	09:26–10:16	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
106630602026-09-18	09:40–10:30	No matching position; investigate	None published	—	17 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
113470602026-09-18	09:40–10:35	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
91880602026-09-18	09:54–10:44	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
160710602026-09-18	09:55–10:50	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
145960602026-09-18	10:09–10:59	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
55530602026-09-18	10:10–11:05	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
37390602026-09-18	10:24–11:14	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
154080602026-09-18	10:25–11:20	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
207840602026-09-18	10:39–11:30	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
92320602026-09-18	10:40–11:35	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
160490602026-09-18	10:54–11:45	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
146460602026-09-18	10:55–11:50	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
126430602026-09-18	11:09–12:02	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
163700602026-09-18	11:10–12:05	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
186930602026-09-18	11:24–12:17	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
107090602026-09-18	11:25–12:20	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
49700602026-09-18	11:39–12:33	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
12650602026-09-18	11:40–12:35	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
154760602026-09-18	11:54–12:48	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
31900602026-09-18	11:55–12:50	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
222650602026-09-18	12:09–13:03	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
131500602026-09-18	12:10–13:05	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
232830602026-09-18	12:24–13:18	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
43710602026-09-18	12:25–13:20	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
26420602026-09-18	12:39–13:33	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
224240602026-09-18	12:40–13:35	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
15590602026-09-18	12:54–13:48	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
74250602026-09-18	12:55–13:50	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
104450602026-09-18	13:09–14:05	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
121280602026-09-18	13:09–14:04	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
150540602026-09-18	13:24–14:19	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
169410602026-09-18	13:25–14:21	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
11450602026-09-18	13:39–14:34	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
19890602026-09-18	13:40–14:36	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
50970602026-09-18	13:54–14:49	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
13210602026-09-18	13:55–14:52	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
99770602026-09-18	14:09–15:05	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
57190602026-09-18	14:10–15:08	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
45580602026-09-18	14:25–15:23	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
89660602026-09-18	14:25–15:21	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
169130602026-09-18	14:31–14:49	No matching position; investigate	None published	—	9 of 10 expected snapshots · 90%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
14060602026-09-18	14:40–15:39	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
169590602026-09-18	14:40–15:38	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
56040602026-09-18	14:55–15:55	No matching position; investigate	None published	—	19 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
142630602026-09-18	15:10–16:10	No matching position; investigate	None published	—	19 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
1680602026-09-18	15:12–16:15	No matching position; investigate	None published	—	19 of 19 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
173520602026-09-18	15:26–16:26	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
36600602026-09-18	15:27–16:30	No matching position; investigate	None published	—	19 of 19 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
188980602026-09-18	15:40–16:40	No matching position; investigate	None published	—	19 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
176350602026-09-18	15:42–16:45	No matching position; investigate	None published	—	19 of 19 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
211050602026-09-18	15:55–16:55	No matching position; investigate	None published	—	19 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
126500602026-09-18	15:59–17:02	No matching position; investigate	None published	—	19 of 19 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
68400602026-09-18	16:14–17:17	No matching position; investigate	None published	—	19 of 19 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
6780602026-09-18	16:25–17:22	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
105730602026-09-18	16:30–17:31	No matching position; investigate	None published	—	19 of 19 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
73750602026-09-18	16:40–17:37	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
51020602026-09-18	16:44–17:45	No matching position; investigate	None published	—	19 of 19 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
128830602026-09-18	16:55–17:52	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
57240602026-09-18	16:59–17:58	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
133640602026-09-18	17:10–18:07	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
184120602026-09-18	17:12–18:08	No matching position; investigate	None published	—	17 of 18 expected snapshots · 94.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
106100602026-09-18	17:25–18:21	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
167530602026-09-18	17:26–18:22	No matching position; investigate	None published	—	17 of 18 expected snapshots · 94.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
195630602026-09-18	17:40–18:36	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
195330602026-09-18	17:41–18:35	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
155540602026-09-18	17:56–18:49	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
11690602026-09-18	18:10–19:05	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
87530602026-09-18	18:11–19:04	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
126890602026-09-18	18:25–19:18	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
190560602026-09-18	18:40–19:35	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
36610602026-09-18	18:40–19:33	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
224630602026-09-18	19:09–20:00	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
164360602026-09-18	19:10–20:01	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
119870602026-09-18	19:39–20:29	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
194200602026-09-18	19:40–20:31	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
114860602026-09-18	20:06–20:55	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
63120602026-09-18	20:10–21:01	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
106210602026-09-18	20:36–21:25	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
41460602026-09-18	20:40–21:31	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
142990602026-09-18	21:06–21:55	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
191850602026-09-18	21:10–21:58	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
183800602026-09-18	21:36–22:23	No matching position; investigate	None published	—	15 of 16 expected snapshots · 93.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
217980602026-09-18	21:40–22:28	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
129960602026-09-18	22:05–22:52	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
82640602026-09-18	22:10–22:57	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
107970602026-09-18	22:34–23:17	No matching position; investigate	None published	—	15 of 15 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
26310602026-09-18	22:40–23:26	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
100760602026-09-18	23:03–23:43	No matching position; investigate	None published	—	14 of 14 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
90980602026-09-18	23:10–23:35	No matching position; investigate	None published	—	12 of 11 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
189420602026-09-18	23:32–24:12	No matching position; investigate	None published	—	14 of 14 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
231570602026-09-18	23:40–24:03	No matching position; investigate	None published	—	11 of 11 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
223280602026-09-18	24:17–24:40	No matching position; investigate	None published	—	11 of 11 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
185560602026-09-18	24:22–24:52	No matching position; investigate	None published	—	12 of 12 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
185660602026-09-18	24:52–25:22	No matching position; investigate	None published	—	12 of 12 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
119871102026-09-17	19:39–20:29	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
107640702026-09-12	14:27–15:11	No matching position; investigate	None published	—	15 of 15 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
203850502026-09-10	04:25–04:52	No matching position; investigate	None published	—	11 of 12 expected snapshots · 91.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
222870502026-09-10	04:55–05:22	No matching position; investigate	None published	—	11 of 12 expected snapshots · 91.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
193460502026-09-10	05:25–05:53	No matching position; investigate	None published	—	11 of 12 expected snapshots · 91.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
14330502026-09-10	05:38–06:25	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
65800502026-09-10	05:41–06:15	No matching position; investigate	None published	—	13 of 13 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
258770502026-09-10	05:55–06:45	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
184590502026-09-10	05:57–06:45	No matching position; investigate	None published	—	15 of 16 expected snapshots · 93.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
107780502026-09-10	06:10–07:02	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
240690502026-09-10	06:25–07:19	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
289340502026-09-10	06:29–07:20	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
6570502026-09-10	06:40–07:36	No matching position; investigate	None published	—	17 of 18 expected snapshots · 94.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
173500502026-09-10	06:54–07:51	No matching position; investigate	None published	—	17 of 18 expected snapshots · 94.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
99920502026-09-10	06:57–07:49	No matching position; investigate	None published	—	15 of 17 expected snapshots · 88.2%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
261390502026-09-10	07:10–08:07	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
43610502026-09-10	07:25–08:23	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
85240502026-09-10	07:25–08:20	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
278520502026-09-10	07:41–08:39	No matching position; investigate	None published	—	17 of 18 expected snapshots · 94.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
154550502026-09-10	07:55–08:53	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
188220502026-09-10	07:55–08:50	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
79200502026-09-10	08:10–09:07	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
147200502026-09-10	08:25–09:21	No matching position; investigate	None published	—	18 of 18 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
253400502026-09-10	08:27–09:19	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
275350502026-09-10	08:40–09:35	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
284240502026-09-10	08:55–09:50	No matching position; investigate	None published	—	18 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
183150502026-09-10	08:57–09:49	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.

What these labels mean

Trip seen in the feed: A public vehicle observation overlaps this trip’s scheduled window. IDs match exactly, or an OC numeric timetable suffix is reconciled to one unique live trip on this route and date. Both trip IDs and the matching rule are included in the download.
Missing position to investigate: No public vehicle position matched the scheduled trip, and that trip’s own scheduled window had at least 75% of the expected operator-feed snapshots with observations near both ends. This needs investigation and is not proof of cancellation.
Missing data, not a missing bus: The trip window lacks enough operator-specific archive coverage, or a live trip ID cannot be assigned to one unique scheduled trip. It is excluded from missing-service counts.
Public vehicle identifier: An identifier published by the realtime feed. It may change and is not necessarily a verified physical fleet number.
Operator-confirmed cancellation: Historical cancellation is published only when a retained operator trip update explicitly marks it cancelled or deleted. Position absence alone is never relabelled as cancellation.
Which timetable was used?: Each date uses the latest retained official timetable fetched before that Toronto service day began. Days without such a timetable are not counted as zero service or as no-shows. Source version IDs, checksums and fetch times are included in the JSON download.