Map
FREvery 12 min
Scheduled service and available evidence
Evidence period: Oct 28, 2026 – Nov 3, 2026
—
No retained notice returned; this does not prove zero cancellations.
Not published
OC Transpo publishes no train positions, so train trips cannot be checked here.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 4, 2026, 9:44 p.m..
0 of 12 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.
OC Transpo publishes no train positions; no position check is made for this route.
Timetables retained before the service day: 7 / 7 requested days · 0 missing days.
Historical calculation: Nov 4, 2026, 8:38 p.m.
Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.
Predictions against the timetable
No comparable percentage published
The public feed received does not provide train arrival predictions from which to calculate this result.
These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.
The general hourly comparison is not suitable for this service purpose. Source records remain available.
Improvement or decline requires comparable periods. This single result cannot establish a trend.
Road work and event road closures the City of Ottawa has published, measured as near this route’s path. Near is not proof that the bus is detoured: check the operator’s own alerts for that.
Road work
Place Hintonburg Place between Bayswater and dead end
Aug 9, 2026, 7:00 a.m. to Dec 31, 2026, 5:00 p.m.
Place Hintonburg Place reduced to 1 lane with alternating traffic between Bayswater and dead end due to construction. Flagpersons present. From 7:00am, 09/08/26 to 5:00pm, 31/12/26
The City marks this as affecting transit.
about 16 m from the route
City record updated Sep 4, 2026, 4:12 p.m..
Road work
Heron between Bronson and Data Centre rd
Oct 15, 2026, 12:00 a.m. to Nov 13, 2026, 5:00 p.m.
Heron off-peak lane reductions between Bronson and Data Centre rd due to construction, from October 15th to November 13th.
The City marks this as affecting transit.
about 0 m from the route
City record updated Oct 16, 2026, 1:00 p.m..
A route counts as near when its timetable path passes within 40 m of the City’s mapped closure; a stop counts when it is within 75 m.
Source: City of Ottawa traffic events (road work and closures). Contains information licensed under the Open Government Licence, City of Ottawa. The City says this list is best effort and may be incomplete. City of Ottawa traffic map ↗
2 partial-capture days not counted.
No counted cancellations on this route in the last four weeks. Notices we could not check would be listed below.
Route check
A short summary of what we know. We say so when we cannot answer a question.
Bottom line
Public data cannot rate this train line live. Check official alerts and rider reports below.
Available evidence: the official timetable, official service alerts, train research, and dated rider observations. None is presented as a live train position.
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 October 30, 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: October 26, 2026
Operator calendar-date records: 0 added · 2 removed
Feed fingerprint: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad
Service date checked: November 2, 2026
Operator calendar-date records: 0 added · 2 removed
Feed fingerprint: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945
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.
The public feed has no live O-Train positions or predictions. The schedule comparison is visible, but a train reliability before-and-after score cannot be produced from missing realtime rail data.
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 live grade is published. Official alerts, the timetable, research, and dated observations stay separate and auditable until OC Transpo publishes dependable realtime rail data.
The public feed does not provide live train positions, arrival predictions, dependable passenger counts, or proof that a scheduled train ran. A timetable entry is not a live observation.
O-Train evidence
Trains are not in the public data feed
The bus punctuality reports compare archived arrival predictions with published schedules. They do not count independently measured physical arrivals. Otranspo has no comparable public train-position dataset for these reports, so those bus figures cannot show where a train is or whether Lines 1, 2 and 4 run on time.
Publishing train positions, their timestamps, and the measurement method would help build a separate, verifiable record of rail service. The missing dataset does not establish how the trains performed.
These are rider sightings approved by a moderator. They show a reported time and place. They are not official train positions, a complete train count, or proof of a cause.
No approved rider observation matches this place or line in the last 31 days. That does not mean no train ran or no problem occurred.