Stop impacts: Blair Station stop I relocation (UPDATED): October 10 2025 - Updated on October 9, 2026 Until further notice, stop I at Blair Station will be temporarily closed. This closure is due to construction work being performed on the north bus platform, as part of the Blair Station Elevator Replacement Project. Impacts Service for routes 12, 15, 23, 24, 26, 39, N39, and 42 will be relocated two stops east to stop G during the work period. No pedestrian access to north bus platform from the west side of the station. Use the accessible walkway along north platform East. To assist customers with accessing the station, shuttle buses will operate 24/7 between Gloucester Centre Mall, stop B and stop H. During the hours of midnight and 6 am, the shuttle bus service will extend to Telesat Court. What else to expect Customers should expect a heavier presence of construction activity along the pedestrian walkway at the station. Starting March 2, 2026, part of the north bus platform and the lower level east doors will be closed for several months to allow work on the new elevator system. Customers will use the adjacent south doors to access stops F, G, and H using a temporary platform installed next to the existing platform. This will not affect the stop locations or service. Other minor impacts to platforms and walkways on certain workdays may occur. Construction crews and flaggers will guide customers as required. Affected stops Bus Stop (560#) not in use · Routes · Alternate Stop #3027 -- Blair I · · 12 Tunney's Pasture · 15 Parliament · 23 Rothwell Heights & Blair · 24 Chapel Hill · 26 Pineview · 39 Millennium · 39 Blair & N Rideau · 42 Hurdman · #3027 -- Blair G Stop relocation map

No 15 trips cancelled now · 0 did not run in NovemberCancellations →

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

STO route 15: Des Érables

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

Quai local de la GAPPE #6100 min sched.
de la GAPPE/CARMEN101 min sched.
de la GAPPE/OXFORD102 min sched.
SAINT-LOUIS/Av. GATINEAU106 min sched.
SAINT-LOUIS/de NANTEL107 min sched.
SAINT-LOUIS/de NANTEL107 min sched.
SAINT-LOUIS/CARTIER108 min sched.
SAINT-LOUIS/du PONT ALONZO-WRIGHT109 min sched.
SAINT-LOUIS/LEBAUDY110 min sched.
SAINT-LOUIS/LEBAUDY110 min sched.
des ÉRABLES/SAINT-ALEXANDRE111 min sched.
des ÉRABLES/SAINT-ALEXANDRE112 min sched.
des ÉRABLES/du SOMMELIER112 min sched.
ARRÊT DE COURTOISIE Érables/Tire113 min sched.
ARRÊT DE COURTOISIE Érables/Sucrerie114 min sched.
ARRÊT DE COURTOISIE Érables/Fleurimont115 min sched.
des ÉRABLES/TACHÉ116 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

—

No retained notice returned; this does not prove zero cancellations.

Trips needing investigation

0 of 7 trips with a usable feed window (0%) had no matching position.

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

7 with position · 0 to investigate · 3 excluded · 10 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 7 / 10 (70%). 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, 1:37 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

96.2%

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

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

The hours we have evidence for

1690% · 112 predictions · 7 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?

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

Too few buses were measured to judge bunching: 0 pairs checked, 30 needed.

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

Where this route is slowest

Not enough trips yet to measure speed between timepoints (20 trips needed for each segment).

Tsi ní:ioht →

Cancellations on this route

What these words mean →

6 partial-capture days not counted.

No counted cancellations on this route in the last four weeks. Notices we could not check would be listed below.

Did not come (no bus seen, no notice), last 7 days: none of the 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	Not enough readings	Not enough readings	Not enough readings
6 to 9 am	Usually seats0% of 27 trips	Not enough readings	Not enough readings
9 am to 3 pm	Not enough readings	Not enough readings	Not enough readings
3 to 6 pm	Usually seats0% of 28 trips	Not enough readings	Not enough readings
6 to 10 pm	Not enough readings	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 15 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.

96 in 100 eligible predictions were within 5 minutes of the timetable · 345 predictions checked

Prediction sample size: Moderate sample

Based on 345 eligible provider predictions over 16 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

We do not yet have enough route-by-stop history to name a recurring problem stop. Rider reports are used as leads, not proof.

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?: 0 of 7 checked trips need a closer look0 of 7 trips with enough public-feed evidence had no matching position over 7 days. 3 of 10 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 4.4 min (positive means later; negative means earlier)96 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: 2
Distinct scheduled stops: 33
Distinct published paths: 2
Kahiatónhsera: tsi niió:re ne kà:sere: 06:53–16:53

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 169 arrivals over 9 days; after has 34 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: 96.2%
Eligible predictions checked: 345
Weekdays with data: 16
95th-percentile predicted delay: 4.4 min late

Patterns by hour (3)

Patterns by hour (3)
Hour	Ioiánere tsi nikarì:wes	Median	95th percentile	Tsi tó:kenske
06:00	100.0%	1.9 min late	2.9 min late	24 · 4 days
07:00	100.0%	1.2 min late	2.7 min late	27 · 4 days
16:00	90.2%	1.7 min late	5.9 min late	112 · 7 days

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

Scheduled bus, but not observed in realtime

7 / 10 scheduled trips published at least one position across 5 service days (70.0%).

06:003 / 5 trips without a position40.0%
16:000 / 5 trips without a position100.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 · 2 trips in the retained timetable · retained notices; capture coverage unverified

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

06:53– 07:08
Trip sto:63295296Insufficient coverage or identity; outcome unknown
16:37– 16:53
Trip sto:63295280Vehicle position matchedFirst / last feed position: 4:34 p.m. EST / 4:53 p.m. EST; not actual start or end times.

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