STO · Regular service
Cégep GRoy, Pob Allum
Choose a destination, then find your stop on this route.
Search by stop name or code. Results follow the published stop order, not distance.
Enter a stop name or code to see matching stops.
Service date: October 9, 2026
0 official shapes · 88 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.
Repeated problem stops: PARC-O-BUS ALLUMETTIÈRES, des ALLUMETTIÈRES/WILFRID-LAVIGNE, des ALLUMETTIÈRES/SAMUEL-EDEY, VANIER/des ALLUMETTIÈRES, de la CITÉ-DES-JEUNES/SAINT-RAYMOND and 7 more. These are highlighted from route-specific provider predictions compared with the timetable, with at least 60 eligible predictions over 3 days. They do not establish actual arrivals or a cause.
The line is the official route. Dots show published stops, buses seen now and stops named in current notices.
Buses we can see right now appear on the route below. A marker stops when we stop hearing from that bus. We never make up movement.
Service date October 9, 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.
Towards Cégep GRoy
Starts at PARC-O-BUS ALLUMETTIÈRES
Timetable only. No usable prediction is available for this trip.
Towards Cégep GRoy
Starts at PARC-O-BUS ALLUMETTIÈRES
Timetable only. No usable prediction is available for this trip.
Towards Cégep GRoy
Starts at VANIER/du PLATEAU
Timetable only. No usable prediction is available for this trip.
Towards Cégep GRoy
Starts at PARC-O-BUS ALLUMETTIÈRES
Timetable only. No usable prediction is available for this trip.
Showing 4 of 6 trips. Open a stop for its full departure board.
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 Oct 9, 5:53 a.m.
Would you count on route 50?
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 public link is shared, with a short tag that names the app you picked. Panel state, location, receipts, and other browser-only details are left out. Email and social services apply their own privacy terms.
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 STO GTFS. Check the Alerts panel for current official notices and each stop page for observed departures.
Scheduled service and available evidence
Evidence period: Oct 2, 2026 – Oct 8, 2026
—
No retained notice returned; this does not prove zero cancellations. 2 partial-capture days not counted.
0
0 of 36 trips with a usable feed window (0%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
36 with position · 0 to investigate · 9 excluded · 45 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Oct 9, 2026, 5:53 a.m..
0 of 6 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.
9 scheduled trips were excluded from the position check for feed or identity gaps.
Published position coverage: 36 / 45 (80%). This is not a delivered-service rate. 7 service days in this source.
Timetables retained before the service day: 7 / 7 requested days · 0 missing days.
Historical calculation: Oct 9, 2026, 4:37 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.
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.
Did not come (no bus seen, no notice), last 7 days: none of the trips we could check.
Not measured yet. The daily count has not reached these days, so there is no number to show.
From the load level STO’s buses report, over the last eight weeks. A time is marked usually busy when at least half of the trips with a reading reached standing room or fuller.
| When this route is usually busy | Weekdays | Saturdays | Sundays |
|---|---|---|---|
| Before 6 am | Not enough readings | Not enough readings | Not enough readings |
| 6 to 9 am | Usually seats47.4% of 137 trips | Not enough readings | Not enough readings |
| 9 am to 3 pm | Usually busy53.3% of 30 trips | Not enough readings | Not enough readings |
| 3 to 6 pm | Usually seats43.9% of 57 trips | Not enough readings | Not enough readings |
| 6 to 10 pm | Usually seats39.4% of 33 trips | Not enough readings | Not enough readings |
| After 10 pm | Not enough readings | Not enough readings | Not enough readings |
Based on 55 computed days.
Predictions against the timetable
76.6%
of eligible provider predictions were within five minutes of the timetable.
These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.
Calculated: Oct 9, 2026
2 partial-capture days not counted.
Explore the dated evidence Source of this resultShare of predictions within five minutes of the timetable. Only eligible hours are shown; an absent hour does not mean zero.
7 hourly cohorts meet the thresholds of 30 predictions and 5 service days. Hourly thresholds are assessed separately from the route-wide aggregate.
Improvement or decline requires comparable periods. This single result cannot establish a trend.
Verdict
Median provider predictions are 3.5 to 6.3 min later than the timetable in 2 hours of the day.
08:00 has 38% of predictions within five minutes of the timetable, against 77% the rest of the day.
Scenario: 4 to 6 min more running time on 6 trips. The schedule-block model adds no buses; fleet and workforce feasibility are unverified.
Assumptions: published departure times, trip blocks and service pattern stay fixed while running time changes. A scheduler must test headways, transfers, recovery, fleet circulation, operator shifts, labour rules and cost before use.
| What | When | Measured | Scenario or next investigation |
|---|---|---|---|
| ProblemPredictions later than timetable | 06:00 · 08:00 | 3.5 min late · 6.3 min late | More running time |
| ProblemOne hour has a lower prediction match | 08:00 | 38% | Operations, not the timetable |
Route check
A short summary of what we know. We say so when we cannot answer a question.
Bottom line
Provider predictions often differed from the timetable; actual arrivals were not independently measured.
77 in 100 eligible predictions were within 5 minutes of the timetable · 7,103 predictions checkedPrediction sample size: Larger sample
Based on 7,103 eligible provider predictions over 19 measured days, from Sep 10, 2026 to Oct 8, 2026.
Updated Oct 9, 2026, 4:33 a.m.
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.
No current official notice matches this route.
Prediction differences by stop
58 in 100 eligible predictions differed from the timetable by more than 5 minutes (104 predictions over 21 days).
Open this stop55 in 100 eligible predictions differed from the timetable by more than 5 minutes (60 predictions over 21 days).
Open this stop51 in 100 eligible predictions differed from the timetable by more than 5 minutes (125 predictions over 21 days).
Open this stop50 in 100 eligible predictions differed from the timetable by more than 5 minutes (125 predictions over 21 days).
Open this stopThese are route-specific provider predictions compared with the timetable. They identify repeated prediction differences at a place and time, not measured arrivals or their cause.
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 7, 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 5, 2026
Operator calendar-date records: 1 added · 0 removed
Feed fingerprint: a7e1f22955084828 · ca455c71-c30a-4e4d-8b72-2709212731cd
Service date checked: October 12, 2026
Operator calendar-date records: 1 added · 0 removed
Feed fingerprint: 529c515442564d26 · 816c00d7-757c-47a0-a3ab-42cbe122301d
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.
Still collecting: before has 3,413 arrivals over 9 days; after has 384 arrivals over 1 days. No improvement or decline is claimed yet.
Checksums let anyone verify which retained timetable produced the counts. A changed count does not identify a cause, cancellation, operator decision, or passenger impact.
We compare the last eligible provider prediction for each scheduled arrival with the official schedule. These are not independently measured arrivals. A result needs at least 200 eligible predictions. Within 5 minutes is the rider-facing target used here.
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.
Provisional results, published evidence
Each hour compares the last eligible provider prediction for a scheduled arrival with the timetable. “Within 5 minutes” describes that prediction difference, not a measured arrival or proof that a bus ran.
Evidence window: September 10, 2026 to October 8, 2026
| Hour | On time | Median | 95th percentile | Evidence |
|---|---|---|---|---|
| 06:00 | 84.4% | 3.5 min late | 5.9 min late | 392 · 8 days |
| 07:00 | 77.0% | 1.9 min late | 10.4 min late | 984 · 8 days |
| 08:00 | 37.5% | 6.3 min late | 10.3 min late | 344 · 8 days |
| 09:00 | 70.1% | 2.7 min late | 9.4 min late | 368 · 8 days |
| 16:00 | 77.1% | 2.8 min late | 8.9 min late | 328 · 8 days |
| 17:00 | 89.3% | 0.8 min late | 6.1 min late | 328 · 8 days |
| 18:00 | 96.5% | 0 min early | 2.6 min late | 287 · 7 days |
1 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
27 / 27 scheduled trips published at least one position across 3 service days (100.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.
Prediction check: the last eligible provider prediction no earlier than ten minutes before the scheduled arrival, counted once per trip, stop and scheduled Toronto calendar date. It is compared with the timetable, not an independently measured arrival. Trip-position 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.
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 8, 2026 · 9 trips in the retained timetable · retained notices; capture coverage unverified
In short: 9 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.
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.
