Station · STO
Station MONTCALM
Performance
Service delivery · evidence state
Service at Station MONTCALM
Cancellations at this station
Local count cannot be published
Exact stop-call evidence could not be read for Oct 17, 2026 – Oct 23, 2026. No zero is assumed.
Dates, source versions and limits
Method: retained-pre-service-exact-trip-stop-call-v1. Cancellation-feed completeness and position coverage are unverified.
The retained timetables were fetched, imported and first activated before the service day. The archive does not prove they remained the active timetables throughout that period. Comparisons between places remain unavailable.
- Departure-board snapshot
- 32 listed departures · 3 live provider predictions
- Prediction agreement
- 72.8% predicted within five minutes of schedule. 2,185 eligible provider predictions; arrivals not independently measured
Server snapshot assembled Oct 24, 2026, 11:33 a.m.; open Departures for a refreshed board. This is not a cancellation count.
Bus prediction reliability at this station
Verdict
Bus prediction reliability at this station
Early evidence: 5 of 20 weekdays with eligible final provider predictions. This updates hourly; more records will make the estimate steadier.
72.8% of final provider predictions within 5 minutes of the timetable, from 2,185 predictions over 5 weekdays. The lowest sampled hour is 19:00 at 60%.
Median predicted difference from the timetable: 3 min late. At the 95th percentile: 11 min late.
Final provider predictions for conventional bus arrivals at OC Transpo and STO stations; physical arrivals are not independently verified. Express (200/500), shopper/community (300), event (400), and school (600) routes are excluded because each needs a purpose-specific measure. STO routes are included and graded by their own families: Rapibus 100, 200, 400 and 800 count, and STO school journeys numbered 300 and above are excluded the way OC Transpo’s 600s are. Each operator is measured against its own service, never against the other’s.
We use the agency’s last prediction within ten minutes of each scheduled arrival. 5 weekdays with eligible predictions, 2026-10-17 to 2026-10-24. Within five minutes means the final prediction differs from the schedule by no more than five minutes.
- 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: 89% of final predictions within five minutes of the timetable, 109 predictions, typically 1.1 min late
- 07:00: 82.5% of final predictions within five minutes of the timetable, 171 predictions, typically 2.2 min late
- 08:00: 77% of final predictions within five minutes of the timetable, 174 predictions, typically 1.7 min late
- 09:00: 72.2% of final predictions within five minutes of the timetable, 97 predictions, typically 2.6 min late
- 10:00: 70.3% of final predictions within five minutes of the timetable, 111 predictions, typically 2.6 min late
- 11:00: 77.9% of final predictions within five minutes of the timetable, 113 predictions, typically 2.5 min late
- 12:00: 78.4% of final predictions within five minutes of the timetable, 125 predictions, typically 2.6 min late
- 13:00: 75.2% of final predictions within five minutes of the timetable, 113 predictions, typically 3.3 min late
- 14:00: 69.2% of final predictions within five minutes of the timetable, 117 predictions, typically 3 min late
- 15:00: 67.4% of final predictions within five minutes of the timetable, 193 predictions, typically 3.4 min late
- 16:00: 65.9% of final predictions within five minutes of the timetable, 170 predictions, typically 3.3 min late
- 17:00: 69.4% of final predictions within five minutes of the timetable, 157 predictions, typically 3.2 min late
- 18:00: 64.9% of final predictions within five minutes of the timetable, 94 predictions, typically 3.6 min late
- 19:00: 60.2% of final predictions within five minutes of the timetable, 88 predictions, typically 4.2 min late
- 20:00: 65.5% of final predictions within five minutes of the timetable, 84 predictions, typically 2.7 min late
- 21:00: 71.8% of final predictions within five minutes of the timetable, 78 predictions, typically 2.7 min late
- 22:00: 67.1% of final predictions within five minutes of the timetable, 82 predictions, typically 3 min late
- 23:00: 82.7% of final predictions within five minutes of the timetable, 52 predictions, typically 2.9 min late
- 90% or more of predictions within five minutes
- 80 to 90% of predictions within five minutes
- under 80% of predictions within five minutes
- not enough data
| What | When | Measured | Scenario or next investigation |
|---|---|---|---|
| ProblemPredictions later than timetable | 13:00 | 3.3 min late | Running time on the routes here |
| ProblemPredictions later than timetable | 15:00 to 20:00 | 3.5 min late | Running time on the routes here |
How Station MONTCALM is doing
These indicators separate repeated delay from variation in the operator’s arrival predictions. They suggest questions for planners and operations staff; they do not establish the cause or prove when buses arrived. Each figure shows its route-hour sample.
Measured over 18 route-hours. 0 more were observed too thinly to count, and are excluded rather than assumed good.
Scheduling
Repeated late predictions can point to a timetable worth reviewing. Check actual arrival and dispatch records before deciding whether running time needs to change.
- Who can fix it
- A service planner
- What it costs
- Cost unavailable until fleet, labour, recovery and transfer effects are tested.
Predictions close to the timetable
66.7%
Route-hours where the median eligible arrival prediction is less than one minute early and less than three minutes late.
Route-hours with repeated late predictions
6of 18
Route-hours where the median eligible arrival prediction is at least three minutes late. Review running time against actual operating records.
Route-hours with early predictions
0of 18
Route-hours where the median eligible arrival prediction is at least one minute early. This does not establish that buses departed early.
Typical predicted delay
3.4min
The typical median predicted delay in flagged route-hours; not a validated amount to add to the timetable.
Operations: not measurable here
This site records a median delay for each hour at a stop, and no percentile, so the gap between a normal trip and a bad one cannot be worked out. That is a limit of our own measurement, not a finding about this place.
Measurements
Calculated: · Method: settled-arrivals-oc-sto-conventional-v5
- Predictions later than timetable · 13:00
- Median delay 3.3 min
- Measured arrivals 113
- On time 75.2%
- Predictions later than timetable · 15:00 to 20:00
- Median delay 3.5 min
- Measured arrivals 702
- On time 65.9%
MONTCALM right now
- Next departures
- 11:41 a.m.800 Lorrain
- 11:45 a.m.38 Freeman
- 11:51 a.m.400 Lorrain
- Timetable and live times as of 11:33 a.m. The board below keeps updating.
Checking alerts and elevators.
Station actions
Opens your device’s print dialog. Choose Save as PDF when available.
Print view prepared from the station record shown on this page. https://otranspo.ca/en/stations/sto%3A2573
Rate or report an issue
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
- Elevator unavailable
- Accessibility barrier
- Washroom unavailable
- Cleanliness
- Graffiti
- Damage
- Lighting
- Snow or ice
- Safety
- Other issue
Emergency: call 9-1-1. Check official OC Transpo or STO notices before travelling.
Evidence behind this pageOpen the definition, method, sources, dates, coverage, and known limits.
What is being shown
A current station board assembled from the imported timetable and any usable operator prediction for each trip.
How it was produced
Platforms sharing the station stop code are grouped, scheduled trips are read from the current GTFS, and a live time is used only when the operator publishes a matching prediction.
Evidence dates
- Computed or assembled
- Sample
- 32 departures across 5 published platform records in the current four-hour board.
- Coverage
- 3 departures have a published live prediction; 29 are timetable-only.
Sources
Limits to keep in mind
- OC Transpo does not publish live rail positions or predictions in the feed used here, so rail times are timetable-only.
- The stop source does not publish a complete station accessibility chain, entrances, or indoor paths.
Contains information licensed under the Open Government Licence – City of Ottawa.