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

Previous measure: 79.9% of arrivals were within five minutes of the timetable (32,270 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 35: Lac Des Fées

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

des ALLUMETTIÈRES/LAURIER21 min sched.
MAISONNEUVE/VERDUN22 min sched.
MAISONNEUVE/SACRÉ-COEUR23 min sched.
KING EDWARD/ST-PATRICK29 min sched.
KING EDWARD/YORK0 min sched.
RIDEAU/CUMBERLAND1 min sched.
CENTRE RIDEAU3 min sched.
ALBERT/METCALFE5 min sched.
ALBERT/BANK6 min sched.
KENT / SPARKS7 min sched.
WELLINGTON/LYON8 min sched.
du PORTAGE/AUBRY15 min sched.
du PORTAGE/LAVAL16 min sched.
EDDY/WELLINGTON19 min sched.
MONTCALM/WRIGHT20 min sched.
MONTCALM/GAGNON21 min sched.
Station MONTCALM #322 min sched.
MONTCALM/LOIS23 min sched.
des ALLUMETTIÈRES/SAINT-JOSEPH24 min sched.
des ALLUMETTIÈRES/DEMONTIGNY25 min sched.
des ALLUMETTIÈRES/LABELLE25 min sched.
LABELLE/WìGWÀS26 min sched.
LABELLE/DUROCHER27 min sched.
LABELLE/DUMAS27 min sched.
LABELLE/NICOLET28 min sched.
LABELLE/FONTAINE28 min sched.
LABELLE/BOURQUE29 min sched.
GAMELIN/MOUSSETTE0 min sched.
LIONEL-ÉMOND/GAMELIN1 min sched.
CORBEIL/BRIGHAM2 min sched.
CORBEIL/FRÉCHETTE2 min sched.
CORBEIL/BRADY3 min sched.
THÉRIEN/BÉDARD4 min sched.
THÉRIEN/d'ORSONNENS5 min sched.
de la CITÉ-DES-JEUNES/THÉRIEN5 min sched.
de la CITÉ-DES-JEUNES/PERRAS6 min sched.
de la CITÉ-DES-JEUNES/PERRAS7 min sched.
CEGEP GABRIELLE-ROY8 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: 6.

Trips needing investigation

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

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

278 with position · 6 to investigate · 51 excluded · 335 scheduled trips

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

Coverage, exclusions and sources

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

Published position coverage: 278 / 335 (83%). 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:48 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

79.9%

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

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

The hours we have evidence for

05100% · 188 predictions · 7 days
0699% · 658 predictions · 7 days
0787% · 927 predictions · 6 days
0890% · 1,076 predictions · 7 days
0983% · 1,170 predictions · 8 days
1086% · 872 predictions · 8 days
1193% · 1,042 predictions · 9 days
1292% · 1,061 predictions · 9 days
1394% · 1,005 predictions · 9 days
1486% · 957 predictions · 10 days
1560% · 1,037 predictions · 9 days
1658% · 1,229 predictions · 10 days
1776% · 1,237 predictions · 9 days
1871% · 1,085 predictions · 8 days
1979% · 882 predictions · 8 days
2090% · 595 predictions · 8 days
2193% · 632 predictions · 8 days
2292% · 658 predictions · 8 days
2387% · 191 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?

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

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

0% of pairs (32) 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.)	3,391	1% (23)	0% (1)
Midday (9 a.m. to 3 p.m.)	7,533	0% (2)	0% (4)
Afternoon rush (3 to 6 p.m.)	3,681	2% (69)	1% (27)
Evening (6 to 10 p.m.)	2,607	0% (1)	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 de la CITÉ-DES-JEUNES/PERRAS, 2.9 km/h actual against 9.4 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	de la CITÉ-DES-JEUNES/PERRAS	310 m	9.4 km/h	2.9 km/h	281	68%
CENTRE RIDEAU	du PORTAGE/AUBRY	2.4 km	11.5 km/h	9.6 km/h	404	9%
du PORTAGE/AUBRY	EDDY/WELLINGTON	450 m	7.3 km/h	9.9 km/h	419	2%
TERRASSES de la CHAUDIÈRE	de l'HÔTEL-de-VILLE/LAURIER	750 m	12 km/h	10.9 km/h	286	12%
Station MONTCALM #3	des ALLUMETTIÈRES/SAINT-JOSEPH	480 m	12.4 km/h	11 km/h	422	14%
MONTCALM/HANSON	de l'HÔTEL-de-VILLE/LAURIER	1.6 km	11.4 km/h	11.8 km/h	75	0%
CEGEP GABRIELLE-ROY	de la CITÉ-DES-JEUNES/TALBOT	430 m	12.9 km/h	12.5 km/h	104	13%
de l'HÔTEL-de-VILLE/LAURIER	MUSÉE DE L'HISTOIRE	400 m	13.8 km/h	13.5 km/h	352	13%

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

