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

Route 45

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, 4:55 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.

120531002026-09-18 · Cancelled by the operator · None publishedSep 18, 2026, 8:51 a.m.
123631002026-09-18 · Cancelled by the operator · None publishedSep 18, 2026, 8:51 a.m.
50461002026-09-18 · Cancelled by the operator · None publishedSep 18, 2026, 9:14 a.m.
541002026-09-18 · Cancelled by the operator · None publishedSep 18, 2026, 9:03 a.m.
110501102026-09-17 · 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 17, 2026, 3:03 p.m.
21801102026-09-17 · 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 17, 2026, 8:49 a.m.
27031102026-09-17 · 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 17, 2026, 6:52 a.m.
27701102026-09-17 · 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 17, 2026, 8:49 a.m.
48821102026-09-17 · 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 17, 2026, 3:03 p.m.
86841102026-09-17 · 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 17, 2026, 6:52 a.m.
151281002026-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:21 a.m.
21801002026-09-16 · Cancelled by the operator · None publishedSep 16, 2026, 9:18 a.m.
27701002026-09-16 · Cancelled by the operator · None publishedSep 16, 2026, 9:29 a.m.
63441002026-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:21 a.m.
121550302026-09-15 · Cancelled by the operator · None publishedSep 15, 2026, 8:36 a.m.
151280302026-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, 7:34 a.m.
159480302026-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:36 a.m.
63440302026-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, 7:34 a.m.
151280202026-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:53 a.m.
63440202026-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:53 a.m.
116440702026-09-12 · Cancelled by the operator · None publishedSep 12, 2026, 11:22 a.m.
132990702026-09-12 · Cancelled by the operator · None publishedSep 12, 2026, 12:12 p.m.
173570702026-09-12 · Cancelled by the operator · None publishedSep 12, 2026, 11:42 a.m.
184240702026-09-12 · Cancelled by the operator · None publishedSep 12, 2026, 11:52 a.m.
50620702026-09-12 · Cancelled by the operator · None publishedSep 12, 2026, 11:12 a.m.
72890702026-09-12 · Cancelled by the operator · None publishedSep 12, 2026, 12:22 p.m.
151280502026-09-10 · Cancelled by the operator · None publishedSep 10, 2026, 8:39 a.m.
214800502026-09-10 · Cancelled by the operator · None publishedSep 10, 2026, 6:58 a.m.
29570502026-09-10 · Cancelled by the operator · None publishedSep 10, 2026, 6:47 a.m.
47550502026-09-10 · Cancelled by the operator · None publishedSep 10, 2026, 7:35 a.m.
63440502026-09-10 · Cancelled by the operator · None publishedSep 10, 2026, 9:09 a.m.
92500502026-09-10 · Cancelled by the operator · None publishedSep 10, 2026, 7:35 a.m.
41590402026-09-09 · Cancelled by the operator · None publishedSep 9, 2026, 9:13 a.m.
196410902026-09-05 · Cancelled by the operator · None publishedSep 5, 2026, 7:28 a.m.
278150902026-09-05 · Cancelled by the operator · None publishedSep 5, 2026, 7:28 a.m.
29110902026-09-05 · Cancelled by the operator · None publishedSep 5, 2026, 7:28 a.m.
66860902026-09-05 · Cancelled by the operator · None publishedSep 5, 2026, 7:28 a.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, 2026143 of 146 trip windows had enough operator-feed evidence	146	0	143	3	0%	0	Open this day	Open this day	Open this day	Open this day
Sep 17, 2026145 of 146 trip windows had enough operator-feed evidence	146	145	1	0	99.3%	25	Open this day	Open this day	Open this day	Open this day
Sep 16, 2026145 of 146 trip windows had enough operator-feed evidence	146	145	1	0	99.3%	22	Open this day	Open this day	Open this day	Open this day
Sep 15, 2026137 of 146 trip windows had enough operator-feed evidence	146	141	3	2	96.6%	22	Open this day	Open this day	Open this day	Open this day
Sep 14, 2026145 of 146 trip windows had enough operator-feed evidence	146	146	0	0	100%	21	Open this day	Open this day	Open this day	Open this day
Sep 13, 202678 of 86 trip windows had enough operator-feed evidence	86	86	0	0	100%	16	Open this day	Open this day	Open this day	Open this day
Sep 12, 202681 of 88 trip windows had enough operator-feed evidence	88	76	12	0	86.4%	13	Open this day	Open this day	Open this day	Open this day
Sep 11, 2026144 of 146 trip windows had enough operator-feed evidence	146	146	0	0	100%	21	Open this day	Open this day	Open this day	Open this day
Sep 10, 2026145 of 146 trip windows had enough operator-feed evidence	146	13	132	1	8.9%	1	Open this day	Open this day	Open this day	Open this day
Sep 9, 2026144 of 146 trip windows had enough operator-feed evidence	146	144	2	0	98.6%	21	Open this day	Open this day	Open this day	Open this day
Sep 8, 2026144 of 146 trip windows had enough operator-feed evidence	146	140	6	0	95.9%	20	Open this day	Open this day	Open this day	Open this day
Sep 7, 202676 of 86 trip windows had enough operator-feed evidence	86	1	75	10	1.2%	1	Open this day	Open this day	Open this day	Open this day
Sep 6, 202676 of 86 trip windows had enough operator-feed evidence	86	1	76	9	1.2%	1	Open this day	Open this day	Open this day	Open this day
Sep 5, 202675 of 88 trip windows had enough operator-feed evidence	88	2	73	13	2.3%	2	Open this day	Open this day	Open this day	Open this day
Sep 4, 2026134 of 146 trip windows had enough operator-feed evidence	146	3	131	12	2.1%	2	Open this day	Open this day	Open this day	Open this day
Sep 3, 202621 of 146 trip windows had enough operator-feed evidence	146	65	0	81	44.5%	16	Open this day	Open this day	Open this day	Open this day
Sep 2, 202627 of 146 trip windows had enough operator-feed evidence	146	87	0	59	59.6%	17	Open this day	Open this day	Open this day	Open this day
Sep 1, 202664 of 146 trip windows had enough operator-feed evidence	146	126	1	19	86.3%	20	Open this day	Open this day	Open this day	Open this day
Aug 31, 202684 of 146 trip windows had enough operator-feed evidence	146	132	2	12	90.4%	20	Open this day	Open this day	Open this day	Open this day
Aug 30, 202670 of 86 trip windows had enough operator-feed evidence	86	84	0	2	97.7%	17	Open this day	Open this day	Open this day	Open this day
Aug 29, 202662 of 88 trip windows had enough operator-feed evidence	88	76	1	11	86.4%	11	Open this day	Open this day	Open this day	Open this day
Aug 28, 202616 of 146 trip windows had enough operator-feed evidence	146	44	0	102	30.1%	9	Open this day	Open this day	Open this day	Open this day
Aug 27, 202624 of 146 trip windows had enough operator-feed evidence	146	74	0	72	50.7%	15	Open this day	Open this day	Open this day	Open this day
Aug 26, 20262 of 146 trip windows had enough operator-feed evidence	146	3	0	143	2.1%	1	Open this day	Open this day	Open this day	Open this day
Aug 25, 202648 of 146 trip windows had enough operator-feed evidence	146	88	0	58	60.3%	17	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
103890602026-09-18	03:58–04:19	Excluded: feed incomplete during this trip	None published	—	7 of 11 expected snapshots · 63.6%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
134830602026-09-18	04:19–04:42	Excluded: feed incomplete during this trip	None published	—	8 of 11 expected snapshots · 72.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
194530602026-09-18	04:56–05:17	No matching position; investigate	None published	—	9 of 11 expected snapshots · 81.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
223440602026-09-18	05:17–05:25	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
228220602026-09-18	05:30–05:34	No matching position; investigate	None published	—	7 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
169900602026-09-18	05:34–05:43	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
92790602026-09-18	06:00–06:04	No matching position; investigate	None published	—	7 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
193220602026-09-18	06:04–06:13	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
115210602026-09-18	06:15–06:20	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
176580602026-09-18	06:20–06:29	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
29570602026-09-18	06:30–06:35	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
214800602026-09-18	06:35–06:44	No matching position; investigate	None published	—	7 of 8 expected snapshots · 87.5%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
21680602026-09-18	06:45–06:50	No matching position; investigate	None published	—	6 of 7 expected snapshots · 85.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
196820602026-09-18	06:50–06:59	No matching position; investigate	None published	—	6 of 8 expected snapshots · 75%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
86840602026-09-18	07:00–07:05	Excluded: feed incomplete during this trip	None published	—	5 of 7 expected snapshots · 71.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
27030602026-09-18	07:05–07:15	No matching position; investigate	None published	—	6 of 8 expected snapshots · 75%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
114780602026-09-18	07:15–07:22	No matching position; investigate	None published	—	6 of 8 expected snapshots · 75%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
25870602026-09-18	07:22–07:32	No matching position; investigate	None published	—	7 of 8 expected snapshots · 87.5%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
2020602026-09-18	07:30–07:37	No matching position; investigate	None published	—	7 of 8 expected snapshots · 87.5%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
50460602026-09-18	07:37–07:47	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
92500602026-09-18	07:45–07:52	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
47550602026-09-18	07:52–08:02	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
36890602026-09-18	07:58–08:05	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
217240602026-09-18	08:05–08:15	No matching position; investigate	None published	—	9 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
168630602026-09-18	08:15–08:22	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
153390602026-09-18	08:22–08:32	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
114560602026-09-18	08:32–08:39	No matching position; investigate	None published	—	7 of 8 expected snapshots · 87.5%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
119380602026-09-18	08:39–08:49	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
151280602026-09-18	08:45–08:51	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
63440602026-09-18	08:51–09:00	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
21800602026-09-18	09:00–09:06	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
27700602026-09-18	09:06–09:15	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
57120602026-09-18	09:15–09:21	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
178280602026-09-18	09:21–09:30	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
159480602026-09-18	09:30–09:36	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
121550602026-09-18	09:36–09:45	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
169110602026-09-18	09:45–09:51	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
168350602026-09-18	09:51–10:00	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
65470602026-09-18	10:00–10:06	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
19160602026-09-18	10:06–10:15	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
159130602026-09-18	10:15–10:21	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
82490602026-09-18	10:21–10:30	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
179190602026-09-18	10:30–10:36	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
147310602026-09-18	10:36–10:45	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
169360602026-09-18	10:45–10:51	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
189200602026-09-18	10:51–11:00	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
131930602026-09-18	11:00–11:06	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
63760602026-09-18	11:06–11:15	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
24600602026-09-18	11:15–11:21	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
23680602026-09-18	11:21–11:30	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
19790602026-09-18	11:30–11:36	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
216370602026-09-18	11:36–11:45	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
175320602026-09-18	11:45–11:51	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
164420602026-09-18	11:51–12:00	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
89980602026-09-18	12:00–12:06	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
92780602026-09-18	12:06–12:15	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
228000602026-09-18	12:15–12:21	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
185230602026-09-18	12:21–12:30	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
42640602026-09-18	12:30–12:36	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
190540602026-09-18	12:36–12:45	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
185640602026-09-18	12:45–12:51	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
187260602026-09-18	12:51–13:00	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
31720602026-09-18	13:00–13:06	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
21630602026-09-18	13:06–13:15	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
72180602026-09-18	13:15–13:21	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
191680602026-09-18	13:21–13:30	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
71770602026-09-18	13:30–13:36	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
37350602026-09-18	13:36–13:46	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
87260602026-09-18	13:45–13:51	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
139690602026-09-18	13:51–14:01	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
116840602026-09-18	14:00–14:06	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
168480602026-09-18	14:06–14:16	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
70230602026-09-18	14:15–14:21	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
52630602026-09-18	14:21–14:31	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
380602026-09-18	14:30–14:36	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
202500602026-09-18	14:36–14:46	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
71690602026-09-18	14:45–14:51	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
134370602026-09-18	14:51–15:01	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
89770602026-09-18	15:00–15:06	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
129630602026-09-18	15:06–15:17	No matching position; investigate	None published	—	8 of 9 expected snapshots · 88.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
28250602026-09-18	15:15–15:21	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
178620602026-09-18	15:21–15:32	No matching position; investigate	None published	—	8 of 9 expected snapshots · 88.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
119610602026-09-18	15:28–15:34	No matching position; investigate	None published	—	7 of 8 expected snapshots · 87.5%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
82710602026-09-18	15:34–15:45	No matching position; investigate	None published	—	9 of 9 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
125820602026-09-18	15:44–15:50	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
25540602026-09-18	15:50–16:01	No matching position; investigate	None published	—	9 of 9 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
88110602026-09-18	16:00–16:06	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
20360602026-09-18	16:08–16:19	No matching position; investigate	None published	—	8 of 9 expected snapshots · 88.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
208960602026-09-18	16:15–16:21	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
12050602026-09-18	16:21–16:31	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
231240602026-09-18	16:30–16:36	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
44750602026-09-18	16:36–16:46	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
48820602026-09-18	16:45–16:51	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
110500602026-09-18	16:51–17:01	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
176710602026-09-18	17:00–17:06	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
165360602026-09-18	17:06–17:16	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
8950602026-09-18	17:15–17:21	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
155710602026-09-18	17:21–17:31	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
108510602026-09-18	17:30–17:36	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
94150602026-09-18	17:36–17:45	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
126850602026-09-18	17:45–17:51	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
33050602026-09-18	17:51–18:00	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
49050602026-09-18	18:00–18:06	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
80080602026-09-18	18:06–18:15	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
62990602026-09-18	18:15–18:21	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
94040602026-09-18	18:21–18:31	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
217010602026-09-18	18:30–18:36	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
172550602026-09-18	18:36–18:46	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
203500602026-09-18	18:45–18:51	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
8960602026-09-18	18:51–19:01	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
179770602026-09-18	19:00–19:06	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
89740602026-09-18	19:06–19:16	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
65020602026-09-18	19:15–19:21	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
44470602026-09-18	19:21–19:31	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
204260602026-09-18	19:30–19:36	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
78730602026-09-18	19:36–19:46	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
55860602026-09-18	19:45–19:51	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
186760602026-09-18	19:51–20:01	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
124350602026-09-18	20:00–20:05	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
15660602026-09-18	20:05–20:15	No matching position; investigate	None published	—	9 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
32560602026-09-18	20:15–20:20	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
31280602026-09-18	20:20–20:30	No matching position; investigate	None published	—	9 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
131750602026-09-18	20:30–20:35	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
59890602026-09-18	20:35–20:44	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
50350602026-09-18	21:00–21:05	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
131760602026-09-18	21:05–21:14	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
217420602026-09-18	21:30–21:35	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
147120602026-09-18	21:35–21:44	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
187270602026-09-18	22:00–22:05	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
35870602026-09-18	22:05–22:14	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
19040602026-09-18	22:30–22:35	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
46520602026-09-18	22:35–22:44	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
30040602026-09-18	23:00–23:05	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
2770602026-09-18	23:05–23:14	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
192920602026-09-18	23:30–23:35	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
56600602026-09-18	23:35–23:44	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
185890602026-09-18	24:00–24:05	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
112240602026-09-18	24:05–24:14	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
190060602026-09-18	24:30–24:35	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
173970602026-09-18	24:35–24:44	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
86410602026-09-18	25:00–25:05	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
83790602026-09-18	25:05–25:27	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.
190900602026-09-18	25:45–26:02	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.
49660602026-09-18	26:02–26:24	No matching position; investigate	None published	—	9 of 11 expected snapshots · 81.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
67420602026-09-18	26:44–27:01	No matching position; investigate	None published	—	10 of 10 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
210310602026-09-18	27:01–27:23	No matching position; investigate	None published	—	10 of 11 expected snapshots · 90.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
187271102026-09-17	22:00–22:05	No matching position; investigate	None published	—	8 of 7 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
27701002026-09-16	09:06–09:15	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
27700302026-09-15	09:06–09:15	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
121550302026-09-15	09:36–09:45	No matching position; investigate	None published	—	8 of 8 expected snapshots · 100%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.