Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.
OC Transpo · Event service
Centre Canadian Tire Centre · Centre Canadian Tire Centre via Eagleson
Accessibility is unknown for some trips.
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 · 18 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 19, 2026
Span and median gap are computed from today’s official GTFS stop_times. They are timetable measures, not observed headways or a frequency guarantee.
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 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 19, 2:29 p.m.
3 official stop patterns
Each row below is one exact stop order published in the official schedule. Short turns and alternate destinations stay separate.
15 stops · 1 imported trip
Scheduled from Sep 18, 2026 to Oct 18, 2026
Published weekly days: Saturday
1 official service record
1 added date and 4 removed dates
8 stops · 2 imported trips
Scheduled from Sep 18, 2026 to Oct 18, 2026
Published weekly days: Wednesday
1 official service record
1 added date and 3 removed dates
17 stops · 4 imported trips
Scheduled from Sep 18, 2026 to Oct 18, 2026
Published weekly days: Wednesday, Saturday
2 official service records
2 added dates and 7 removed dates
Official feed version 99de510d-89b0-4652-9d93-217659284cf2
Source checksum 2f30d876ae731cae79cf274d036530bb78b0c14f6e0e994d1ad32ca16291b367
Would you count on route 404?
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.
Route check
A plain-language summary of the strongest evidence we have. We say when the data cannot answer a question.
Bottom line
This route needs event-release evidence before its departures can be rated fairly.
Confidence in this summary: Still building
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.
1 current notice affects 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.
Schedule change check
This compares the current retained official schedule with the prior retained version. Schedule changes are facts about what was planned; they do not prove that a trip ran.
Current published schedule began September 18, 2026
We check 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.
At least one selected date uses added or removed calendar-date service. Treat this as holiday or special-service context, not ordinary weekday growth.
Service date checked: September 14, 2026
Operator calendar-date records: 0 added · 3 removed
Feed fingerprint: d6d50360bb16d494 · 151dbfc4-6745-4fbd-9eef-6885ecb708f4
Service date checked: September 21, 2026
Operator calendar-date records: 0 added · 2 removed
Feed fingerprint: 2f30d876ae731cae · 99de510d-89b0-4652-9d93-217659284cf2
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.
A post-event departure is not called late when event-release evidence shows the event ended late. Without that context, the result stays uncertain.
Routes 404 and 406 need Canadian Tire Centre event-release evidence before post-event departures can be rated.
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.
Check the numbers
This route has more than one official schedule record. We keep each record separate so the totals stay checkable and we do not invent a combined worst-case result.
Open any result below to see the hours, denominators, observed days, and position coverage behind it.
No reliability cohort can be safely matched to this public route. No representative schedule record is substituted.
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.
