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

Route 70

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 13 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-08, 2026-08-09, 2026-08-10, 2026-08-11, 2026-08-12, 2026-08-13, 2026-08-14, 2026-08-15, 2026-08-16, 2026-08-17, 2026-08-18, 2026-08-19, 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 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.

74331002026-09-06 · CANCELED · None publishedSep 6, 2026, 8:44 p.m.
140390902026-09-05 · CANCELED · None publishedSep 5, 2026, 2:38 p.m.
167920902026-09-05 · CANCELED · None publishedSep 5, 2026, 5:27 p.m.
90900902026-09-05 · CANCELED · None publishedSep 5, 2026, 3:44 p.m.
70750602026-09-04 · CANCELED · None publishedSep 4, 2026, 5:12 p.m.
70280502026-09-03 · CANCELED · None publishedSep 3, 2026, 5:02 p.m.
220450302026-09-01 · 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 1, 2026, 5:00 p.m.
1340702026-08-29 · CANCELED · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Aug 29, 2026, 4:31 p.m.
144190702026-08-29 · CANCELED · None publishedAug 29, 2026, 4:31 p.m.
236700702026-08-29 · CANCELED · None publishedA matching vehicle was also seen after this notice. Open the trip to compare the evidence; this does not prove trip completion.Aug 29, 2026, 4:31 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, 202661 of 64 trip windows had enough operator-feed evidence	64	1	60	3	1.6%	1	67	0%	10.4 min	12.9 min
Sep 5, 202665 of 67 trip windows had enough operator-feed evidence	67	1	64	2	1.5%	1	Open this day	Open this day	Open this day	Open this day
Sep 4, 202688 of 98 trip windows had enough operator-feed evidence	98	1	87	10	1%	1	Open this day	Open this day	Open this day	Open this day
Sep 3, 202615 of 98 trip windows had enough operator-feed evidence	98	92	0	6	93.9%	29	Open this day	Open this day	Open this day	Open this day
Sep 2, 202615 of 98 trip windows had enough operator-feed evidence	98	87	0	11	88.8%	28	Open this day	Open this day	Open this day	Open this day
Sep 1, 202627 of 98 trip windows had enough operator-feed evidence	98	95	3	0	96.9%	31	Open this day	Open this day	Open this day	Open this day
Aug 31, 202645 of 98 trip windows had enough operator-feed evidence	98	93	2	3	94.9%	29	Open this day	Open this day	Open this day	Open this day
Aug 30, 202654 of 64 trip windows had enough operator-feed evidence	64	64	0	0	100%	18	Open this day	Open this day	Open this day	Open this day
Aug 29, 202643 of 65 trip windows had enough operator-feed evidence	65	59	1	5	90.8%	26	Open this day	Open this day	Open this day	Open this day
Aug 28, 20262 of 98 trip windows had enough operator-feed evidence	98	35	0	63	35.7%	13	Open this day	Open this day	Open this day	Open this day
Aug 27, 202611 of 98 trip windows had enough operator-feed evidence	98	53	0	45	54.1%	19	Open this day	Open this day	Open this day	Open this day
Aug 26, 20260 of 98 trip windows had enough operator-feed evidence	98	0	0	98	0%	0	Open this day	Open this day	Open this day	Open this day
Aug 25, 202620 of 98 trip windows had enough operator-feed evidence	98	62	0	36	63.3%	22	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
256641002026-09-06	04:27–05:20	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.
272611002026-09-06	04:28–04:55	No matching position; investigate	None published	—	10 of 12 expected snapshots · 83.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
159671002026-09-06	04:57–05:50	Excluded: feed incomplete during this trip	None published	—	12 of 17 expected snapshots · 70.6%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
203721002026-09-06	04:58–05:25	Excluded: feed incomplete during this trip	None published	—	8 of 12 expected snapshots · 66.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
271341002026-09-06	05:52–06:19	Excluded: feed incomplete during this trip	None published	—	8 of 12 expected snapshots · 66.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
11381002026-09-06	05:57–06:25	No matching position; investigate	None published	—	9 of 12 expected snapshots · 75%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
240871002026-09-06	06:22–06:49	No matching position; investigate	None published	—	9 of 12 expected snapshots · 75%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
118811002026-09-06	06:27–06:55	No matching position; investigate	None published	—	9 of 12 expected snapshots · 75%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
200441002026-09-06	06:52–07:45	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.
95701002026-09-06	06:52–07:19	No matching position; investigate	None published	—	9 of 12 expected snapshots · 75%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
234551002026-09-06	07:22–08:15	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.
114711002026-09-06	07:24–08:14	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.
213741002026-09-06	08:22–09:15	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
285371002026-09-06	08:24–09:14	No matching position; investigate	None published	—	16 of 16 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
148401002026-09-06	09:22–10:15	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
54171002026-09-06	09:24–10:17	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
194361002026-09-06	09:54–10:47	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
285011002026-09-06	10:22–11:17	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
200431002026-09-06	10:24–11:17	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
111771002026-09-06	10:52–11:47	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
154041002026-09-06	10:54–11:47	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
231971002026-09-06	11:22–12:17	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
74241002026-09-06	11:24–12:17	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
263961002026-09-06	11:52–12:48	No matching position; investigate	None published	—	17 of 18 expected snapshots · 94.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
117891002026-09-06	11:54–12:49	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
105731002026-09-06	12:22–13:18	No matching position; investigate	None published	—	15 of 18 expected snapshots · 83.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
290401002026-09-06	12:24–13:19	Observed	6636	12:29 p.m. / 1:51 p.m.	15 of 17 expected snapshots · 88.2%
95131002026-09-06	12:52–13:48	No matching position; investigate	None published	—	14 of 18 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
158541002026-09-06	12:54–13:49	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.
112361002026-09-06	13:22–14:18	No matching position; investigate	None published	—	14 of 18 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
122651002026-09-06	13:24–14:19	No matching position; investigate	None published	—	14 of 17 expected snapshots · 82.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
226111002026-09-06	13:52–14:48	No matching position; investigate	None published	—	14 of 18 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
180441002026-09-06	13:54–14:49	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.
20921002026-09-06	14:22–15:18	No matching position; investigate	None published	—	14 of 18 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
171691002026-09-06	14:24–15:19	No matching position; investigate	None published	—	14 of 17 expected snapshots · 82.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
89281002026-09-06	14:52–15:48	No matching position; investigate	None published	—	14 of 18 expected snapshots · 77.8%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
119651002026-09-06	14:54–15:49	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.
189881002026-09-06	15:22–16:18	No matching position; investigate	None published	—	15 of 18 expected snapshots · 83.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
185721002026-09-06	15:24–16:19	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.
153921002026-09-06	15:52–16:48	No matching position; investigate	None published	—	17 of 18 expected snapshots · 94.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
265031002026-09-06	15:54–16:49	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
85481002026-09-06	16:22–17:18	No matching position; investigate	None published	—	17 of 18 expected snapshots · 94.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
200481002026-09-06	16:24–17:19	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
194171002026-09-06	16:52–17:48	No matching position; investigate	None published	—	16 of 18 expected snapshots · 88.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
273001002026-09-06	16:54–17:49	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
172651002026-09-06	17:22–18:18	No matching position; investigate	None published	—	16 of 18 expected snapshots · 88.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
247121002026-09-06	17:24–18:19	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
74931002026-09-06	17:52–18:48	No matching position; investigate	None published	—	16 of 18 expected snapshots · 88.9%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
160381002026-09-06	17:54–18:49	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
120081002026-09-06	18:22–19:18	No matching position; investigate	None published	—	17 of 18 expected snapshots · 94.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
226201002026-09-06	18:24–19:19	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
102781002026-09-06	18:52–19:47	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
158451002026-09-06	18:54–19:49	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
182881002026-09-06	19:22–20:17	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
52821002026-09-06	19:24–20:17	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
20701002026-09-06	19:52–20:47	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
208211002026-09-06	19:54–20:47	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
40631002026-09-06	20:52–21:47	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
73931002026-09-06	20:54–21:47	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
84201002026-09-06	21:52–22:45	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.
288701002026-09-06	21:54–22:45	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.
259201002026-09-06	22:52–23:45	No matching position; investigate	None published	—	16 of 17 expected snapshots · 94.1%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
36431002026-09-06	22:59–23:50	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.
220431002026-09-06	23:57–24:50	No matching position; investigate	None published	—	17 of 17 expected snapshots · 100%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem.

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.