No 76 trips cancelled now · 7 did not run in NovemberCancellations →

Previous measure: 89.2% of arrivals were within five minutes of the timetable (23,476 arrivals over 22 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.

STO route 76: La Vérendrye

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 29, 2026 – Nov 4, 2026

Scheduled trips with cancellation notices

Trips in the published timetable marked cancelled without qualifying later matching vehicle observations in our archive. This does not prove the trip did not operate. Trips with any notice: 1.

Trips needing investigation

8 of 326 trips with a usable feed window (2.5%) had no matching position.

These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.

318 with position · 8 to investigate · 88 excluded · 414 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 5, 2026, 1:53 a.m..

Coverage, exclusions and sources

0 of 1 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.

88 scheduled trips were excluded from the position check for feed or identity gaps.

Published position coverage: 318 / 414 (76.8%). 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: Nov 5, 2026, 1:08 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.

What does the evidence show?

Predictions against the timetable

89.2%

of eligible provider predictions were within five minutes of the timetable.

Predictions in the source: 23,476
Weekdays with evidence: 17
Evidence window: Oct 6, 2026 – Nov 3, 2026

The hours we have evidence for

5 a.m.99% · 152 predictions · 8 days
6 a.m.95% · 674 predictions · 8 days
7 a.m.93% · 774 predictions · 10 days
8 a.m.93% · 819 predictions · 11 days
9 a.m.89% · 916 predictions · 12 days
10 a.m.92% · 704 predictions · 11 days
11 a.m.92% · 780 predictions · 13 days
12 p.m.94% · 801 predictions · 12 days
1 p.m.88% · 849 predictions · 12 days
2 p.m.89% · 773 predictions · 13 days
3 p.m.77% · 814 predictions · 12 days
4 p.m.67% · 845 predictions · 13 days
5 p.m.87% · 864 predictions · 12 days
6 p.m.89% · 673 predictions · 11 days
7 p.m.96% · 511 predictions · 10 days
8 p.m.96% · 445 predictions · 10 days
9 p.m.94% · 403 predictions · 10 days
10 p.m.96% · 443 predictions · 10 days
11 p.m.99% · 161 predictions · 8 days

Share of predictions within five minutes of the timetable. Only eligible hours are shown; an absent hour does not mean zero.

These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.

Calculated: Nov 5, 2026

6 partial-capture days not counted.

What about time of day?

19 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.

Explore the dated evidence Source of this result

Buses arriving bunched

Last 28 days, October 8, 2026 to November 4, 2026: 20 days counted.

2 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: October 8, 2026, October 12, 2026.

Values and interpretation

0% of back-to-back buses on this route arrived bunched together: 36 of 11,027 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

0% of pairs (38) had a long gap: more than 1.75 times the planned wait between them.

Buses arriving bunched
Time of day	Pairs checked	Bunched	Long gap
Morning rush (6 to 9 a.m.)	2,617	0% (3)	0% (3)
Midday (9 a.m. to 3 p.m.)	5,039	0% (16)	0% (10)
Afternoon rush (3 to 6 p.m.)	2,422	1% (17)	1% (25)
Evening (6 to 10 p.m.)	949	0% (0)	0% (0)

How this is measured →How we got this numberBunching and slow spots on every route →

Where this route is slowest

Slowest: QUAI LOCAL de la CITÉ #8 to HÔPITAL DE GATINEAU, 6.7 km/h actual against 17.3 km/h planned.

Where this route is slowest
From	To	Distance	Planned speed	Actual speed	Trips measured	Slow trips
QUAI LOCAL de la CITÉ #8	HÔPITAL DE GATINEAU	1.4 km	17.3 km/h	6.7 km/h	431	79%
Quai local LABROSSE #5	la VÉRENDRYE EST/MAIN	1.7 km	19.2 km/h	7.5 km/h	358	75%
HÔPITAL DE GATINEAU	la VÉRENDRYE OUEST/de la CITÉ	690 m	15.1 km/h	15.9 km/h	490	6%
HÔPITAL DE GATINEAU	QUAI LOCAL de la CITÉ arrivée	1.5 km	18.9 km/h	18.1 km/h	383	3%
de l'OASIS/de la CITÉ	HÔPITAL DE GATINEAU	590 m	16.9 km/h	20.1 km/h	411	3%
la VÉRENDRYE EST/MAIN	Terminus Labrosse	1.3 km	21.6 km/h	22.3 km/h	453	2%
la VÉRENDRYE EST/MAIN	de l'OASIS/de la CITÉ	2.8 km	28.8 km/h	28.7 km/h	407	4%
la VÉRENDRYE OUEST/de la CITÉ	la VÉRENDRYE EST/MAIN	3 km	32.7 km/h	31 km/h	480	3%

A slow trip took at least 1.5 times the planned time.

How this is measured →

Cancellations on this route

What these words mean →

6 partial-capture days not counted.

1 scheduled trips with counted cancellation notices from Thu, Oct 8 to Wed, Nov 4.

Not counted: 0 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.

Hours with the most cancellations: 10 a.m. (1)

Latest cancelled trips

Tue, Nov 3, scheduled 10:18

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: 7 of 326 trips we could check.

When this route is usually busy

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 35 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats1.1% of 449 trips	Usually seats0% of 37 trips	Usually seats0% of 31 trips
9 am to 3 pm	Usually seats1.8% of 774 trips	Usually seats0% of 96 trips	Usually seats0% of 88 trips
3 to 6 pm	Usually seats4.7% of 537 trips	Usually seats0% of 46 trips	Usually seats0% of 49 trips
6 to 10 pm	Usually seats0% of 334 trips	Usually seats0% of 62 trips	Usually seats0% of 54 trips
After 10 pm	Usually seats0% of 108 trips	Usually seats0% of 15 trips	Not enough readings

Based on 55 computed days.

Source: the occupancy status in STO’s public real-time vehicle feed, which STO sets from each bus’s load sensor (seats available under 60% full, standing room under 90%, full above 90%).
Each trip counts once per time of day, at the highest load it reported.
Reports of an empty bus are left out, because older records could not tell an empty bus from one with no sensor.
A time of day needs at least 12 trips on at least 4 different days before anything is shown. Holidays are counted with their day of the week.

Open the dated prediction analysis

Verdict

What this route needs

16:00 has 67% of predictions within five minutes of the timetable, against 93% the rest of the day.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 19 hours with samples

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: 99.3% of final predictions within five minutes of the timetable, 152 predictions, typically 0.2 min late
06:00: 95% of final predictions within five minutes of the timetable, 674 predictions, typically 1 min late
07:00: 92.5% of final predictions within five minutes of the timetable, 774 predictions, typically 1.5 min late
08:00: 92.7% of final predictions within five minutes of the timetable, 819 predictions, typically 1.3 min late
09:00: 88.6% of final predictions within five minutes of the timetable, 916 predictions, typically 1.4 min late
10:00: 92.3% of final predictions within five minutes of the timetable, 704 predictions, typically 1.8 min late
11:00: 91.8% of final predictions within five minutes of the timetable, 780 predictions, typically 1.4 min late
12:00: 93.8% of final predictions within five minutes of the timetable, 801 predictions, typically 0.9 min late
13:00: 88.2% of final predictions within five minutes of the timetable, 849 predictions, typically 1.9 min late
14:00: 89.3% of final predictions within five minutes of the timetable, 773 predictions, typically 1.8 min late
15:00: 76.5% of final predictions within five minutes of the timetable, 814 predictions, typically 2.2 min late
16:00: 66.9% of final predictions within five minutes of the timetable, 845 predictions, typically 2.9 min late
17:00: 86.7% of final predictions within five minutes of the timetable, 864 predictions, typically 2.3 min late
18:00: 88.9% of final predictions within five minutes of the timetable, 673 predictions, typically 1.3 min late
19:00: 95.7% of final predictions within five minutes of the timetable, 511 predictions, typically 1 min late
20:00: 96.4% of final predictions within five minutes of the timetable, 445 predictions, typically 0.9 min late
21:00: 94.3% of final predictions within five minutes of the timetable, 403 predictions, typically 0.7 min late
22:00: 96.4% of final predictions within five minutes of the timetable, 443 predictions, typically 0.5 min late
23:00: 99.4% of final predictions within five minutes of the timetable, 161 predictions, typically 0.6 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

Findings
What	When	Measured	Scenario or next investigation
ProblemOne hour has a lower prediction match	16:00	67%	Operations, not the timetable

Measurements

One hour has a lower prediction match · 16:00: Hour 16:00; On time 66.9%; Measured arrivals 845; Shortfall 25.6 pts; Route median on time 92.5%

Open history, reliability and route analysis

Route check

How route 76 has been running

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, but check the problem times below.

89 in 100 eligible predictions were within 5 minutes of the timetable · 23,476 predictions checked

Prediction sample size: Larger sample

Based on 23,476 eligible provider predictions over 22 measured days, from Oct 6, 2026 to Nov 3, 2026.

Updated Nov 5, 2026, 1:32 a.m.

Where and when did predictions differ repeatedly?

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.

4 p.m.–5 p.m.: 33 in 100 eligible predictions differed from the timetable by more than 5 minutes (845 predictions over 13 days).

No current official notice matches this route.

Prediction differences by stop

Quai local LABROSSE #5
59 in 100 eligible predictions differed from the timetable by more than 5 minutes (505 predictions over 24 days).
Open this stop
QUAI LOCAL de la CITÉ #8
54 in 100 eligible predictions differed from the timetable by more than 5 minutes (602 predictions over 24 days).
Open this stop

These 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.

Check every trip and date

Open a time period to see each service day, scheduled trip, feed gap, observed public vehicle ID, and the exact counts behind this summary.

What riders want to know

Is any trip cancelled right now?: 0 of 1Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 8 of 326 checked trips need a closer look8 of 326 trips with enough public-feed evidence had no matching position over 7 days. 88 of 414 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
How did provider predictions differ from the timetable?: At the 95th percentile, the predicted difference was 5.9 min (positive means later; negative means earlier)89 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
What wait did provider predictions imply?: No route-level result meets the evidence threshold yet. This does not mean gaps did not happen.

Schedule change check

Published schedule: before and after

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 November 3, 2026

Selected service day from each published schedule

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.

Before

Service date checked: November 2, 2026

Scheduled trips: 70
Distinct scheduled stops: 45
Distinct published paths: 2
Published service span: 5:38 a.m.–12:02 a.m. next day

Operator calendar-date records: 1 added · 0 removed

Feed fingerprint: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

New schedule

Service date checked: November 9, 2026

Scheduled trips: 70
Distinct scheduled stops: 45
Distinct published paths: 2
Published service span: 5:38 a.m.–12:02 a.m. next day

Operator calendar-date records: 1 added · 0 removed

Feed fingerprint: 64b436d79ab51a76 · 623ad8b0-ad29-4d70-b8e6-e594a396233e

Did service improve after the change?

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 12,141 arrivals over 13 days; after has 1,501 arrivals over 2 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.

How this route is judged: Regular all-stop route

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.

What this data cannot prove

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.

See the definitions, thresholds and evidence order

Official current feed: explicit cancellations, skipped stops and active notices.
Matched observations: vehicle positions and settled predictions tied to the official schedule.
Official timetable: what was planned, kept separate from what was observed.
Rider and operator reports: leads about routes, times and places to investigate, not numeric proof by themselves.

Provisional results, published evidence

How did predictions compare with the timetable?

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: October 6, 2026 to November 3, 2026

Within 5 minutes of schedule: 89.2%
Eligible predictions checked: 23,476
Weekdays with data: 17
95th-percentile predicted delay: 5.9 min late

Patterns by hour (19)

Patterns by hour (19)
Hour	On time	Median	95th percentile	Evidence
05:00	99.3%	0.2 min late	2.4 min late	152 · 8 days
06:00	95.0%	1 min late	3.1 min late	674 · 8 days
07:00	92.5%	1.5 min late	5.3 min late	774 · 10 days
08:00	92.7%	1.3 min late	5.5 min late	819 · 11 days
09:00	88.6%	1.4 min late	5.7 min late	916 · 12 days
10:00	92.3%	1.8 min late	5.4 min late	704 · 11 days
11:00	91.8%	1.4 min late	5.2 min late	780 · 13 days
12:00	93.8%	0.9 min late	4.7 min late	801 · 12 days
13:00	88.2%	1.9 min late	5.5 min late	849 · 12 days
14:00	89.3%	1.8 min late	5.7 min late	773 · 13 days
15:00	76.5%	2.2 min late	7.7 min late	814 · 12 days
16:00	66.9%	2.9 min late	12.3 min late	845 · 13 days
17:00	86.7%	2.3 min late	6 min late	864 · 12 days
18:00	88.9%	1.3 min late	6 min late	673 · 11 days
19:00	95.7%	1 min late	4.3 min late	511 · 10 days
20:00	96.4%	0.9 min late	3.3 min late	445 · 10 days
21:00	94.3%	0.7 min late	3.1 min late	403 · 10 days
22:00	96.4%	0.5 min late	2.4 min late	443 · 10 days
23:00	99.4%	0.6 min late	2.5 min late	161 · 8 days

1 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.

Scheduled bus, but not observed in realtime

318 / 414 scheduled trips published at least one position across 5 service days (76.8%).

21:006 / 14 trips without a position57.1%
22:006 / 14 trips without a position57.1%
06:0012 / 30 trips without a position60.0%
23:002 / 5 trips without a position60.0%
07:0013 / 34 trips without a position61.8%
19:007 / 19 trips without a position63.2%

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

Trips scheduled that day

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.

Service day

November 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

November 4, 2026 · 70 trips in the retained timetable · retained notices; capture coverage unverified

In short: 49 with a matched position · 2 with no matching position (to investigate) · 19 with an unknown outcome.

05:38– 05:56
Trip sto:63296800Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 5:52 a.m. EST; not actual start or end times.
06:08– 06:26
Trip sto:63296793Vehicle position matchedFirst / last feed position: 6:04 a.m. EST / 6:23 a.m. EST; not actual start or end times.
06:20– 06:37
Trip sto:63296765Vehicle position matchedFirst / last feed position: 6:16 a.m. EST / 6:36 a.m. EST; not actual start or end times.
06:30– 06:48
Trip sto:63296801Vehicle position matchedFirst / last feed position: 6:22 a.m. EST / 6:46 a.m. EST; not actual start or end times.
06:38– 06:55
Trip sto:63296769Vehicle position matchedFirst / last feed position: 6:26 a.m. EST / 6:52 a.m. EST; not actual start or end times.
06:48– 07:06
Trip sto:63296794Vehicle position matchedFirst / last feed position: 6:38 a.m. EST / 7:07 a.m. EST; not actual start or end times.
06:57– 07:14
Trip sto:63296766Vehicle position matchedFirst / last feed position: 6:47 a.m. EST / 7:15 a.m. EST; not actual start or end times.
07:07– 07:25
Trip sto:63296796Vehicle position matchedFirst / last feed position: 6:53 a.m. EST / 7:23 a.m. EST; not actual start or end times.
07:16– 07:37
Trip sto:63296767Vehicle position matchedFirst / last feed position: 7:08 a.m. EST / 7:35 a.m. EST; not actual start or end times.
07:31– 07:49
Trip sto:63296802Vehicle position matchedFirst / last feed position: 7:32 a.m. EST / 7:53 a.m. EST; not actual start or end times.
07:32– 07:53
Trip sto:63296768Vehicle position matchedFirst / last feed position: 7:31 a.m. EST / 7:52 a.m. EST; not actual start or end times.
07:53– 08:14
Trip sto:63296770Vehicle position matchedFirst / last feed position: 7:54 a.m. EST / 8:15 a.m. EST; not actual start or end times.

· Open all evidence for this day