STO · Regular service
Labrosse, La Cité
Choose a destination, then select a stop on the map or route diagram.
0 verified representative shapes · 45 stops
Dashed lines connect the published stop order; they are not claimed street paths
A solid line matches one published representative trip whose stops and order were checked. Another trip with the same stops may follow a different shape. Dashed lines connect published stops only; they do not describe streets.
This view does not show live vehicle positions.
All published paths
Different journeys can take different branches. Choose a published path above to see its stops in order.
You can also select any stop on the map to open its departure board.
Published stop order does not prove that a vehicle is running now.
Scheduled from Sep 27, 2026 to Nov 22, 2026
This service is published only as specific added dates, not as a weekly calendar.
6 official service records
57 added dates and 0 removed dates
Service sto:H01S026A-Samedi-0-_26AUT-0000010-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 3, 2026, Oct 10, 2026, Oct 17, 2026, Oct 24, 2026, Oct 31, 2026, Nov 7, 2026, Nov 14, 2026, Nov 21, 2026
Service sto:H01S026A-Samedi-10-_26AUT-0000010-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 12, 2026
Service sto:H01S026I-Dimanche-0-_26AUT-0000001-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 27, 2026, Oct 4, 2026, Oct 11, 2026, Oct 18, 2026, Oct 25, 2026, Nov 1, 2026, Nov 8, 2026, Nov 15, 2026, Nov 22, 2026
Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026
Service sto:H01S026A-Samedi-0-_26AUT-0000010-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 3, 2026, Oct 10, 2026, Oct 17, 2026, Oct 24, 2026, Oct 31, 2026, Nov 7, 2026, Nov 14, 2026, Nov 21, 2026
Service sto:H01S026A-Samedi-10-_26AUT-0000010-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 12, 2026
Service sto:H01S026I-Dimanche-0-_26AUT-0000001-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 27, 2026, Oct 4, 2026, Oct 11, 2026, Oct 18, 2026, Oct 25, 2026, Nov 1, 2026, Nov 8, 2026, Nov 15, 2026, Nov 22, 2026
Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026
Scheduled from Sep 27, 2026 to Nov 22, 2026
This service is published only as specific added dates, not as a weekly calendar.
6 official service records
57 added dates and 0 removed dates
Service sto:H01S026A-Samedi-0-_26AUT-0000010-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 3, 2026, Oct 10, 2026, Oct 17, 2026, Oct 24, 2026, Oct 31, 2026, Nov 7, 2026, Nov 14, 2026, Nov 21, 2026
Service sto:H01S026A-Samedi-10-_26AUT-0000010-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 12, 2026
Service sto:H01S026I-Dimanche-0-_26AUT-0000001-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 27, 2026, Oct 4, 2026, Oct 11, 2026, Oct 18, 2026, Oct 25, 2026, Nov 1, 2026, Nov 8, 2026, Nov 15, 2026, Nov 22, 2026
Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026
Service sto:H01S026A-Samedi-0-_26AUT-0000010-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 3, 2026, Oct 10, 2026, Oct 17, 2026, Oct 24, 2026, Oct 31, 2026, Nov 7, 2026, Nov 14, 2026, Nov 21, 2026
Service sto:H01S026A-Samedi-10-_26AUT-0000010-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 12, 2026
Service sto:H01S026I-Dimanche-0-_26AUT-0000001-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 27, 2026, Oct 4, 2026, Oct 11, 2026, Oct 18, 2026, Oct 25, 2026, Nov 1, 2026, Nov 8, 2026, Nov 15, 2026, Nov 22, 2026
Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:76
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026
Official feed version ca455c71-c30a-4e4d-8b72-2709212731cd
Source checksum a7e1f22955084828484cca5e8f1ebff9e785c70984ad5dd93b872a5d64ace6e4
Some imported trips are marked accessible and others are not or are unstated; verify each departure.
Would you count on route 76?
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 1, 2026 – Oct 7, 2026
—
No retained notice returned; this does not prove zero cancellations. 1 partial-capture day not counted.
4
4 of 344 trips with a usable feed window (1.2%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
340 with position · 4 to investigate · 70 excluded · 414 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Oct 8, 2026, 11:31 p.m..
0 of 1 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.
70 scheduled trips were excluded from the position check for feed or identity gaps.
Published position coverage: 340 / 414 (82.1%). 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 8, 2026, 10:40 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.
1 partial-capture day not counted.
1 scheduled trips with counted cancellation notices from Thu, Sep 10 to Wed, Oct 7.
Not counted: 2 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
Hours with the most cancellations: 4 p.m. (1)
A cause is shown only when STO’s own alert for that trip gives one.
Did not come (no bus seen, no notice), last 7 days: 4 of 344 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.
No time of day was usually busy in the last eight weeks.
| When this route is usually busy | Weekdays | Saturdays | Sundays |
|---|---|---|---|
| Before 6 am | Usually seats0% of 31 trips | Not enough readings | Not enough readings |
| 6 to 9 am | Usually seats0.7% of 452 trips | Usually seats0% of 39 trips | Usually seats0% of 32 trips |
| 9 am to 3 pm | Usually seats1.2% of 755 trips | Usually seats0% of 89 trips | Usually seats0% of 88 trips |
| 3 to 6 pm | Usually seats4% of 497 trips | Usually seats0% of 41 trips | Usually seats0% of 50 trips |
| 6 to 10 pm | Usually seats0% of 344 trips | Usually seats0% of 52 trips | Usually seats0% of 60 trips |
| After 10 pm | Usually seats0% of 114 trips | Usually seats0% of 13 trips | Usually seats0% of 13 trips |
Based on 56 computed days.
Predictions against the timetable
88.1%
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
1 partial-capture day 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.
20 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.
Route check
A short summary of what we know. We say so when we cannot answer a question.
Bottom line
Provider predictions were usually close to schedule in this dated sample.
88 in 100 eligible predictions were within 5 minutes of the timetable · 36,052 predictions checkedPrediction sample size: Larger sample
Based on 36,052 eligible provider predictions over 28 measured days, from Sep 9, 2026 to Oct 7, 2026.
Updated Oct 8, 2026, 10:32 p.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 repeated prediction-difference period has cleared the evidence threshold yet.
No current official notice matches this route.
Prediction differences by stop
60 in 100 eligible predictions differed from the timetable by more than 5 minutes (757 predictions over 29 days).
Open this stop57 in 100 eligible predictions differed from the timetable by more than 5 minutes (895 predictions over 29 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 16,643 arrivals over 13 days; after has 1,577 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 9, 2026 to October 7, 2026
| Hour | On time | Median | 95th percentile | Evidence |
|---|---|---|---|---|
| 00:00 | 100.0% | 0.5 min late | 2.1 min late | 30 · 10 days |
| 05:00 | 96.8% | 0.3 min late | 1.6 min late | 218 · 10 days |
| 06:00 | 94.3% | 1.2 min late | 3.3 min late | 965 · 10 days |
| 07:00 | 75.2% | 2.6 min late | 8 min late | 1,359 · 13 days |
| 08:00 | 94.1% | 1.3 min late | 4.9 min late | 1,284 · 13 days |
| 09:00 | 93.0% | 1.3 min late | 4.5 min late | 1,107 · 13 days |
| 10:00 | 93.0% | 2 min late | 5.1 min late | 880 · 13 days |
| 11:00 | 85.4% | 2.2 min late | 6.1 min late | 964 · 13 days |
| 12:00 | 91.7% | 1.5 min late | 5.3 min late | 988 · 13 days |
| 13:00 | 84.8% | 1.8 min late | 9.9 min late | 999 · 13 days |
| 14:00 | 85.8% | 2.2 min late | 6.2 min late | 996 · 13 days |
| 15:00 | 78.7% | 3 min late | 8.1 min late | 1,006 · 13 days |
| 16:00 | 84.7% | 2.1 min late | 7.1 min late | 1,188 · 13 days |
| 17:00 | 93.3% | 1.7 min late | 4.8 min late | 1,202 · 13 days |
| 18:00 | 87.0% | 1.9 min late | 7.4 min late | 953 · 13 days |
| 19:00 | 94.0% | 0.9 min late | 3.9 min late | 697 · 13 days |
| 20:00 | 95.5% | 1.4 min late | 4 min late | 621 · 13 days |
| 21:00 | 96.9% | 0.6 min late | 3.1 min late | 540 · 12 days |
| 22:00 | 95.9% | 0.8 min late | 3.5 min late | 561 · 13 days |
| 23:00 | 98.0% | 1 min late | 2.7 min late | 205 · 9 days |
No repeated pattern below 70% is yet established across at least three service days.
340 / 344 scheduled trips published at least one position across 4 service days (98.8%).
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 7, 2026 · 70 trips in the retained timetable · retained notices; capture coverage unverified
In short: 70 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.