Tsi ní:ioht →

City road work, kí:ken route

Road work tánon event road closures, City of Ottawa published. Measured near ne route. Near iah proof tsi bus detoured. Check ne operator alerts.

The City’s road work list could not be read right now.

A route counts as near when its timetable path passes within 40 m of the City’s mapped closure; a stop counts when it is within 75 m.

Source: City of Ottawa traffic events (road work and closures). Contains information licensed under the Open Government Licence, City of Ottawa. The City says this list is best effort and may be incomplete. City of Ottawa traffic map ↗

Cancellations on this route

What these words mean →

6 partial-capture days not counted.

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

Latest cancelled trips

Tue, Nov 3, scheduled 16:40
Mon, Nov 2, scheduled 07:19
Fri, Oct 30, scheduled 15:47
Fri, Oct 30, scheduled 15:10
Fri, Oct 30, scheduled 14: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: 4 of 284 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 29 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats5.9% of 546 trips	Not enough readings	Not enough readings
9 am to 3 pm	Usually seats3% of 767 trips	Not enough readings	Not enough readings
3 to 6 pm	Usually seats7.3% of 531 trips	Not enough readings	Not enough readings
6 to 10 pm	Usually seats2.3% of 426 trips	Not enough readings	Not enough readings
After 10 pm	Usually seats2.4% of 82 trips	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 the dated prediction analysis

Ka' nikarihò:ten

What this route needs

Median provider predictions are 3.1 to 3.7 min later than the timetable in 3 hours of the day.

Predictions near the start are about 4.7 min later than the timetable; the difference grows by another 3 min along the route.

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

Scenario: 3 to 4 min more running time on 52 trips. The schedule-block model estimates 20 additional 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.

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: 100% of final predictions within five minutes of the timetable, 188 predictions, typically 1.4 min late
06:00: 98.5% of final predictions within five minutes of the timetable, 658 predictions, typically 0.5 min late
07:00: 87.3% of final predictions within five minutes of the timetable, 927 predictions, typically 0.7 min late
08:00: 89.5% of final predictions within five minutes of the timetable, 1,076 predictions, typically 1.4 min late
09:00: 83.2% of final predictions within five minutes of the timetable, 1,170 predictions, typically 1.5 min late
10:00: 85.9% of final predictions within five minutes of the timetable, 872 predictions, typically 0.8 min late
11:00: 93% of final predictions within five minutes of the timetable, 1,042 predictions, typically 1.1 min late
12:00: 91.8% of final predictions within five minutes of the timetable, 1,061 predictions, typically 1.3 min late
13:00: 94.3% of final predictions within five minutes of the timetable, 1,005 predictions, typically 1.1 min late
14:00: 85.9% of final predictions within five minutes of the timetable, 957 predictions, typically 1 min late
15:00: 59.5% of final predictions within five minutes of the timetable, 1,037 predictions, typically 3.7 min late
16:00: 57.8% of final predictions within five minutes of the timetable, 1,229 predictions, typically 3.7 min late
17:00: 76.2% of final predictions within five minutes of the timetable, 1,237 predictions, typically 2.4 min late
18:00: 70.9% of final predictions within five minutes of the timetable, 1,085 predictions, typically 3.1 min late
19:00: 79% of final predictions within five minutes of the timetable, 882 predictions, typically 2.3 min late
20:00: 90.4% of final predictions within five minutes of the timetable, 595 predictions, typically 0.9 min late
21:00: 93.4% of final predictions within five minutes of the timetable, 632 predictions, typically 1 min late
22:00: 91.6% of final predictions within five minutes of the timetable, 658 predictions, typically 0.8 min late
23:00: 87.4% of final predictions within five minutes of the timetable, 191 predictions, typically 0.2 min early

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	Ó:nen	Tewaterièn:tare	Scenario or next investigation
ProblemPredictions later than timetable	15:00 to 17:00 · 18:00	3.7 min late · 3.1 min late	More running time
ProblemOne hour has a lower prediction match	16:00	58%	Operations, not the timetable

Measurements

Predictions later than timetable · 15:00 to 17:00: Measured arrivals 2,266; Hours affected 2; Spread 16.6 min; Median delay 3.7 min; Suggested running time change 3.7 min
Predictions later than timetable · 18:00: Measured arrivals 1,085; Hours affected 1; Spread 5.8 min; Median delay 3.1 min; Suggested running time change 3.1 min
One hour has a lower prediction match · 16:00: Hour 16:00; Ioiánere tsi nikarì:wes 57.8%; Measured arrivals 1,229; Shortfall 29.6 pts; Route median on time 87.4%

Open history, reliability and route analysis

Route check

How route 35 has been running

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.

80 in 100 eligible predictions were within 5 minutes of the timetable · 32,270 predictions checked

Prediction sample size: Larger sample

Based on 32,270 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.

