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

Route 39

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

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

25821002026-09-06 · CANCELED · None publishedSep 6, 2026, 10:45 a.m.
154570502026-09-03 · CANCELED · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Sep 3, 2026, 9:24 a.m.
11080202026-08-31 · CANCELED · None publishedAug 31, 2026, 7:50 p.m.
154570202026-08-31 · CANCELED · None publishedAug 31, 2026, 10:36 a.m.
154970202026-08-31 · CANCELED · None publishedAug 31, 2026, 11:06 a.m.
98800202026-08-31 · CANCELED · None publishedAug 31, 2026, 8:39 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 6, 2026141 of 149 trip windows had enough operator-feed evidence	149	2	139	8	1.3%	2	41	95.1%	1.9 min	3.2 min
Sep 5, 2026150 of 158 trip windows had enough operator-feed evidence	158	3	148	7	1.9%	3	Open this day	Open this day	Open this day	Open this day
Sep 4, 2026140 of 163 trip windows had enough operator-feed evidence	163	7	133	23	4.3%	5	Open this day	Open this day	Open this day	Open this day
Sep 3, 202625 of 163 trip windows had enough operator-feed evidence	163	123	2	38	75.5%	44	Open this day	Open this day	Open this day	Open this day
Sep 2, 202623 of 163 trip windows had enough operator-feed evidence	163	130	0	33	79.8%	46	Open this day	Open this day	Open this day	Open this day
Sep 1, 202646 of 163 trip windows had enough operator-feed evidence	163	160	0	3	98.2%	49	Open this day	Open this day	Open this day	Open this day
Aug 31, 202681 of 163 trip windows had enough operator-feed evidence	163	151	5	7	92.6%	50	Open this day	Open this day	Open this day	Open this day

