Site usage analyticsWhat is collected
Usage analytics is on by default to improve Otranspo. You can turn it off here.
Loading: Loading the route history. Live times above are ready to use.
Would you count on route 582?
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.
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.
Scheduled service and available evidence
Evidence period: Oct 23, 2026 – Oct 29, 2026
—
No retained notice returned; this does not prove zero cancellations.
—
No sufficiently checked population here; no zero inferred.
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: Oct 30, 2026, 4:44 a.m..
0 scheduled trips were excluded from the position check for feed or identity gaps.
Position coverage unavailable; no delivered-service rate inferred.
Timetables retained before the service day: 7 / 7 requested days · 0 missing days.
Historical calculation: Oct 30, 2026, 3:49 a.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
This service purpose needs a different method. A general percentage could give a misleading picture.
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.
Last 28 days, October 2, 2026 to October 29, 2026: 24 days counted.
3 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: October 2, 2026, October 8, 2026, October 15, 2026.
Too few buses were measured to judge bunching: 0 pairs checked, 30 needed.
Not enough trips yet to measure speed between timepoints (20 trips needed for each segment).
How this is measured →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
Baseline between Cornell and McWatters
Mar 30, 2026, 7:00 a.m. to Nov 30, 2026, 5:00 p.m.
Baseline lane reductions in both directions between Cornell and McWatters due to construction. Follow the signed detour. From Monday, March 30 to Monday, November 30.
The City marks this as affecting transit.
about 0 m from the route
City record updated Sep 22, 2026, 3:24 p.m..
Road work
Greenbank between Lisa and Monterey
Mar 30, 2026, 7:00 a.m. to Nov 30, 2026, 5:00 p.m.
Greenbank lane reductions in both directions between Lisa and Monterey due to construction. Follow the signed detour. From Monday, March 30 to Monday, November 30.
The City marks this as affecting transit.
about 0 m from the route
City record updated Sep 4, 2026, 8:36 a.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 ↗
3 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
We need to know where this express route picks people up before we can rate it.
Prediction sample size: Still building
There are not enough eligible predictions to publish a route comparison yet.
These are repeated prediction-to-timetable differences, not independently measured service failures. They use the same eligible predictions as the result above, but group by stop rather than hour, so the 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.
Prediction differences by stop
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 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.
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.
Inbound performance must be checked at pickup points. Early outbound running after pickups are finished is not treated like early service on a regular route.
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.
Evidence cannot be read right now; no replacement figure is invented.
Dated service
The timetable, notices and what the live feed says are shown apart. Seeing a bus on the map does not prove you can board it.
October 29, 2026 · 0 trips in the retained timetable · retained notices; capture coverage unverified
No scheduled trips are available for this day in this source. This does not prove that no service ran.
The current public route group, its published schedule variants and stop patterns, current operations, and reliability from matching eligible final provider predictions 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.