Before
Service date checked: August 31, 2026
- Scheduled trips
- 121
- Distinct scheduled stops
- 107
- Distinct published paths
- 2
- Published service span
- 05:51–25:01
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
14
OC Transpo
St-Laurent ↔ Tunney's Pasture
All imported trips are marked accessible.Imported schedule valid through: Oct 4, 2026
Verdict
What this route needs
Timetable short by 4.1 to 4.3 min in 13 hours of the day.
Buses already leave about 2.9 min late and hold it to the end. The running time is right; the terminal is the problem.
Unreliable 18:00 to 20:00: a bad trip runs 22.1 min behind a normal one.
21:00 drops to 40% on time, against 61% 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: 83.3% of arrivals on time, 825 arrivals, typically 1.7 min late
- 01:00: not enough data
- 02:00: not enough data
- 03:00: not enough data
- 04:00: not enough data
- 05:00: 100% of arrivals on time, 109 arrivals, typically 1.2 min late
- 06:00: 72.9% of arrivals on time, 1,730 arrivals, typically 2.3 min late
- 07:00: 70.6% of arrivals on time, 2,072 arrivals, typically 3.1 min late
- 08:00: 55.7% of arrivals on time, 1,562 arrivals, typically 4.1 min late
- 09:00: 56.2% of arrivals on time, 1,483 arrivals, typically 4 min late
- 10:00: 54.2% of arrivals on time, 1,480 arrivals, typically 4.3 min late
- 11:00: 59.2% of arrivals on time, 2,017 arrivals, typically 3.7 min late
- 12:00: 51.8% of arrivals on time, 1,596 arrivals, typically 4.4 min late
- 13:00: 54.4% of arrivals on time, 1,696 arrivals, typically 4.4 min late
- 14:00: 66.9% of arrivals on time, 1,564 arrivals, typically 2.8 min late
- 15:00: 55.6% of arrivals on time, 1,447 arrivals, typically 4 min late
- 16:00: 51.8% of arrivals on time, 1,186 arrivals, typically 4.7 min late
- 17:00: 68.8% of arrivals on time, 1,122 arrivals, typically 2.2 min late
- 18:00: 62.9% of arrivals on time, 1,111 arrivals, typically 2.1 min late. Unreliable: a bad trip runs far behind a normal one.
- 19:00: 72.9% of arrivals on time, 857 arrivals, typically 2.5 min late. Unreliable: a bad trip runs far behind a normal one.
- 20:00: 49.9% of arrivals on time, 860 arrivals, typically 4.7 min late
- 21:00: 39.6% of arrivals on time, 761 arrivals, typically 6.7 min late
- 22:00: 64.7% of arrivals on time, 697 arrivals, typically 3.5 min late
- 23:00: 65.5% of arrivals on time, 984 arrivals, typically 3.2 min late
- 90% or more on time
- 80 to 90% on time
- under 80% on time
- not enough data
- unreliable: a bad trip runs 20 min or more behind a normal one
| What | When | Measured | Fix |
|---|---|---|---|
| ProblemLate by the timetable | 07:00 to 14:00 · 15:00 to 17:00 · 20:00 to 00:00 | 4.1 min late · 4.3 min late | Recovery time at the terminal |
| ProblemUnreliable | 18:00 to 20:00 | 22.1 min swing | Operations, not the timetable |
| ProblemOne hour collapses | 21:00 | 40% | Operations, not the timetable |
Measurements
- Late by the timetable · 07:00 to 14:00
- medianDelaySeconds 246
- spreadSeconds 708
- observations 11,906
- hoursAffected 7
- suggestedRunningTimeChangeMinutes 4.1
- Late by the timetable · 20:00 to 00:00
- medianDelaySeconds 245
- spreadSeconds 656
- observations 3,302
- hoursAffected 4
- suggestedRunningTimeChangeMinutes 4.1
- Late by the timetable · 15:00 to 17:00
- medianDelaySeconds 259
- spreadSeconds 884
- observations 2,633
- hoursAffected 2
- suggestedRunningTimeChangeMinutes 4.3
- Unreliable · 18:00 to 20:00
- medianDelaySeconds 140
- spreadSeconds 1,323
- observations 1,968
- hoursAffected 2
- suggestedRunningTimeChangeMinutes 2.3
- One hour collapses · 21:00
- hour 21
- onTimePct 39.6
- routeMedianOnTimePct 61.1
- shortfallPoints 21.4
- observations 761
07:00 56→6007:00 56→6008:00 60→6408:00 56→6009:00 55→5909:00 55→5910:00 56→6010:00 57→6111:00 58→6211:00 59→6312:00 59→6312:00 59→6313:00 60→6413:00 63→6715:00 66→7015:00 66→7016:00 65→6916:00 67→7120:00 52→5620:00 53→5721:00 51→5521:00 53→5722:00 48→5222:00 49→5323:00 43→4723:00 46→50
Route check
How route 14 is doing
A plain-language summary of the strongest evidence we have. We say when the data cannot answer a question.
Bottom line
This route is often far from its schedule.
56 in 100 arrivals were within 5 minutes of schedule · 41,751 arrivals checkedConfidence in this summary: High
Based on 41,751 arrivals over 19 weekdays, from Aug 8, 2026 to Sep 7, 2026.
Updated Sep 7, 2026, 11:34 p.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.
- 9 p.m.–10 p.m.: 60 in 100 arrivals were more than 5 minutes early or late (761 arrivals over 5 days).
- 8 p.m.–9 p.m.: 50 in 100 arrivals were more than 5 minutes early or late (860 arrivals over 8 days).
- 12 p.m.–1 p.m.: 48 in 100 arrivals were more than 5 minutes early or late (1,596 arrivals over 10 days).
- 4 p.m.–5 p.m.: 48 in 100 arrivals were more than 5 minutes early or late (1,186 arrivals over 6 days).
No current official notice matches this route.
Problem places
- PARKDALE / OXFORD
74 in 100 arrivals were more than 5 minutes early or late (377 arrivals over 18 days).
Open this stop - PARKDALE / WELLINGTON
73 in 100 arrivals were more than 5 minutes early or late (389 arrivals over 18 days).
Open this stop - SCOTT / PARKDALE
72 in 100 arrivals were more than 5 minutes early or late (378 arrivals over 18 days).
Open this stop - GLADSTONE / PARKDALE
71 in 100 arrivals were more than 5 minutes early or late (386 arrivals over 18 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?
- No trips start in the next 4 hours
- Possible no-shows after checking feed gaps?
- 311 of 663 checked trips need a closer look
- How late does this route get?
- The slowest 5 in 100 were more than about 23.7 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.
311 of 663 trips with enough public-feed evidence had no matching position over 7 days. 39 of 702 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
56 in 100 arrivals were within 5 minutes of schedule.
0.2 min beyond the scheduled wait, based on 10 arrivals at 1 high-frequency stop over 2 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
- 60
- Distinct scheduled stops
- 107
- Distinct published paths
- 2
- Published service span
- 06:55–24:45
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 22,665 arrivals over 11 days; after has 438 arrivals over 3 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 14?
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 · 107 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: GLADSTONE / ARTHUR, GLADSTONE / ROCHESTER, GLADSTONE / PRESTON, CORSO ITALIA A, GLADSTONE / LORETTA 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 St-Laurent
- 61 scheduled trips
- 5:51 a.m.–1:01 a.m. (next day)
- 16 min median scheduled gap
- Towards Tunney's Pasture
- 60 scheduled trips
- 5:51 a.m.–12:58 a.m. (next day)
- 15 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.
No upcoming trip start is published in the next four hours.
Buses seen now
The current healthy operator position feed contains no vehicle matched to this route.
Official notices
No matching active notice appears in the current healthy operator feed.
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, 1:43 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 8, 2026 to September 7, 2026
- Within 5 minutes of schedule
- 55.7%
- Arrivals checked
- 41,751
- Weekdays with data
- 19
- How late the worst 5 in 100 were
- 23.7 min late
Patterns by hour (21)
| Hour | On time | Median | Worst 5 in 100 | Evidence |
|---|---|---|---|---|
| 00:00 | 83.3% | 1.7 min late | 9.6 min late | 825 · 6 days |
| 01:00 | 100.0% | 1.9 min late | 3.9 min late | 71 · 1 days |
| 05:00 | 100.0% | 1.2 min late | 2.9 min late | 109 · 5 days |
| 06:00 | 72.9% | 2.3 min late | 8.5 min late | 1,730 · 7 days |
| 07:00 | 70.6% | 3.1 min late | 11.8 min late | 2,072 · 7 days |
| 08:00 | 55.7% | 4.1 min late | 16.4 min late | 1,562 · 8 days |
| 09:00 | 56.2% | 4 min late | 22.8 min late | 1,483 · 9 days |
| 10:00 | 54.2% | 4.3 min late | 15.7 min late | 1,480 · 9 days |
| 11:00 | 59.2% | 3.7 min late | 14 min late | 2,017 · 9 days |
| 12:00 | 51.8% | 4.4 min late | 22 min late | 1,596 · 10 days |
| 13:00 | 54.4% | 4.4 min late | 16.2 min late | 1,696 · 10 days |
| 14:00 | 66.9% | 2.8 min late | 19.5 min late | 1,564 · 7 days |
| 15:00 | 55.6% | 4 min late | 18.1 min late | 1,447 · 7 days |
| 16:00 | 51.8% | 4.7 min late | 20 min late | 1,186 · 6 days |
| 17:00 | 68.8% | 2.2 min late | 15.1 min late | 1,122 · 10 days |
| 18:00 | 62.9% | 2.1 min late | 25 min late | 1,111 · 10 days |
| 19:00 | 72.9% | 2.5 min late | 23.8 min late | 857 · 9 days |
| 20:00 | 49.9% | 4.7 min late | 24.1 min late | 860 · 8 days |
| 21:00 | 39.6% | 6.7 min late | 16.5 min late | 761 · 5 days |
| 22:00 | 64.7% | 3.5 min late | 10 min late | 697 · 7 days |
| 23:00 | 65.5% | 3.2 min late | 15.2 min late | 984 · 7 days |
15 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
349 / 642 scheduled trips published at least one position across 6 service days (54.4%).
- 14:0029 / 40 trips without a position27.5%
- 00:007 / 12 trips without a position41.7%
- 13:0023 / 44 trips without a position47.7%
- 15:0018 / 36 trips without a position50.0%
- 16:0022 / 44 trips without a position50.0%
- 18:0012 / 24 trips without a position50.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.
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
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 St-Laurent: TUNNEY'S PASTURE E to ST-LAURENT C
54 stops · 557 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: ST-LAURENT D to TUNNEY'S PASTURE E
54 stops · 544 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
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
- 41,751 settled arrivals across 1 matching reliability records.
- Coverage
- 2 published stop patterns containing 108 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.