Before
Service date checked: September 7, 2026
- Scheduled trips
- 0
- Distinct scheduled stops
- 0
- Distinct published paths
- 0
- Published service span
- —–—
Feed fingerprint: e0b417f2ea03fcf0 · 37ff8dfc-21cc-48c3-9eba-fc0d2e50b2ad
Otranspo
Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.
Route
687
OC Transpo
Merivale H.S ↔ Merivale Gardens
All imported trips are marked accessible.Imported schedule valid through: Oct 10, 2026
Verdict
What this route needs
Timetable short by 4.1 min in 2 hours of the day.
Fix: 4 min more running time on 7 trips. No extra buses.
This changes running time only. It does not move departure times, rewrite headways, or check that a driver’s shift still fits, and a scheduler has to.
- 00:00: not enough data
- 01:00: not enough data
- 02:00: not enough data
- 03:00: not enough data
- 04:00: not enough data
- 05:00: not enough data
- 06:00: not enough data
- 07:00: 89.6% of arrivals on time, 364 arrivals, typically 1.9 min late
- 08:00: not enough data
- 09:00: not enough data
- 10:00: not enough data
- 11:00: not enough data
- 12:00: not enough data
- 13:00: not enough data
- 14:00: 66.5% of arrivals on time, 200 arrivals, typically 4.2 min late
- 15:00: 68% of arrivals on time, 50 arrivals, typically 4 min late
- 16:00: not enough data
- 17:00: not enough data
- 18:00: not enough data
- 19:00: not enough data
- 20:00: not enough data
- 21:00: not enough data
- 22:00: not enough data
- 23:00: not enough data
- 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 | 14:00 to 16:00 | 4.1 min late | More running time |
Measurements
- Late by the timetable · 14:00 to 16:00
- medianDelaySeconds 246
- spreadSeconds 341
- observations 250
- hoursAffected 2
- suggestedRunningTimeChangeMinutes 4.1
14:00 30→34
Route check
How route 687 is doing
A plain-language summary of the strongest evidence we have. We say when the data cannot answer a question.
Bottom line
We need to confirm how this service is meant to work before rating it.
Confidence in this summary: Medium
Based on 614 arrivals over 8 weekdays, from Aug 14, 2026 to Sep 13, 2026.
Updated Sep 13, 2026, 8:32 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.
Problem times are not ranked because this service needs a purpose-specific test.
No current official notice matches this route.
Problem places
We do not yet have enough route-by-stop history to name a recurring problem stop. Rider reports are used as leads, not proof.
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 live cancellation answer
- Possible no-shows after checking feed gaps?
- 2 of 8 checked trips need a closer look
- How late does this route get?
- Not enough evidence yet
- Do buses bunch or leave long gaps?
- No route-level result meets the evidence threshold yet. This does not mean gaps did not happen.
OC Transpo’s live trip-update feed did not answer this check. That is a feed gap. It does not mean zero cancellations, and it is not proof of a cancellation. Open the evidence to see the schedule, retained explicit cancellation notices, and every labelled data gap.
2 of 8 trips with enough public-feed evidence had no matching position over 7 days. 0 of 8 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
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 10, 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 14, 2026
- Scheduled trips
- 2
- Distinct scheduled stops
- 72
- Distinct published paths
- 2
- Published service span
- 07:17–15:08
Feed fingerprint: d6d50360bb16d494 · 151dbfc4-6745-4fbd-9eef-6885ecb708f4
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.
Ordinary on-time scoring does not fit this route’s service purpose. The schedule counts remain visible, but the result waits for the purpose-specific evidence described below.
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: School route
No grade is shown until a purpose-specific completion and pickup measure is available.
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 687?
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 · 72 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.
Today’s schedule
Service date September 13, 2026
The current official GTFS contains no service for this route on this service date.
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.
The realtime prediction feed is unavailable or stale. Timetable times remain labelled as scheduled only.
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 13, 9:33 p.m.
Provisional results, published evidence
Data behind this result
An ordinary on-time grade is not appropriate for this service without checking its purpose. The route check above explains the pickup, community-service or event evidence needed. You can still inspect the recorded trips and data gaps below.
Evidence window: August 14, 2026 to September 13, 2026
Scheduled bus, but not observed in realtime
6 / 8 scheduled trips published at least one position across 4 service days (75.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 Merivale: VAAN / WOODROFFE to MERIVALE / VIEWMOUNT
53 stops · 7 imported trips
Scheduled from Sep 10, 2026 to Oct 10, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday
7 official service records
2 added dates and 9 removed dates
- View stops and calendar →
Towards Nepean South ~ Nepean Sud: MERIVALE H.S (STUDENTS ONLY) to VAAN / COLEWAY
52 stops · 7 imported trips
Scheduled from Sep 10, 2026 to Oct 10, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday
7 official service records
2 added dates and 9 removed dates
Official feed version 151dbfc4-6745-4fbd-9eef-6885ecb708f4
Source checksum d6d50360bb16d4947e79ce46b61cdf1159a460a36e995ce284333c00050863b7
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
- 614 settled arrivals across 1 matching reliability records.
- Coverage
- 2 published stop patterns containing 105 stop calls are available on this page.
- Method or data version
- last-prediction-within-ten-minutes-v1; 151dbfc4-6745-4fbd-9eef-6885ecb708f4; d6d50360bb16d4947e79ce46b61cdf1159a460a36e995ce284333c00050863b7
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.