Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.
Route
617
OC Transpo
This page includes all 2 current versions of the route, including short trips and different destinations.
Share this page
Use the permanent public link to this page and its sources.
Only the canonical public link is shared. Panel state, location, receipts, and other browser-only details are left out. Email and social services apply their own privacy terms.
Route check
How route 617 is doing
A plain-language summary of the strongest evidence we have. We say when the data cannot answer a question.
Bottom line
We do not have enough evidence to rate this route yet.
87 in 100 arrivals were within 5 minutes of schedule · 134 arrivals checked
Confidence in this summary: Still building
Based on 134 arrivals over 2 weekdays, from 2026-07-29T18:45:47.010Z to 2026-08-28T18:45:47.010Z.
Updated Aug 28, 2026, 2:45 p.m.
Problems to fix
These are repeated patterns, not one bad day or an unverified rider report.
No recurring problem time has cleared our evidence threshold yet.
No current official notice matches this route.
Problem places
We do not yet have enough route-by-stop history to name a recurring problem stop. Rider reports are used as leads, not proof.
The questions riders ask
- Cancelled trips right now
- Cannot confirm right now
- Trips that may not have shown up
- No confirmed count yet
- Late service
- The slowest 5 in 100 were more than about 7.1 min late
- Long gaps or bunching
- No route-level result meets the evidence threshold yet. This does not mean gaps did not happen.
Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
3 of 6 scheduled trips had no matching vehicle position over 3 days. The feed covered 50.0%. These are cases to investigate—not confirmed no-shows.
87 in 100 arrivals were within 5 minutes of schedule.
How this route is judged: Regular all-stop route
We compare observed arrivals with the official schedule. A result needs at least 200 arrivals. Within 5 minutes is the rider-facing target used here.
What this data cannot prove
The public feed does not provide dependable passenger counts or passed-up-rider events. A missing position does not by itself prove a cancellation, no-show, short turn or cause.
See the definitions, thresholds and evidence order
- Official current feed: explicit cancellations, skipped stops and active notices.
- Matched observations: vehicle positions and settled predictions tied to the official schedule.
- Official timetable: what was planned, kept separate from what was observed.
- Rider and operator reports: leads about routes, times and places to investigate—not numeric proof by themselves.
Live route map
Where the buses are now
Fresh vehicle positions appear on the route below. A marker stops moving when the evidence runs out—we do not invent movement.
Route and live buses
The line is the official route. Dots show published stops, buses seen now and stops named in current notices.
0 official shapes · 92 stops · 0 vehicle markers
Loading official route geometry · Loading current vehicles
Markers move between GPS fixes using measured progress along the published route. They pause after one measured reporting interval, on a measured standstill, or when evidence becomes stale.
Today’s schedule
Service date August 28, 2026
- Towards Omer-Deslauriers
- 1 scheduled trip
- 7:57 a.m.–8:44 a.m.
- Scheduled gap unavailable because fewer than two distinct trips start
- Towards Hurdman
- 1 scheduled trip
- 3:17 p.m.–4:09 p.m.
- Scheduled gap unavailable because fewer than two distinct trips start
Span and median gap are computed from today’s official GTFS stop_times. They are timetable measures, not observed headways or a frequency guarantee.
Next trips from the ends of the route
These are trip starts. For the time at your stop, open that stop’s departure board.
No upcoming trip start is published in the next four hours.
The realtime prediction feed is unavailable or stale. Timetable times remain labelled as scheduled only.
Buses seen now
Current vehicle positions cannot be confirmed. No zero is shown.
Official notices
No matching active notice appears in the current healthy operator feed.
Planned changes
The planned-change register is unavailable. No planned change is confirmed or ruled out.
These are Otranspo register records, separate from operator alerts. A record is attached only when its route label identifies one operator; ambiguous OC Transpo/STO number matches are withheld.
Evidence checked Aug 28, 4:11 p.m.
Check the numbers
Data behind this result
This route has more than one official schedule record. We keep each record separate so the totals stay checkable and we do not invent a combined worst-case result.
Open any result below to see the hours, denominators, observed days, and position coverage behind it.
Observed evidence cohort 617
Provisional results, published evidence
When is this route reliable?
Every hour below is backed by this route’s settled arrivals. “On time” means no more than five minutes early or late, so a bus that leaves very early counts as a failure for the waiting rider.
Evidence window: July 29, 2026 to August 28, 2026
- 87.3%
- Within ±5 min
- 134
- Settled arrivals
- 2
- Observed weekdays
- 7.1 min late
- How late the worst 5 in 100 were
Patterns by hour (2)
| Hour | On time | Median | Worst 5 in 100 | Evidence |
|---|---|---|---|---|
| 08:00 | 95.1% | 0.5 min late | 2.8 min late | 81 · 2 days |
| 15:00 | 69.2% | 2.7 min late | 8.2 min late | 39 · 1 days |
No repeated pattern below 70% is yet established across at least three service days.
Scheduled bus, but not observed in realtime
3 / 6 scheduled trips published at least one position across 3 service days (50.0%).
This is not a confirmed no-show. A missing position can mean a cancelled or missed bus, but it can also mean an unassigned trip ID or an operator-feed gap. Otranspo publishes the gap because it matters to riders while keeping the conclusion honest.
Method: last prediction within ten minutes of each arrival; one arrival per trip, stop and service date. Trip coverage: GTFS schedule compared with any GTFS-RT position carrying the same trip and local service date. Sources and limitations.
See all stops and route patterns
Stops and stations
2 official stop patterns
Each row below is one exact stop order published in the official schedule. Short turns and alternate destinations stay separate.
- View stops and calendar →
Towards Omer-Deslauriers: HURDMAN E to CHESTERTON / OMER-DESLAURIERS
48 stops · 10 imported trips
Scheduled from Aug 14, 2026 to Sep 20, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday
10 official service records
4 added dates and 8 removed dates
- View stops and calendar →
Towards Hurdman: VIEWMOUNT / GRANT CARMAN to HURDMAN B
46 stops · 10 imported trips
Scheduled from Aug 14, 2026 to Sep 20, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday
10 official service records
4 added dates and 8 removed dates
Official feed version 6a5cf745-35f3-4cac-aa4d-35b6661335fe
Source checksum 93bdaf6ee5d5ca7fd25a8c81319668a8489f2d9c86433718618d79c61c38bba2
Evidence behind this pageOpen the definition, method, sources, dates, coverage, and known limits.
What is being shown
The current public route group, its published schedule variants and stop patterns, current operations, and matching observed reliability where available.
How it was produced
2 current GTFS route record variants are grouped by operator and public route number. Stop patterns remain tied to their published variant; aggregated reliability records are not merged into an invented percentile.
Evidence dates
- Collected or observed
- Computed or assembled
- Sample
- 134 settled arrivals across 1 matching reliability records.
- Coverage
- 2 published stop patterns containing 94 stop calls are available on this page.
- Method or data version
- last-prediction-within-ten-minutes-v1; 6a5cf745-35f3-4cac-aa4d-35b6661335fe; 93bdaf6ee5d5ca7fd25a8c81319668a8489f2d9c86433718618d79c61c38bba2
Sources
Limits to keep in mind
- Schedule variants can apply on different dates. A grouped route is not a claim that every pattern operates today.
- Accessibility fields report only what the operator publishes; an unknown value is not confirmation of access.
Rider evidence
Community reports
Signals below are moderated community aggregates, not official operator notices or reliability scores.
You can report without signing in. Anonymous reports count a little less when we calculate public patterns. You can add an account after submitting.
Report a specific problem
Emergency: call 9-1-1. Check official OC Transpo or STO notices before travelling.
Source: currently imported OC Transpo GTFS. Check the Alerts panel for current official notices and each stop page for observed departures.