16–17: 42 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,229 predictions over 10 days).
15–16: 41 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,037 predictions over 9 days).

No current official notice matches this route.

Prediction differences by stop

CEGEP GABRIELLE-ROY
45 in 100 eligible predictions differed from the timetable by more than 5 minutes (414 predictions over 18 days).
Open this stop
du PORTAGE/AUBRY
39 in 100 eligible predictions differed from the timetable by more than 5 minutes (506 predictions over 18 days).
Open this stop
de la GALÈNE/du MICA
38 in 100 eligible predictions differed from the timetable by more than 5 minutes (113 predictions over 18 days).
Open this stop
de la GALÈNE/des MINEURS
37 in 100 eligible predictions differed from the timetable by more than 5 minutes (113 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?: No live cancellation answerSTO’s live trip-update feed did not answer this check. That is a feed gap. It does not mean zero cancellations, and it is not proof of a cancellation. Open the evidence to see the schedule, retained explicit cancellation notices, and every labelled data gap.
Possible no-shows after checking feed gaps?: 6 of 284 checked trips need a closer look6 of 284 trips with enough public-feed evidence had no matching position over 7 days. 51 of 335 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 10.4 min (positive means later; negative means earlier)80 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 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: 67
Distinct scheduled stops: 96
Distinct published paths: 6
Kahiatónhsera: tsi niió:re ne kà:sere: 05:35–23:26

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 17,551 arrivals over 10 days; after has 2,866 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: 79.9%
Eligible predictions checked: 32,270
Weekdays with data: 17
95th-percentile predicted delay: 10.4 min late

Patterns by hour (19)

Patterns by hour (19)
Hour	Ioiánere tsi nikarì:wes	Median	95th percentile	Tsi tó:kenske
05:00	100.0%	1.4 min late	2.8 min late	188 · 7 days
06:00	98.5%	0.5 min late	4.1 min late	658 · 7 days
07:00	87.3%	0.7 min late	6.6 min late	927 · 6 days
08:00	89.5%	1.4 min late	6.8 min late	1,076 · 7 days
09:00	83.2%	1.5 min late	7.9 min late	1,170 · 8 days
10:00	85.9%	0.8 min late	8.9 min late	872 · 8 days
11:00	93.0%	1.1 min late	5.3 min late	1,042 · 9 days
12:00	91.8%	1.3 min late	5.5 min late	1,061 · 9 days
13:00	94.3%	1.1 min late	5.2 min late	1,005 · 9 days
14:00	85.9%	1 min late	9.9 min late	957 · 10 days
15:00	59.5%	3.7 min late	18.2 min late	1,037 · 9 days
16:00	57.8%	3.7 min late	22.5 min late	1,229 · 10 days
17:00	76.2%	2.4 min late	16.7 min late	1,237 · 9 days
18:00	70.9%	3.1 min late	8.9 min late	1,085 · 8 days
19:00	79.0%	2.3 min late	10.7 min late	882 · 8 days
20:00	90.4%	0.9 min late	8.3 min late	595 · 8 days
21:00	93.4%	1 min late	5.3 min late	632 · 8 days
22:00	91.6%	0.8 min late	5.8 min late	658 · 8 days
23:00	87.4%	0.2 min early	5.8 min late	191 · 8 days

2 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

278 / 335 scheduled trips published at least one position across 5 service days (83.0%).

07:0012 / 30 trips without a position60.0%
06:008 / 25 trips without a position68.0%
15:008 / 25 trips without a position68.0%
05:001 / 5 trips without a position80.0%
16:005 / 25 trips without a position80.0%
18:003 / 15 trips without a position80.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 · 67 trips in the retained timetable · retained notices; capture coverage unverified

In short: 50 with a matched position · 1 with no matching position (to investigate) · 16 with an unknown outcome.

05:35– 06:05
Trip sto:63295682Insufficient coverage or identity; outcome unknown
06:06– 06:54
Trip sto:63295690Insufficient coverage or identity; outcome unknown
06:15– 06:44
Trip sto:63290308Insufficient coverage or identity; outcome unknown
06:35– 07:07
Trip sto:63296415Insufficient coverage or identity; outcome unknown
06:44– 07:30
Trip sto:63296416Insufficient coverage or identity; outcome unknown
06:45– 07:32
Trip sto:63290309Insufficient coverage or identity; outcome unknown
07:08– 07:55
Trip sto:63295002Insufficient coverage or identity; outcome unknown
07:10– 07:45
Trip sto:63295500Insufficient coverage or identity; outcome unknown
07:19– 08:05
Trip sto:63295730Insufficient coverage or identity; outcome unknown
07:31– 08:18
Trip sto:63295747Insufficient coverage or identity; outcome unknown
07:46– 08:33
Trip sto:63295374Insufficient coverage or identity; outcome unknown
07:50– 08:25
Trip sto:63294582Insufficient 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).