Before
Service date checked: August 31, 2026
- Scheduled trips
- 100
- Distinct scheduled stops
- 139
- Distinct published paths
- 10
- Published service span
- 04:57–27:33
Feed fingerprint: ecc28a3727bcaff4 · 345fd07d-fb05-4eaa-8ec2-3daf8b7fcbe9
Otranspo
Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.
Route
57
OC Transpo
Tunney's Pasture & N Rideau ↔ Carling Campus ~ Complexe Carling
All imported trips are marked accessible.Imported schedule valid through: Oct 4, 2026
Verdict
What this route needs
Timetable short by 3.2 to 4.8 min in 12 hours of the day.
Buses already leave about 2.7 min late and hold it to the end. The running time is right; the terminal is the problem.
15:00 drops to 35% on time, against 71% the rest of the day.
Fix: recovery time at the terminal so the next trip starts on time. More running time would not help here.
- 00:00: 70.4% of arrivals on time, 530 arrivals, typically 1.8 min late
- 01:00: 81.9% of arrivals on time, 529 arrivals, typically 1.7 min late
- 02:00: 81.2% of arrivals on time, 565 arrivals, typically 1.3 min late
- 03:00: 87.5% of arrivals on time, 144 arrivals, typically 1.7 min late
- 04:00: not enough data
- 05:00: 82.8% of arrivals on time, 279 arrivals, typically 0.7 min late
- 06:00: 91.3% of arrivals on time, 1,370 arrivals, typically 1.3 min late
- 07:00: 68.3% of arrivals on time, 1,811 arrivals, typically 3.1 min late
- 08:00: 52.4% of arrivals on time, 1,093 arrivals, typically 4.9 min late
- 09:00: 80.1% of arrivals on time, 699 arrivals, typically 2.2 min late
- 10:00: 67.1% of arrivals on time, 741 arrivals, typically 3 min late
- 11:00: 71.9% of arrivals on time, 981 arrivals, typically 3.4 min late
- 12:00: 71% of arrivals on time, 818 arrivals, typically 3.3 min late
- 13:00: 67.4% of arrivals on time, 877 arrivals, typically 3.1 min late
- 14:00: 44.1% of arrivals on time, 922 arrivals, typically 5.4 min late
- 15:00: 35.1% of arrivals on time, 961 arrivals, typically 6.4 min late
- 16:00: 48.3% of arrivals on time, 871 arrivals, typically 5.2 min late
- 17:00: 53.9% of arrivals on time, 714 arrivals, typically 4.8 min late
- 18:00: 75.3% of arrivals on time, 576 arrivals, typically 1.1 min late
- 19:00: 61.5% of arrivals on time, 706 arrivals, typically 3.8 min late
- 20:00: 72.9% of arrivals on time, 641 arrivals, typically 2.6 min late
- 21:00: 65% of arrivals on time, 694 arrivals, typically 3.4 min late
- 22:00: 71.9% of arrivals on time, 793 arrivals, typically 3.1 min late
- 23:00: 83.7% of arrivals on time, 632 arrivals, typically 1.5 min late
- 90% or more on time
- 80 to 90% on time
- under 80% on time
- not enough data
| What | When | Measured | Fix |
|---|---|---|---|
| ProblemLate by the timetable | 07:00 to 09:00 · 11:00 to 18:00 · 19:00 · 21:00 to 23:00 | 4 min late … 3.2 min late | Recovery time at the terminal |
| ProblemOne hour collapses | 15:00 | 35% | Operations, not the timetable |
Measurements
- Late by the timetable · 11:00 to 18:00
- medianDelaySeconds 287
- spreadSeconds 498
- observations 6,144
- hoursAffected 7
- suggestedRunningTimeChangeMinutes 4.8
- Late by the timetable · 07:00 to 09:00
- medianDelaySeconds 239
- spreadSeconds 641.5
- observations 2,904
- hoursAffected 2
- suggestedRunningTimeChangeMinutes 4
- Late by the timetable · 21:00 to 23:00
- medianDelaySeconds 194
- spreadSeconds 292.5
- observations 1,487
- hoursAffected 2
- suggestedRunningTimeChangeMinutes 3.2
- Late by the timetable · 19:00
- medianDelaySeconds 226
- spreadSeconds 617
- observations 706
- hoursAffected 1
- suggestedRunningTimeChangeMinutes 3.8
- One hour collapses · 15:00
- hour 15
- onTimePct 35.1
- routeMedianOnTimePct 71
- shortfallPoints 35.9
- observations 961
07:00 45→4907:00 51→5508:00 42→4608:00 53→5711:00 51→5611:00 57→6212:00 54→5912:00 60→6513:00 54→5913:00 60→6514:00 55→6014:00 60→6515:00 58→6315:00 62→6716:00 56→6116:00 62→6717:00 52→5717:00 62→6719:00 42→4619:00 43→4721:00 39→4221:00 40→4322:00 37→4022:00 40→43
Route check
How route 57 is doing
A plain-language summary of the strongest evidence we have. We say when the data cannot answer a question.
Bottom line
Service is unreliable often enough to affect riders.
69 in 100 arrivals were within 5 minutes of schedule · 32,023 arrivals checkedConfidence in this summary: High
Based on 32,023 arrivals over 20 weekdays, from Aug 9, 2026 to Sep 8, 2026.
Updated Sep 8, 2026, 2:32 a.m.
Where and when does it keep going wrong?
These are repeated patterns, not one bad day or an unverified rider report. They are measured the same way as the verdict above, over the same arrivals, but they are counted per stop rather than per hour, so the two lists need not match line for line.
- 3 p.m.–4 p.m.: 65 in 100 arrivals were more than 5 minutes early or late (961 arrivals over 8 days).
- 2 p.m.–3 p.m.: 56 in 100 arrivals were more than 5 minutes early or late (922 arrivals over 8 days).
- 4 p.m.–5 p.m.: 52 in 100 arrivals were more than 5 minutes early or late (871 arrivals over 6 days).
- 8 a.m.–9 a.m.: 48 in 100 arrivals were more than 5 minutes early or late (1,093 arrivals over 8 days).
1 current notice affects this route
- • NCC Weekend Bikedays: Routes 57, 61, 62, 63, 74, 75, 87 to detour
Problem places
- BASELINE / Q.C.H.
50 in 100 arrivals were more than 5 minutes early or late (262 arrivals over 19 days).
Open this stop - JOHN SUTHERLAND / RICHMOND
50 in 100 arrivals were more than 5 minutes early or late (266 arrivals over 19 days).
Open this stop - QUEENSWAY CARLETON / IRVING GREENBERG
49 in 100 arrivals were more than 5 minutes early or late (267 arrivals over 19 days).
Open this stop - QUEENSWAY CARLETON / EMERGENCY
48 in 100 arrivals were more than 5 minutes early or late (264 arrivals over 19 days).
Open this stop
These are route-specific settled arrivals. They identify a repeated location and time difference, but do not prove the cause.
Check every trip and date
Open a time period to see each service day, scheduled trip, feed gap, observed public vehicle ID, and the exact counts behind this summary.
What riders want to know
- Is any trip cancelled right now?
- 0 of 12
- Possible no-shows after checking feed gaps?
- 232 of 517 checked trips need a closer look
- How late does this route get?
- The slowest 5 in 100 were more than about 12.0 min late
- Do buses bunch or leave long gaps?
- Average extra wait was under 30 seconds at the measured stop
Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
232 of 517 trips with enough public-feed evidence had no matching position over 7 days. 37 of 554 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
69 in 100 arrivals were within 5 minutes of schedule.
0.0 min beyond the scheduled wait, based on 253 arrivals at 3 high-frequency stops over 8 days.
Schedule change check
Fall schedule: before and after
This compares the official schedule that ended with the one that started August 30. Schedule changes are facts about what was planned; they do not prove that a trip ran.
Current published schedule began September 4, 2026
What the official notice says about this route
The City’s public summary did not name this route. The feed comparison below can still show a changed timetable, but it cannot tell us why it changed.
Read the official August 30 service-change notice →One comparable weekday from each published schedule
We use the first Monday after the new schedule began and the Monday one week earlier. Every figure comes from the retained official GTFS versions named below.
New schedule
Service date checked: September 7, 2026
- Scheduled trips
- 53
- Distinct scheduled stops
- 136
- Distinct published paths
- 6
- Published service span
- 05:44–24:59
Feed fingerprint: e0b417f2ea03fcf0 · 37ff8dfc-21cc-48c3-9eba-fc0d2e50b2ad
Did service improve after the change?
We will compare settled arrivals for the 14 days before and after the change. We publish the comparison only after both sides have at least 7 service days and 200 arrivals.
Still collecting: before has 16,469 arrivals over 11 days; after has 1,884 arrivals over 4 days. No improvement or decline is claimed yet.
Checksums let anyone verify which retained timetable produced the counts. A changed count does not identify a cause, cancellation, operator decision, or passenger impact.
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.
Would you count on route 57?
No sign-in needed. A vote from a device that is not signed in counts a little less than one from an account, and a person who rates many routes counts a little less on each, so no one voice outweighs the rest.
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.
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 · 139 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.
Repeated problem stops: HOLLY ACRES / BAYSHORE STATION, HOLLY ACRES / RAMP, RICHMOND / NANAIMO, JOHN SUTHERLAND / RICHMOND, QUEENSWAY CARLETON / IRVING GREENBERG and 7 more. These are highlighted from route-specific settled arrivals with at least 60 observations over 3 days; the pattern does not prove a cause.
Today’s schedule
Service date September 8, 2026
- Towards Rideau
- 4 scheduled trips
- 12:38 a.m.–2:53 a.m.
- 30 min median scheduled gap
- Towards Tunney's Pasture
- 47 scheduled trips
- 4:57 a.m.–12:37 a.m. (next day)
- 30 min median scheduled gap
- Towards Bayshore
- 7 scheduled trips
- 12:02 a.m.–3:33 a.m.
- 30 min median scheduled gap
- Towards Carling Campus ~ Complexe Carling
- 42 scheduled trips
- 5:42 a.m.–12:26 a.m. (next day)
- 30 min median scheduled gap
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.
Towards Tunney's Pasture
Starts at BAYSHORE A
Timetable only. No usable prediction is available for this trip.
Towards Tunney's Pasture
Starts at BAYSHORE A
Timetable only. No usable prediction is available for this trip.
Towards Carling Campus ~ Complexe Carling
Starts at FITZGERALD / AD. 25
Timetable only. No usable prediction is available for this trip.
Towards Carling Campus ~ Complexe Carling
Starts at TUNNEY'S PASTURE B
Timetable only. No usable prediction is available for this trip.
Showing 4 of 12 trips. Open a stop for its full departure board.
Buses seen now
The current healthy operator position feed contains no vehicle matched to this route.
Official notices
- Read notice →
NCC Weekend Bikedays: Routes 57, 61, 62, 63, 74, 75, 87 to detour
Timing not published by the operator
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 Sep 8, 2:52 a.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: August 9, 2026 to September 8, 2026
- Within 5 minutes of schedule
- 69.4%
- Arrivals checked
- 32,023
- Weekdays with data
- 20
- How late the worst 5 in 100 were
- 12 min late
Patterns by hour (23)
| Hour | On time | Median | Worst 5 in 100 | Evidence |
|---|---|---|---|---|
| 00:00 | 70.4% | 1.8 min late | 19.1 min late | 530 · 6 days |
| 01:00 | 81.9% | 1.7 min late | 9.3 min late | 529 · 6 days |
| 02:00 | 81.2% | 1.3 min late | 6.4 min late | 565 · 7 days |
| 03:00 | 87.5% | 1.7 min late | 5.8 min late | 144 · 7 days |
| 05:00 | 82.8% | 0.7 min late | 10.1 min late | 279 · 6 days |
| 06:00 | 91.3% | 1.3 min late | 5.7 min late | 1,370 · 7 days |
| 07:00 | 68.3% | 3.1 min late | 11.6 min late | 1,811 · 10 days |
| 08:00 | 52.4% | 4.9 min late | 17.8 min late | 1,093 · 8 days |
| 09:00 | 80.1% | 2.2 min late | 9.7 min late | 699 · 6 days |
| 10:00 | 67.1% | 3 min late | 8.5 min late | 741 · 7 days |
| 11:00 | 71.9% | 3.4 min late | 11 min late | 981 · 9 days |
| 12:00 | 71.0% | 3.3 min late | 10.5 min late | 818 · 9 days |
| 13:00 | 67.4% | 3.1 min late | 19.9 min late | 877 · 10 days |
| 14:00 | 44.1% | 5.4 min late | 13.7 min late | 922 · 8 days |
| 15:00 | 35.1% | 6.4 min late | 16.5 min late | 961 · 8 days |
| 16:00 | 48.3% | 5.2 min late | 16.9 min late | 871 · 6 days |
| 17:00 | 53.9% | 4.8 min late | 13 min late | 714 · 8 days |
| 18:00 | 75.3% | 1.1 min late | 12.1 min late | 576 · 7 days |
| 19:00 | 61.5% | 3.8 min late | 14.1 min late | 706 · 8 days |
| 20:00 | 72.9% | 2.6 min late | 10.7 min late | 641 · 8 days |
| 21:00 | 65.0% | 3.4 min late | 9.1 min late | 694 · 6 days |
| 22:00 | 71.9% | 3.1 min late | 7.1 min late | 793 · 7 days |
| 23:00 | 83.7% | 1.5 min late | 8.9 min late | 632 · 7 days |
10 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
Scheduled bus, but not observed in realtime
285 / 554 scheduled trips published at least one position across 7 service days (51.4%).
- 14:0016 / 22 trips without a position27.3%
- 23:0016 / 23 trips without a position30.4%
- 00:0010 / 15 trips without a position33.3%
- 22:0016 / 28 trips without a position42.9%
- 21:0015 / 27 trips without a position44.4%
- 20:0014 / 26 trips without a position46.2%
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.
Arrival check: the last prediction within ten minutes of arrival, counted once per trip, stop and service date. Trip check: the timetable kept before each service day, matched to recorded positions. Exact IDs are preferred; an OC timetable suffix is matched only to one trip on the same route and date with an overlapping time window. Missing timetables, ambiguous matches and feed gaps stay labelled; they are not confirmed no-shows. Sources and limitations.
See all stops and route patterns
Stops and stations
12 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 Rideau: BAYSHORE A to RIDEAU B
35 stops · 42 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
12 official service records
3 added dates and 23 removed dates
- View stops and calendar →
Towards Tunney's Pasture: DISCOVERY / NETWORK ACCESS to TUNNEY'S PASTURE C
54 stops · 185 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 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 Tunney's Pasture: DISCOVERY / NETWORK ACCESS to TUNNEY'S PASTURE C
53 stops · 103 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
12 official service records
3 added dates and 23 removed dates
- View stops and calendar →
Towards Tunney's Pasture: MOODIE / FITZGERALD to TUNNEY'S PASTURE C
48 stops · 2 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 2026
Published weekly days: Saturday
2 official service records
1 added date and 5 removed dates
- View stops and calendar →
Towards Tunney's Pasture: BAYSHORE A to TUNNEY'S PASTURE C
20 stops · 15 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 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 Tunney's Pasture: BAYSHORE A to TUNNEY'S PASTURE C
19 stops · 81 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
12 official service records
3 added dates and 23 removed dates
- View stops and calendar →
Towards Bayshore: RIDEAU A to BAYSHORE C
32 stops · 57 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
12 official service records
3 added dates and 23 removed dates
- View stops and calendar →
Towards Bayshore: TUNNEY'S PASTURE B to BAYSHORE C
18 stops · 89 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
12 official service records
3 added dates and 23 removed dates
- View stops and calendar →
Towards Bells Corners: TUNNEY'S PASTURE B to FITZGERALD / AD. 25
47 stops · 2 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 2026
Published weekly days: Saturday
2 official service records
1 added date and 5 removed dates
- View stops and calendar →
Towards Carling Campus ~ Complexe Carling: TUNNEY'S PASTURE B to DISCOVERY / NETWORK ACCESS
56 stops · 95 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
12 official service records
3 added dates and 23 removed dates
- View stops and calendar →
Towards Carling Campus ~ Complexe Carling: TUNNEY'S PASTURE B to DISCOVERY / NETWORK ACCESS
55 stops · 185 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 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 Carling Campus ~ Complexe Carling: FITZGERALD / AD. 25 to DISCOVERY / NETWORK ACCESS
10 stops · 5 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday
5 official service records
0 added dates and 1 removed date
Official feed version 37ff8dfc-21cc-48c3-9eba-fc0d2e50b2ad
Source checksum e0b417f2ea03fcf035ed795c07b47461157b81b0c43d43639094105ed66b0a4a
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
- Collected or observed
- Computed or assembled
- Sample
- 32,023 settled arrivals across 1 matching reliability records.
- Coverage
- 12 published stop patterns containing 447 stop calls are available on this page.
- Method or data version
- last-prediction-within-ten-minutes-v1; 37ff8dfc-21cc-48c3-9eba-fc0d2e50b2ad; e0b417f2ea03fcf035ed795c07b47461157b81b0c43d43639094105ed66b0a4a
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.