Otranspo
Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.
Route 110
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 14 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-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.
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.
- 108080602026-09-04 · CANCELED · None publishedSep 4, 2026, 11:26 a.m.
- 49330602026-09-04 · CANCELED · None publishedSep 4, 2026, 8:14 a.m.
- 62800402026-09-02 · 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 2, 2026, 4:33 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.
Scheduled-trip detail · September 7, 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 |
|---|---|---|---|---|---|
| 223191102026-09-07 | 04:44–05:39 | 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. |
| 250451102026-09-07 | 04:44–05:35 | 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. |
| 173651102026-09-07 | 05:14–06:05 | Excluded: feed incomplete during this trip | None published | — | 11 of 17 expected snapshots · 64.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 231021102026-09-07 | 05:14–06:09 | Excluded: feed incomplete during this trip | None published | — | 11 of 17 expected snapshots · 64.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 196941102026-09-07 | 05:53–07:11 | No matching position; investigate | None published | — | 17 of 22 expected snapshots · 77.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 206071102026-09-07 | 06:15–07:35 | No matching position; investigate | None published | — | 17 of 22 expected snapshots · 77.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 184831102026-09-07 | 06:23–07:41 | No matching position; investigate | None published | — | 17 of 22 expected snapshots · 77.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 113551102026-09-07 | 06:45–08:05 | No matching position; investigate | None published | — | 19 of 22 expected snapshots · 86.4%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 29341102026-09-07 | 16:53–18:14 | No matching position; investigate | None published | — | 20 of 23 expected snapshots · 87%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 271821102026-09-07 | 17:15–18:36 | No matching position; investigate | None published | — | 22 of 23 expected snapshots · 95.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 179391102026-09-07 | 17:23–18:44 | No matching position; investigate | None published | — | 21 of 23 expected snapshots · 91.3%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 113921102026-09-07 | 17:45–19:06 | No matching position; investigate | None published | — | 22 of 23 expected snapshots · 95.7%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.