No 68 trips cancelled now · 5 did not run in NovemberCancellations →

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

STO route 68: Cgp G-Roy/Station Lorrain

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

CEGEP GABRIELLE-ROY1 min sched.
du MONT-BLEU/de la CITÉ-DES-JEUNES1 min sched.
du MONT-BLEU/des GROSEILLIERS2 min sched.
du MONT-BLEU/des MAGNOLIAS3 min sched.
du MONT-BLEU/RIEL4 min sched.
du MONT-BLEU/PÈRE-BÉLAND5 min sched.
du MONT-BLEU/PHILIAS-FORTIN6 min sched.
du MONT-BLEU/ARDOUIN6 min sched.
SAINT-JOSEPH/du MONT-BLEU8 min sched.
SAINT-JOSEPH/JEAN-PROULX9 min sched.
SAINT-JOSEPH/JEAN-PROULX9 min sched.
JEAN-PROULX/NOËL10 min sched.
JEAN-PROULX/NOËL11 min sched.
JEAN-PROULX/BUTEAU12 min sched.
JEAN-PROULX/DEVEAULT12 min sched.
de la CARRIÈRE/ADRIEN-ROBERT13 min sched.
de la CARRIÈRE/d'EDMONTON13 min sched.
Station de la GAPPE #319 min sched.
Station PROMENADES #222 min sched.
Station de la CITÉ #325 min sched.
Station GOUIN #228 min sched.
Station LABROSSE #041 min sched.
Station Lac Beauchamp #24 min sched.
STATION LORRAIN arrêt d'arrivée6 min 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

6 of 270 trips with a usable feed window (2.2%) had no matching position.

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

264 with position · 6 to investigate · 40 excluded · 310 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 264 / 310 (85.2%). 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, 12:49 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.6%

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

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

The hours we have evidence for

0695% · 477 predictions · 7 days
0793% · 625 predictions · 6 days
0891% · 549 predictions · 7 days
0986% · 664 predictions · 8 days
1093% · 599 predictions · 8 days
1193% · 654 predictions · 9 days
1293% · 750 predictions · 9 days
1388% · 710 predictions · 9 days
1485% · 573 predictions · 10 days
1585% · 701 predictions · 9 days
1677% · 723 predictions · 10 days
1776% · 1,003 predictions · 9 days
1881% · 559 predictions · 8 days
1992% · 38 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 4, 2026

6 partial-capture days not counted.

What about time of day?

14 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

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

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

Buses arriving bunched
Tó: nikahwistá:ke	Pairs checked	Bunched	Long gap
Morning rush (6 to 9 a.m.)	2,452	2% (51)	2% (53)
Midday (9 a.m. to 3 p.m.)	5,328	0% (12)	1% (27)
Afternoon rush (3 to 6 p.m.)	3,256	1% (41)	1% (26)
Evening (6 to 10 p.m.)	888	0% (0)	0% (0)

Tsi ní:ioht →How we got this numberBunching and slow spots on every route →

Where this route is slowest

Slowest: CEGEP GABRIELLE-ROY to JEAN-PROULX/NOËL, 11.7 km/h actual against 18.9 km/h planned.

Where this route is slowest
Tsi nón:we	Tsi nón:we	Tsi niió:re (distance)	Planned speed	Actual speed	Trips measured	Slow trips
CEGEP GABRIELLE-ROY	JEAN-PROULX/NOËL	3.1 km	18.9 km/h	11.7 km/h	328	41%
STATION LORRAIN	Station LABROSSE #3	2.8 km	33.8 km/h	17.2 km/h	331	59%
Station de la CITÉ #1	Station PROMENADES #1	1.1 km	21.3 km/h	17.3 km/h	357	17%
Station PROMENADES #2	Station de la CITÉ #3	1.2 km	21.5 km/h	19.6 km/h	363	12%
JEAN-PROULX/NOËL	CEGEP GABRIELLE-ROY/arrivée	3 km	20 km/h	19.8 km/h	333	2%
Station de la GAPPE #1	JEAN-PROULX/NOËL	2 km	22.3 km/h	20.1 km/h	354	6%
JEAN-PROULX/NOËL	Station de la GAPPE #3	2.9 km	22 km/h	24.8 km/h	360	1%
Station de la CITÉ #3	Station GOUIN #2	1.8 km	34.4 km/h	28.9 km/h	358	13%

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

Tsi ní:ioht →

Cancellations on this route

What these words mean →

6 partial-capture days not counted.

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

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: 6 p.m. (1)

Latest cancelled trips

Tue, Nov 3, scheduled 18:10

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: 5 of 270 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	Wísk niwenhniserá:ke	Entákta	Awentatokentì:ke
Before 6 am	Usually seats0% of 40 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats17.5% of 543 trips	Not enough readings	Not enough readings
9 am to 3 pm	Usually seats10.6% of 887 trips	Not enough readings	Not enough readings
3 to 6 pm	Usually seats34.3% of 580 trips	Not enough readings	Not enough readings
6 to 10 pm	Usually seats3.6% of 140 trips	Not enough readings	Not enough readings
After 10 pm	Not enough readings	Not enough readings	Not enough readings

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

88 in 100 eligible predictions were within 5 minutes of the timetable · 17,263 predictions checked

Prediction sample size: Larger sample

Based on 17,263 eligible provider predictions over 17 measured days, from Oct 6, 2026 to Nov 3, 2026.

Updated Nov 4, 2026, 1: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

