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
Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.
Route
OC Transpo
Verdict
Timetable short by 4.4 to 4.5 min in 2 hours of the day.
Buses leave on time and lose about 5.8 min along the route.
Fix: 4 to 5 min more running time on 42 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.
| What | When | Measured | Fix |
|---|---|---|---|
| ProblemLate by the timetable | 08:00 · 15:00 | 4.4 min late · 4.5 min late | More running time |
Route check
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: High
Based on 2,060 arrivals over 9 weekdays, from Aug 14, 2026 to Sep 13, 2026.
Updated Sep 13, 2026, 8:32 p.m.
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.
Open a time period to see each service day, scheduled trip, feed gap, observed public vehicle ID, and the exact counts behind this summary.
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.
11 of 44 trips with enough public-feed evidence had no matching position over 7 days. 0 of 44 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
Schedule change check
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 →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.
Service date checked: September 7, 2026
Feed fingerprint: e0b417f2ea03fcf0 · 37ff8dfc-21cc-48c3-9eba-fc0d2e50b2ad
Service date checked: September 14, 2026
Feed fingerprint: d6d50360bb16d494 · 151dbfc4-6745-4fbd-9eef-6885ecb708f4
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.
No grade is shown until a purpose-specific completion and pickup measure is available.
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.
Would you count on route 663?
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.
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
Fresh vehicle positions appear on the route below. A marker stops moving when the evidence runs out. We do not invent movement.
The line is the official route. Dots show published stops, buses seen now and stops named in current notices.
0 official shapes · 71 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.
Service date September 13, 2026
The current official GTFS contains no service for this route on this service date.
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.
The current healthy operator position feed contains no vehicle matched to this route.
No matching active notice appears in the current healthy operator feed.
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:32 p.m.
Provisional results, published evidence
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
33 / 44 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.
2 official stop patterns
Each row below is one exact stop order published in the official schedule. Short turns and alternate destinations stay separate.
35 stops · 42 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
37 stops · 35 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
The current public route group, its published schedule variants and stop patterns, current operations, and matching observed reliability where available.
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.
Rider evidence
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.