Otranspo
Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.
Route 197
Trip service evidence
Open the totals. See the day, scheduled trip, public feed vehicle ID, and the data gaps that were excluded.
Operator-confirmed cancellations retained for this period
These rows exist only when an operator feed explicitly published CANCELED or DELETED. Collection starts with this feature’s release, so an empty earlier day means “not retained,” not zero cancellations.
No explicit cancellation statement has been retained for this period. This does not prove that every trip operated.
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 |
|---|---|---|---|---|---|---|---|---|---|---|
| Aug 28, 20261 of 22 trip windows had enough operator-feed evidence | 22 | 7 | 0 | 15 | 31.8% | 6 | 35 | 97.1% | 2.1 min | 4.7 min |
Scheduled-trip detail · August 28, 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 |
|---|---|---|---|---|---|
| 166531302026-08-28 | 05:33–06:02 | Excluded: feed incomplete during this trip | None published | — | 0 of 12 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 21541302026-08-28 | 06:00–06:29 | Excluded: feed incomplete during this trip | None published | — | 0 of 12 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 135091302026-08-28 | 06:30–07:03 | Excluded: feed incomplete during this trip | None published | — | 0 of 13 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 109731302026-08-28 | 07:30–08:03 | Excluded: feed incomplete during this trip | None published | — | 0 of 13 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 4531302026-08-28 | 08:00–08:33 | Excluded: feed incomplete during this trip | None published | — | 0 of 13 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 87371302026-08-28 | 08:30–09:03 | Excluded: feed incomplete during this trip | None published | — | 0 of 13 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 114491302026-08-28 | 09:10–09:38 | Excluded: feed incomplete during this trip | None published | — | 0 of 12 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 162461302026-08-28 | 10:10–10:38 | Excluded: feed incomplete during this trip | None published | — | 0 of 12 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 177621302026-08-28 | 11:10–11:38 | Excluded: feed incomplete during this trip | None published | — | 0 of 12 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 60301302026-08-28 | 12:10–12:42 | Excluded: feed incomplete during this trip | None published | — | 0 of 13 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 11681302026-08-28 | 13:10–13:42 | Excluded: feed incomplete during this trip | None published | — | 0 of 13 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 101111302026-08-28 | 14:10–14:42 | Observed | 4676 | 2:39 p.m. / 2:45 p.m. | 6 of 13 expected snapshots · 46.2% |
| 177991302026-08-28 | 15:09–15:41 | Observed | 2506 | 3:17 p.m. / 3:17 p.m. | 2 of 13 expected snapshots · 15.4% |
| 107061302026-08-28 | 15:40–16:12 | Observed | 2540 | 3:17 p.m. / 3:17 p.m. | 0 of 13 expected snapshots · 0% |
| 171011302026-08-28 | 16:09–16:41 | Excluded: feed incomplete during this trip | None published | — | 0 of 13 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 91041302026-08-28 | 16:40–17:12 | Excluded: feed incomplete during this trip | None published | — | 0 of 13 expected snapshots · 0%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 80771302026-08-28 | 17:10–17:42 | Excluded: feed incomplete during this trip | None published | — | 1 of 13 expected snapshots · 7.7%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 216441302026-08-28 | 17:40–18:12 | Observed | 6699 | 6:04 p.m. / 6:06 p.m. | 1 of 13 expected snapshots · 7.7% |
| 183661302026-08-28 | 18:10–18:41 | Excluded: feed incomplete during this trip | None published | — | 5 of 13 expected snapshots · 38.5%Cause: unknown. The public feed cannot distinguish an operator action, onboard equipment issue, communications failure, or another data problem. |
| 143481302026-08-28 | 19:10–19:35 | Observed | 4817 | 7:11 p.m. / 7:45 p.m. | 7 of 11 expected snapshots · 63.6% |
| 6881302026-08-28 | 20:10–20:35 | Observed | 6591 | 8:18 p.m. / 8:36 p.m. | 10 of 11 expected snapshots · 90.9% |
| 151351302026-08-28 | 21:10–21:35 | Observed | 4676 | 9:10 p.m. / 10:38 p.m. | 6 of 11 expected snapshots · 54.5% |
What these labels mean
- observed
- At least one public feed vehicle ID was credibly tied to the scheduled trip on that service date.
- noPositionCandidate
- 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.
- evidenceGap
- No matching position was found, but that trip’s scheduled window lacked enough operator-specific archive coverage. It is excluded from missing-service counts.
- vehicleId
- An identifier published by the realtime feed. It may change and is not necessarily a verified physical fleet number.
- 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.