STATION LORRAIN
45 in 100 eligible predictions differed from the timetable by more than 5 minutes (406 predictions over 18 days).
Open this stop
CEGEP GABRIELLE-ROY
38 in 100 eligible predictions differed from the timetable by more than 5 minutes (407 predictions over 18 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 12Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 6 of 270 checked trips need a closer look6 of 270 trips with enough public-feed evidence had no matching position over 7 days. 40 of 310 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.3 min (positive means later; negative means earlier)88 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
What wait did provider predictions imply?: Average predicted extra wait was under 30 seconds at the sampled stop0.4 min beyond the scheduled wait, based on 273 eligible predictions at 18 high-frequency stops over 5 days.

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 ne first Monday after ne á:se schedule began, tánon ne Monday one week earlier. Akwé:kon figures, 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.

Ohén:ton

Wenhniserá:te wahatkáhtho: October 26, 2026

Schedule trips: 0
Distinct scheduled stops: 0
Distinct published paths: 0
Kahiatónhsera: tsi niió:re ne kà:sere: —–—

Kahiatónhsera: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

New schedule

Wenhniserá:te wahatkáhtho: November 2, 2026

Schedule trips: 62
Distinct scheduled stops: 45
Distinct published paths: 3
Kahiatónhsera: tsi niió:re ne kà:sere: 06:00–19:14

Operator calendar-date records: 1 added · 0 removed

Kahiatónhsera: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

Did service improve after the change?

Enkwatkáhtho' ne arrivals 14 wenhniserá:tens tsi niió:re aorí:wa ne change tánon' ohnà:ken. Ne tsi enkwatkáhtho' entewahró:ri' tsi nikarì:wes ne 7 wenhniserá:tens tánon' 200 arrivals iá:ken'.

Still collecting: before has 9,209 arrivals over 10 days; after has 1,593 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: 87.6%
Eligible predictions checked: 17,263
Weekdays with data: 17
95th-percentile predicted delay: 7.3 min late

Patterns by hour (14)

Patterns by hour (14)
Hour	Ioiánere tsi nikarì:wes	Median	95th percentile	Tsi tó:kenske
06:00	94.5%	0.8 min late	4.6 min late	477 · 7 days
07:00	93.4%	1.3 min late	5.6 min late	625 · 6 days
08:00	91.4%	0.7 min late	6.4 min late	549 · 7 days
09:00	86.3%	0.1 min late	7.3 min late	664 · 8 days
10:00	92.5%	0.6 min late	4.8 min late	599 · 8 days
11:00	93.0%	0.5 min late	4.8 min late	654 · 9 days
12:00	92.5%	0.9 min late	6.1 min late	750 · 9 days
13:00	87.9%	0.8 min late	6.7 min late	710 · 9 days
14:00	85.2%	0.6 min late	8.3 min late	573 · 10 days
15:00	84.7%	1.3 min late	9.3 min late	701 · 9 days
16:00	76.9%	2.9 min late	9.6 min late	723 · 10 days
17:00	76.4%	2.2 min late	7.8 min late	1,003 · 9 days
18:00	81.4%	1.7 min late	8.5 min late	559 · 8 days
19:00	92.1%	0.7 min late	5 min late	38 · 8 days

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

Scheduled bus, but not observed in realtime

264 / 310 scheduled trips published at least one position across 5 service days (85.2%).

07:0012 / 30 trips without a position60.0%
06:0012 / 35 trips without a position65.7%
18:004 / 15 trips without a position73.3%
08:005 / 25 trips without a position80.0%
15:003 / 20 trips without a position85.0%
17:003 / 30 trips without a position90.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 · 62 trips in the retained timetable · retained notices; capture coverage unverified

In short: 41 with a matched position · 4 with no matching position (to investigate) · 17 with an unknown outcome.

06:00– 06:34
Trip sto:63294799Insufficient coverage or identity; outcome unknown
06:00– 06:32
Trip sto:63295393Insufficient coverage or identity; outcome unknown
06:20– 06:52
Trip sto:63296348Insufficient coverage or identity; outcome unknown
06:30– 07:04
Trip sto:63295510Insufficient coverage or identity; outcome unknown
06:38– 07:10
Trip sto:63290319Insufficient coverage or identity; outcome unknown
06:57– 07:29
Trip sto:63295127Insufficient coverage or identity; outcome unknown
06:59– 07:33
Trip sto:63295402Insufficient coverage or identity; outcome unknown
07:03– 07:35
Trip sto:63296309Insufficient coverage or identity; outcome unknown
07:10– 07:42
Trip sto:63294960Insufficient coverage or identity; outcome unknown
07:16– 07:48
Trip sto:63295101Insufficient coverage or identity; outcome unknown
07:30– 08:04
Trip sto:63295883Insufficient coverage or identity; outcome unknown
07:38– 08:10
Trip sto:63295523Insufficient coverage or identity; outcome unknown

· Open all evidence for this day

Draft

This translation is a draft.

Help improve it

About 23% of this site is translated so far. The rest is shown in English.

Read this page in English

This page is a machine draft in Mohawk (Kanien’kéha), the language of the Kanien’kehá:ka (Mohawk) communities. It was prepared without review by its speakers, and is waiting for one. Speakers and the community are invited to correct it. We will replace it with their words. Ottawa is on the unceded territory of the Anishinabe Algonquin Nation.

Cette page est une ébauche automatique en mohawk (kanien’kéha), la langue des communautés kanien’kehá:ka (mohawks). Elle a été préparée sans révision par ses locuteurs, et attend l’un d’eux. Les locuteurs et la communauté sont invités à la corriger. Nous la remplacerons par leurs mots. Ottawa se trouve sur le territoire non cédé de la Nation algonquine anishinabe (Anishinabe Algonquin Nation).