Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.
Route
631
OC Transpo
Rider scorecard
What riders need to know about route 631
Current operator facts and historical observations are kept separate. Missing data is highlighted, but it is not automatically called a cancelled trip or no-show.
Current evidence band
Evidence still emerging
Schedule adherence is assessed at settled arrivals. The visible attention bands are: strong at 80% or more within ±5 minutes; watch at 65–79.9%; needs attention below 65%. At least 200 arrivals are required.
Service purpose
Conventional all-stop service
Schedule adherence is assessed at settled arrivals. The visible attention bands are: strong at 80% or more within ±5 minutes; watch at 65–79.9%; needs attention below 65%. At least 200 arrivals are required.
- Explicit cancellations now
- —
- Skipped route origins now
- —
- Historical no-shows
- Not yet confirmed
- Timetable deviation
- —
- Bunching / service gaps
- —
- Full buses / passed-up riders
- No defensible route count
- Mid-route changes / short turns
- 0 current official notices
Upcoming route-origin departures in the current four-hour board; this is not a historical cancellation rate.
A skipped origin is kept separate from a cancelled trip. Either claim appears only from a current healthy provider relationship.
The schedule-to-position comparison is unavailable. No no-show count is invented.
Not enough settled arrivals to publish a route result.
No route-level high-frequency regularity result meets the evidence gate. This does not mean gaps did not occur.
The public vehicle feed does not provide dependable passenger loads or pass-up events. Rider reports identify where to investigate, but are not turned into a rate.
A notice may explain a change, but it is not a historical short-turn count. Otranspo does not infer an unannounced route change from a missing position.
Recurring problem periods
Hours below 70% within ±5 minutes on at least three service days are surfaced for action. They describe timetable deviation, not proven service failure.
No recurring below-70% hour is established in the currently published route cohorts.
Evidence-backed problem locations
No route-by-stop historical cohort meets the publication contract yet. The route map below highlights current notice-affected stops and live buses, but rider reports are not turned into hotspot claims.
How claims earn confidence
- Official current feed: explicit cancellations, skipped stops and active notices.
- Matched observations: settled predictions and vehicle positions tied to the official schedule.
- Official timetable: what was scheduled, kept distinct from what was observed.
- Rider and operator reports: valuable leads for routes, times and places to investigate—not numeric proof by themselves.
Current route evidence
What is happening on this route
Timetable, vehicle and notice evidence are kept separate so a missing live feed is never presented as no service.
Route map
The route, its published stops, vehicles observed now and stops named by active notices are together here. Exact official street geometry is used when available.
0 official shapes · 86 stops · 0 live vehicles
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 scheduled service
Service date August 28, 2026
The current official GTFS contains no service for this route on this service date.
Next departures from route origins
These are upcoming trip starts, not departures from every stop. Open a stop below for its own 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.
Vehicles observed now
Current vehicle positions cannot be confirmed. No zero is shown.
Active 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, 1:17 p.m.
Reliability evidence by published route cohort
This public route groups more than one official schedule record. Percentiles and observed weekday sets cannot be safely merged from published aggregates, so each matching evidence cohort remains separate.
No reliability cohort can be safely matched to this public route. No representative schedule record is substituted.
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 Colonel By: INNES / AD. 3927 to KENDER / OGILVIE
43 stops · 5 imported trips
Scheduled from Aug 30, 2026 to Sep 20, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday
5 official service records
0 added dates and 1 removed date
- View stops and calendar →
Towards Innes: OGILVIE / KENDER to INNES / AD. 3927
43 stops · 5 imported trips
Scheduled from Aug 30, 2026 to Sep 20, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday
5 official service records
0 added dates and 1 removed date
The stop patterns are available, but this environment cannot name the imported feed version.
Share this page
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.
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
1 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
- Sample
- No matching settled-arrival reliability sample is currently published for this public route.
- Coverage
- 2 published stop patterns containing 86 stop calls are available on this page.
- Method or data version
- last-prediction-within-ten-minutes-v1
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.