Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.
Route
7
OC Transpo
2 official schedule records are grouped under this public route. Destinations and stop patterns from every current record are included below.
Rider scorecard
What riders need to know about route 7
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
Needs attention
63.8% within ±5 min · 103,194 settled arrivals
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 confirmed35.5% candidate observation gap
- Timetable deviation
- 63.8% within ±5 min
- Bunching / service gaps
- 8.0 min predicted average wait · 1.9 min beyond the scheduled wait
- Full buses / passed-up riders
- No defensible route count
- Mid-route changes / short turns
- Current official notices are unavailable.
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.
321 of 905 scheduled trips lacked a matched vehicle position over 7 service days (64.5% observed). These are investigation candidates, not confirmed no-shows.
95% were no later than 17.0 min after schedule in this cohort.
4,991 matched arrivals across 134 high-frequency stops and 11 service days.
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 · 135 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 timetable cannot be read for this route. No service span or frequency is estimated.
Next departures from route origins
These are upcoming trip starts, not departures from every stop. Open a stop below for its own board.
The current official timetable cannot be read for this route. No service span or frequency is estimated.
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
The operator notice feed is unavailable or stale, so no all-clear is claimed.
Planned changes
No safely matched planned change is recorded for this route.
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:16 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.
Observed evidence cohort 7
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
- 63.8%
- Within ±5 min
- 103,194
- Settled arrivals
- 21
- Observed weekdays
- 17 min late
- 95th percentile
Patterns by hour (0)
Not enough arrivals yet to split this route by hour.
No repeated pattern below 70% is yet established across at least three service days.
Scheduled bus, but not observed in realtime
584 / 905 scheduled trips published at least one position across 7 service days (64.5%).
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.
Stops and stations
7 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 Carleton: ST-LAURENT D to CARLETON A
65 stops · 1404 imported trips
Scheduled from Aug 14, 2026 to Sep 20, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
25 official service records
10 added dates and 30 removed dates
- View stops and calendar →
Towards Carleton: RIDEAU A to CARLETON A
25 stops · 179 imported trips
Scheduled from Aug 14, 2026 to Sep 20, 2026
Published weekly days: Monday, Saturday, Sunday
9 official service records
4 added dates and 16 removed dates
- View stops and calendar →
Towards Rideau: ST-LAURENT D to RIDEAU A
41 stops · 48 imported trips
Scheduled from Aug 14, 2026 to Sep 20, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday
16 official service records
6 added dates and 14 removed dates
- View stops and calendar →
Towards Rideau: CARLETON A to RIDEAU B
30 stops · 175 imported trips
Scheduled from Aug 14, 2026 to Sep 20, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
14 official service records
4 added dates and 17 removed dates
- View stops and calendar →
Towards St-Laurent: CARLETON A to ST-LAURENT C
71 stops · 1407 imported trips
Scheduled from Aug 14, 2026 to Sep 20, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
25 official service records
10 added dates and 30 removed dates
- View stops and calendar →
Towards St-Laurent: RIDEAU B to ST-LAURENT C
42 stops · 54 imported trips
Scheduled from Aug 14, 2026 to Sep 20, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday
19 official service records
7 added dates and 17 removed dates
- View stops and calendar →
Towards St-Laurent: ST-LAURENT / DUNBARTON to ST-LAURENT C
13 stops · 3 imported trips
Scheduled from Aug 14, 2026 to Sep 20, 2026
Published weekly days: Saturday
3 official service records
1 added date and 3 removed dates
Official feed version 6a5cf745-35f3-4cac-aa4d-35b6661335fe
Source checksum 93bdaf6ee5d5ca7fd25a8c81319668a8489f2d9c86433718618d79c61c38bba2
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
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
- Computed or assembled
- Sample
- 103,194 settled arrivals across 1 matching reliability records.
- Coverage
- 7 published stop patterns containing 287 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.