Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.
Route
25
STO
Rider scorecard
What riders need to know about route 25
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
Grade withheld
No grading rule is applied until this service purpose can be classified from published evidence.
Service purpose
Purpose not classified
No grading rule is applied until this service purpose can be classified from published evidence.
- Explicit cancellations now
- —
- Skipped route origins now
- —
- Historical no-shows
- Not yet confirmed58.3% candidate observation gap
- Timetable deviation
- Grade withheld
- Bunching / service gaps
- —
- 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.
28 of 48 scheduled trips lacked a matched vehicle position over 4 service days (41.7% observed). These are investigation candidates, not confirmed no-shows.
Withheld under this route’s service-purpose rule.
Withheld under this route’s service-purpose rule.
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.
Recurring timetable-deviation periods are withheld because this route requires purpose-specific pickup, completion, or event-release evidence.
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.
This route cannot be placed on a map from the currently published stop coordinates. The full-screen map remains available.
Open the full-screen map →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
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, 12:09 p.m.
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
- 71.1%
- Within ±5 min
- 3,403
- Settled arrivals
- 9
- Observed weekdays
- 11.5 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
20 / 48 scheduled trips published at least one position across 4 service days (41.7%).
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
The stop list is temporarily unavailable. Nothing is shown rather than an inaccurate order.
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
- Computed or assembled
- Sample
- 3,403 settled arrivals across 1 matching reliability records.
- Coverage
- Published stop-pattern coverage is unavailable for this route.
- 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 STO GTFS. Check the Alerts panel for current official notices and each stop page for observed departures.