No 800 trips cancelled now · 4 did not run in NovemberCancellations →

Previous measure: 87% of arrivals were within five minutes of the timetable (59,912 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 800: Rapibus 800

Toward Lorrain1 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 28, 2026 – Nov 3, 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

4 of 368 trips with a usable feed window (1.1%) had no matching position.

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

364 with position · 4 to investigate · 55 excluded · 423 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 4, 2026, 11:02 p.m..

Coverage, exclusions and sources

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

Published position coverage: 364 / 423 (86.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: Nov 4, 2026, 10:08 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.

What does the evidence show?

Predictions against the timetable

87%

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

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

The hours we have evidence for

5 a.m.98% · 187 predictions · 10 days
6 a.m.96% · 1,222 predictions · 10 days
7 a.m.93% · 1,443 predictions · 9 days
8 a.m.86% · 1,579 predictions · 10 days
9 a.m.95% · 1,926 predictions · 11 days
10 a.m.92% · 1,837 predictions · 11 days
11 a.m.93% · 1,926 predictions · 12 days
12 p.m.94% · 2,029 predictions · 12 days
1 p.m.94% · 1,919 predictions · 12 days
2 p.m.89% · 1,706 predictions · 13 days
3 p.m.74% · 1,987 predictions · 12 days
4 p.m.74% · 1,975 predictions · 13 days
5 p.m.85% · 1,869 predictions · 12 days
6 p.m.85% · 1,983 predictions · 11 days
7 p.m.80% · 1,838 predictions · 11 days
8 p.m.83% · 1,854 predictions · 10 days
9 p.m.87% · 1,753 predictions · 10 days
10 p.m.92% · 1,660 predictions · 10 days
11 p.m.99% · 364 predictions · 10 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 7, 2026 to November 3, 2026: 21 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: 67 of 32,683 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

0% of pairs (114) 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.)	3,699	0% (5)	0% (12)
Midday (9 a.m. to 3 p.m.)	13,090	0% (8)	0% (7)
Afternoon rush (3 to 6 p.m.)	5,393	1% (48)	2% (87)
Evening (6 to 10 p.m.)	8,633	0% (6)	0% (7)
Night (10 p.m. to 4 a.m.)	1,868	0% (0)	0% (1)

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

Where this route is slowest

Slowest: PARC-O-BUS ALLUMETTIÈRES to FRONT/CATHCART, 9 km/h actual against 22.5 km/h planned.

Where this route is slowest
From	To	Distance	Planned speed	Actual speed	Trips measured	Slow trips
PARC-O-BUS ALLUMETTIÈRES	FRONT/CATHCART	2.6 km	22.5 km/h	9 km/h	433	82%
PARC-O-BUS RIVERMEAD	chemin d'AYLMER/MORLEY-WALTERS	790 m	15.5 km/h	14.8 km/h	496	8%
STATION LORRAIN	Station LABROSSE #3	2.8 km	42.3 km/h	16.7 km/h	466	68%
Station de la CITÉ #2	Station PROMENADES #1	1.1 km	17.4 km/h	17 km/h	494	3%
TACHÉ-UQO #1	ALEXANDRE-TACHÉ/CHÂTEAUBRIAND	560 m	14.8 km/h	17.2 km/h	506	4%
chemin d'AYLMER/GRIMES	PRINCIPALE/du BORDEAUX	1.4 km	14.4 km/h	17.8 km/h	490	1%
FRONT/CATHCART	chemin d'AYLMER/du BORDEAUX	1.6 km	18.7 km/h	19.4 km/h	490	2%
FRONT/HARVEY	PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée	2.4 km	17.5 km/h	19.5 km/h	451	0%

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.

3 scheduled trips with counted cancellation notices from Wed, Oct 7 to Tue, Nov 3.

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

Hours with the most cancellations: 1 p.m. (2), 5 a.m. (1)

Latest cancelled trips

Mon, Nov 2, scheduled 13:32
Mon, Oct 19, scheduled 13:45
Mon, Oct 19, scheduled 05:45

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 368 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 60 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats28% of 517 trips	Usually seats7.8% of 51 trips	Usually seats2.1% of 47 trips
9 am to 3 pm	Usually seats6.2% of 988 trips	Usually seats17.8% of 107 trips	Usually seats5.2% of 97 trips
3 to 6 pm	Usually seats47.2% of 564 trips	Usually seats19% of 63 trips	Usually seats21.9% of 64 trips
6 to 10 pm	Usually seats8.6% of 652 trips	Usually seats9% of 78 trips	Usually seats2.7% of 74 trips
After 10 pm	Usually seats1.5% of 201 trips	Usually seats0% of 29 trips	Usually seats0% of 26 trips

Based on 56 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 history, reliability and route analysis

Route check

How route 800 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 in this dated sample.

87 in 100 eligible predictions were within 5 minutes of the timetable · 59,912 predictions checked

Prediction sample size: Larger sample

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

Updated Nov 4, 2026, 10:32 p.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.

No repeated prediction-difference period has cleared the evidence threshold yet.

No current official notice matches this route.

Prediction differences by stop

PARC-O-BUS ALLUMETTIÈRES
69 in 100 eligible predictions differed from the timetable by more than 5 minutes (576 predictions over 24 days).
Open this stop
STATION LORRAIN
43 in 100 eligible predictions differed from the timetable by more than 5 minutes (565 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?: No trips start in the next 4 hoursChecks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 4 of 368 checked trips need a closer look4 of 368 trips with enough public-feed evidence had no matching position over 7 days. 55 of 423 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 7.1 min (positive means later; negative means earlier)87 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 2, 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: October 26, 2026

Scheduled trips: 0
Distinct scheduled stops: 0
Distinct published paths: 0
Published service span: —–—

Feed fingerprint: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

New schedule

Service date checked: November 2, 2026

Scheduled trips: 71
Distinct scheduled stops: 110
Distinct published paths: 3
Published service span: 5:42 a.m.–11:25 p.m.

Operator calendar-date records: 1 added · 0 removed

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

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 33,034 arrivals over 13 days; after has 4,480 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: Rapibus rapid transit

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: 87.0%
Eligible predictions checked: 59,912
Weekdays with data: 17
95th-percentile predicted delay: 7.1 min late

Patterns by hour (19)

Patterns by hour (19)
Hour	On time	Median	95th percentile	Evidence
05:00	97.9%	1.6 min late	2.6 min late	187 · 10 days
06:00	96.2%	0.4 min late	3.9 min late	1,222 · 10 days
07:00	93.2%	1.1 min late	5.4 min late	1,443 · 9 days
08:00	85.6%	1.5 min late	9.1 min late	1,579 · 10 days
09:00	95.3%	0.8 min late	4.8 min late	1,926 · 11 days
10:00	91.9%	0.9 min late	5.7 min late	1,837 · 11 days
11:00	92.9%	1.4 min late	5.2 min late	1,926 · 12 days
12:00	93.5%	1.5 min late	5.1 min late	2,029 · 12 days
13:00	94.2%	1.3 min late	5.1 min late	1,919 · 12 days
14:00	88.5%	1.5 min late	7.5 min late	1,706 · 13 days
15:00	73.6%	2.6 min late	10.3 min late	1,987 · 12 days
16:00	73.5%	2.2 min late	11.3 min late	1,975 · 13 days
17:00	84.5%	1.4 min late	10.5 min late	1,869 · 12 days
18:00	85.3%	2.2 min late	7.1 min late	1,983 · 11 days
19:00	80.0%	2.3 min late	6.7 min late	1,838 · 11 days
20:00	83.0%	1.9 min late	7.1 min late	1,854 · 10 days
21:00	87.3%	1.7 min late	6.9 min late	1,753 · 10 days
22:00	91.6%	1.4 min late	5.5 min late	1,660 · 10 days
23:00	98.9%	0.6 min late	4.5 min late	364 · 10 days

No repeated pattern below 70% is yet established across at least three service days.

Scheduled bus, but not observed in realtime

364 / 423 scheduled trips published at least one position across 7 service days (86.1%).

06:009 / 27 trips without a position66.7%
22:005 / 17 trips without a position70.6%
20:007 / 24 trips without a position70.8%
07:006 / 24 trips without a position75.0%
19:006 / 24 trips without a position75.0%
21:006 / 24 trips without a position75.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

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 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

November 3, 2026 · 71 trips in the retained timetable · retained notices; capture coverage unverified

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

05:42– 06:41
Trip sto:63296892Insufficient coverage or identity; outcome unknown
05:45– 06:49
Trip sto:63296875Insufficient coverage or identity; outcome unknown
06:12– 07:15
Trip sto:63296860Insufficient coverage or identity; outcome unknown
06:13– 07:17
Trip sto:63296862Insufficient coverage or identity; outcome unknown
06:42– 07:46
Trip sto:63296841Insufficient coverage or identity; outcome unknown
06:43– 07:56
Trip sto:63296876Insufficient coverage or identity; outcome unknown
06:57– 08:01
Trip sto:63296838Insufficient coverage or identity; outcome unknown
07:11– 08:23
Trip sto:63296845Insufficient coverage or identity; outcome unknown
07:12– 08:17
Trip sto:63296886Insufficient coverage or identity; outcome unknown
07:42– 08:47
Trip sto:63296863Insufficient coverage or identity; outcome unknown
07:47– 08:53
Trip sto:63296842Insufficient coverage or identity; outcome unknown
08:02– 09:04
Trip sto:63296835Insufficient coverage or identity; outcome unknown

· Open all evidence for this day