Scheduled-trip detail · September 6, 2026

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
6111002026-09-06	03:25–04:13	Excluded: feed incomplete during this trip	None published	—	7 of 16 expected snapshots · 43.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
63801002026-09-06	03:30–04:18	Excluded: feed incomplete during this trip	None published	—	8 of 16 expected snapshots · 50%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
157401002026-09-06	03:55–04:43	No matching position; investigate	None published	—	12 of 16 expected snapshots · 75%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
290171002026-09-06	04:00–04:48	No matching position; investigate	None published	—	12 of 16 expected snapshots · 75%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
191221002026-09-06	04:25–05:14	No matching position; investigate	None published	—	12 of 16 expected snapshots · 75%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
217111002026-09-06	04:30–05:18	No matching position; investigate	None published	—	12 of 16 expected snapshots · 75%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
50661002026-09-06	04:55–05:44	No matching position; investigate	None published	—	12 of 16 expected snapshots · 75%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
201281002026-09-06	05:00–05:48	Excluded: feed incomplete during this trip	None published	—	11 of 16 expected snapshots · 68.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
112971002026-09-06	05:25–06:14	Excluded: feed incomplete during this trip	None published	—	11 of 16 expected snapshots · 68.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
291111002026-09-06	05:30–06:18	Excluded: feed incomplete during this trip	None published	—	11 of 16 expected snapshots · 68.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
531002026-09-06	05:55–06:44	No matching position; investigate	None published	—	13 of 16 expected snapshots · 81.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
49951002026-09-06	06:00–06:49	No matching position; investigate	None published	—	13 of 16 expected snapshots · 81.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
14441002026-09-06	06:25–07:14	No matching position; investigate	None published	—	12 of 16 expected snapshots · 75%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
287211002026-09-06	06:30–07:21	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.
15721002026-09-06	06:55–07:40	No matching position; investigate	None published	—	13 of 15 expected snapshots · 86.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
116901002026-09-06	07:00–07:51	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.
152171002026-09-06	07:25–08:10	No matching position; investigate	None published	—	13 of 15 expected snapshots · 86.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
37621002026-09-06	07:30–08:21	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.
101101002026-09-06	07:47–08:38	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.
56701002026-09-06	07:55–08:09	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.
95241002026-09-06	08:13–08:27	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.
276991002026-09-06	08:28–08:42	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.
93521002026-09-06	08:38–08:53	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.
260971002026-09-06	08:43–08:57	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.
31141002026-09-06	08:53–09:08	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.
76091002026-09-06	08:58–09:12	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.
11101002026-09-06	09:08–09:46	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
155721002026-09-06	09:13–09:27	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.
50681002026-09-06	09:22–09:59	No matching position; investigate	None published	—	12 of 14 expected snapshots · 85.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
287661002026-09-06	09:23–09:38	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.
269071002026-09-06	09:29–09:43	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.
159981002026-09-06	09:38–10:16	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
214591002026-09-06	09:52–10:29	No matching position; investigate	None published	—	12 of 14 expected snapshots · 85.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
55331002026-09-06	09:53–10:08	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.
170651002026-09-06	10:00–10:14	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.
135871002026-09-06	10:08–10:46	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
52391002026-09-06	10:22–10:59	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
230821002026-09-06	10:23–10:38	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.
11111002026-09-06	10:30–10:44	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.
163151002026-09-06	10:38–11:16	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.
212181002026-09-06	10:52–11:29	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
128041002026-09-06	10:53–11:08	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.
201861002026-09-06	11:00–11:14	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.
258491002026-09-06	11:08–11:46	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.
52871002026-09-06	11:22–11:59	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
85601002026-09-06	11:23–11:38	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.
102981002026-09-06	11:30–11:44	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.
56541002026-09-06	11:38–12:16	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.
167241002026-09-06	11:52–12:29	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
258221002026-09-06	11:53–12:08	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.
25621002026-09-06	12:00–12:14	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.
154611002026-09-06	12:08–12:46	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.
172601002026-09-06	12:22–12:59	No matching position; investigate	None published	—	12 of 14 expected snapshots · 85.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
76081002026-09-06	12:23–12:38	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.
179081002026-09-06	12:30–12:44	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.
81641002026-09-06	12:38–13:16	No matching position; investigate	None published	—	12 of 14 expected snapshots · 85.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
66031002026-09-06	12:52–13:29	Excluded: feed incomplete during this trip	None published	—	10 of 14 expected snapshots · 71.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
270481002026-09-06	12:53–13:08	Observed	2517	12:09 p.m. / 1:24 p.m.	8 of 9 expected snapshots · 88.9%
193041002026-09-06	13:00–13:14	No matching position; investigate	None published	—	7 of 9 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
278381002026-09-06	13:08–13:46	No matching position; investigate	None published	—	11 of 14 expected snapshots · 78.6%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
85561002026-09-06	13:22–13:59	No matching position; investigate	None published	—	11 of 14 expected snapshots · 78.6%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
235521002026-09-06	13:23–13:38	No matching position; investigate	None published	—	7 of 9 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
211291002026-09-06	13:30–13:44	No matching position; investigate	None published	—	7 of 9 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
214311002026-09-06	13:38–14:16	No matching position; investigate	None published	—	11 of 14 expected snapshots · 78.6%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
214351002026-09-06	13:52–14:29	No matching position; investigate	None published	—	11 of 14 expected snapshots · 78.6%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
233541002026-09-06	13:53–14:08	No matching position; investigate	None published	—	7 of 9 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
150881002026-09-06	14:00–14:14	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.
67071002026-09-06	14:08–14:46	No matching position; investigate	None published	—	12 of 14 expected snapshots · 85.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
34971002026-09-06	14:22–14:59	Excluded: feed incomplete during this trip	None published	—	10 of 14 expected snapshots · 71.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
262811002026-09-06	14:23–14:38	No matching position; investigate	None published	—	7 of 9 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
115611002026-09-06	14:30–14:44	No matching position; investigate	None published	—	7 of 9 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
170171002026-09-06	14:38–15:16	No matching position; investigate	None published	—	12 of 14 expected snapshots · 85.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
208651002026-09-06	14:52–15:29	Excluded: feed incomplete during this trip	None published	—	10 of 14 expected snapshots · 71.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
258891002026-09-06	14:53–15:08	No matching position; investigate	None published	—	7 of 9 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
168841002026-09-06	15:00–15:14	No matching position; investigate	None published	—	7 of 9 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
200221002026-09-06	15:08–15:46	No matching position; investigate	None published	—	12 of 14 expected snapshots · 85.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
289511002026-09-06	15:23–15:38	No matching position; investigate	None published	—	7 of 9 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
92401002026-09-06	15:30–15:44	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.
107651002026-09-06	15:38–16:16	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
216781002026-09-06	15:52–16:29	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
180021002026-09-06	15:53–16:08	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.
158901002026-09-06	16:00–16:14	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.
37821002026-09-06	16:22–16:59	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
257181002026-09-06	16:23–16:38	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.
16791002026-09-06	16:30–16:44	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.
13381002026-09-06	16:38–17:16	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.
261201002026-09-06	16:52–17:29	Observed	6574	4:50 p.m. / 5:27 p.m.	13 of 14 expected snapshots · 92.9%
54831002026-09-06	16:53–17:08	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.
160171002026-09-06	17:00–17:14	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.
139351002026-09-06	17:08–17:46	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
39551002026-09-06	17:22–17:59	No matching position; investigate	None published	—	12 of 14 expected snapshots · 85.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
185811002026-09-06	17:23–17:38	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.
139881002026-09-06	17:30–17:44	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.
43141002026-09-06	17:38–18:16	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
234401002026-09-06	17:52–18:29	No matching position; investigate	None published	—	12 of 14 expected snapshots · 85.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
37261002026-09-06	17:53–18:08	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.
268941002026-09-06	18:00–18:14	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.
237221002026-09-06	18:08–18:46	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.
164421002026-09-06	18:22–18:59	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
43151002026-09-06	18:23–18:38	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.
68351002026-09-06	18:30–18:44	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.
187881002026-09-06	18:38–19:16	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.
3891002026-09-06	18:52–19:29	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
127471002026-09-06	18:53–19:08	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.
237231002026-09-06	19:00–19:14	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.
82851002026-09-06	19:08–19:46	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.
137681002026-09-06	19:22–19:59	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
58721002026-09-06	19:23–19:38	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.
62551002026-09-06	19:30–19:44	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.
110901002026-09-06	19:38–20:16	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
142821002026-09-06	19:52–20:29	No matching position; investigate	None published	—	12 of 14 expected snapshots · 85.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
147901002026-09-06	19:53–20:08	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.
230951002026-09-06	20:00–20:14	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.
29481002026-09-06	20:08–20:46	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
266441002026-09-06	20:22–20:59	No matching position; investigate	None published	—	12 of 14 expected snapshots · 85.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
221611002026-09-06	20:23–20:38	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.
50641002026-09-06	20:30–20:44	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.
50751002026-09-06	20:38–21:16	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.
4431002026-09-06	20:52–21:29	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
32891002026-09-06	20:53–21:08	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.
111421002026-09-06	21:00–21:14	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.
212381002026-09-06	21:08–21:23	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.
116921002026-09-06	21:22–21:59	No matching position; investigate	None published	—	13 of 14 expected snapshots · 92.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
205041002026-09-06	21:23–21:38	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.
27851002026-09-06	21:30–21:44	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.
71801002026-09-06	21:38–21:53	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.
8731002026-09-06	21:53–22:08	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.
204501002026-09-06	22:00–22:14	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.
203341002026-09-06	22:08–22:23	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.
61451002026-09-06	22:30–22:44	No matching position; investigate	None published	—	7 of 9 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
37201002026-09-06	22:38–22:53	No matching position; investigate	None published	—	7 of 9 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
121921002026-09-06	23:00–23:49	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.
87301002026-09-06	23:08–23:23	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.
174181002026-09-06	23:30–24:15	No matching position; investigate	None published	—	16 of 15 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
214801002026-09-06	23:38–23:53	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.
289411002026-09-06	23:38–24: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.
163281002026-09-06	24:00–24:45	No matching position; investigate	None published	—	16 of 15 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
39561002026-09-06	24:08–24:56	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.
117501002026-09-06	24:30–25:15	No matching position; investigate	None published	—	16 of 15 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
1121002026-09-06	24:38–25: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.
16451002026-09-06	25:00–25:45	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.
219651002026-09-06	25:08–25:56	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.
86121002026-09-06	25:30–26:15	No matching position; investigate	None published	—	14 of 15 expected snapshots · 93.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
89151002026-09-06	25:38–26:26	No matching position; investigate	None published	—	14 of 16 expected snapshots · 87.5%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
24601002026-09-06	26:00–26:45	No matching position; investigate	None published	—	14 of 15 expected snapshots · 93.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
30341002026-09-06	26:08–26:56	No matching position; investigate	None published	—	14 of 16 expected snapshots · 87.5%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
21171002026-09-06	26:30–27:15	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.
63251002026-09-06	26:38–27:26	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.
117011002026-09-06	27:00–27:45	No matching position; investigate	None published	—	16 of 15 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.