DETOUR: Route 23 Rothwell and Blair near Blair and Massey: October 27 2026 - DETOUR: Route 23 Rothwell and Blair near Blair and Massey 23 Rothwell and Blair From Blair, right Swan's Way, Continue Voie Swans, right Wren, left Oxford, right Wick Crescent, left Rothwell, right Delong, left Rebecca, right again Rebecca, right Massey to regular routing. Stops Missed: BLAIR / SWANS - (1783), BLAIR / BRIARCLIFF - (8180), BLAIR / MASSEY - (8865), MASSEY / REBECCA - (8886) Alternate Stops: BLAIR / SWANS - (8848), DELONG / MASSEY - (8181)+2 more notice

No 23 trips cancelled now · 0 did not run in NobyembreCancellations →

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

Ruta 23: Rothwell Heights & Blair

Bawat 30 min

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Okt 27, 2026 – Nob 2, 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. Not counted: 1 trips with qualifying later matching vehicle observations. Trips with any notice: 2.

Trips needing investigation

0 of 40 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.

40 with position · 0 to investigate · 0 excluded · 40 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nob 3, 2026, 7:00 PM.

Coverage, exclusions and sources

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

Published position coverage: 40 / 40 (100%). 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: Nob 3, 2026, 5:49 PM

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

43%

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

Predictions in the source: 5,801
Weekdays with evidence: 18
Evidence window: Okt 5, 2026 – Nob 2, 2026

The hours we have evidence for

0771% · 841 predictions · 10 days
0823% · 392 predictions · 10 days
1561% · 491 predictions · 10 days
1633% · 834 predictions · 10 days
1712% · 495 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: Nob 3, 2026

2 partial-capture days not counted.

What about time of day?

5 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

Mga bus na dumarating nang magkakasabay

Last 28 days, Oktubre 6, 2026 to Nobyembre 2, 2026: 26 days counted.

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

Mga halaga at paliwanag

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

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

Mga bus na dumarating nang magkakasabay
Oras ng araw	Mga pares na sinuri	Nagkumpol	Mahabang pagitan
Rush hour sa umaga (6 hanggang 9 a.m.)	1,355	2% (26)	0% (0)
Rush hour sa hapon (3 hanggang 6 p.m.)	2,448	5% (129)	0% (0)

Paano ito sinusukat →How we got this numberMagkakadikit na bus at mabagal na bahagi sa bawat ruta →

Kung saan pinakamabagal ang rutang ito

Slowest: BLAIR G to BLAIR / MONTRÉAL, 17.6 km/h actual against 19.4 km/h planned.

Kung saan pinakamabagal ang rutang ito
Mula sa	Patungo sa	Layo	Planong bilis	Aktuwal na bilis	Mga biyaheng sinukat	Mabagal na biyahe
BLAIR G	BLAIR / MONTRÉAL	2.6 km	19.4 km/h	17.6 km/h	115	9%
ROTHWELL / DELONG	MONTRÉAL / BLAIR	1.9 km	23.7 km/h	20.6 km/h	121	19%
BLAIR / MONTRÉAL	ROTHWELL / DELONG	3.4 km	34 km/h	26.1 km/h	111	15%

Ang mabagal na biyahe ay inabot nang hindi bababa sa 1.5 beses ng planadong oras.

Paano ito sinusukat →

Gawaing-kalsada ng lungsod malapit sa rutang ito

Mga gawaing kalsada at pagsasara ng kalsada para sa event na inilathala ng City of Ottawa, na sinukat bilang malapit sa daanan ng rutang ito. Ang malapit ay hindi patunay na iniiba ang daan ng bus. Tingnan po ang sariling abiso ng tagapagpatakbo para doon.

Gawaing kalsada
Massey between Blair and Delong
Hun 29, 2026, 12:00 AM to Nob 6, 2026, 5:00 PM
Massey closed between Blair and Delong due to construction, from June 29th to November 6th. Access for local traffic maintained.
Minarkahan ito ng Lungsod na nakakaapekto sa transit.
about 0 m from the route
City record updated Set 4, 2026, 8:44 AM.

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.

Pinagmulan: mga traffic event ng City of Ottawa (road work at mga pagsasara ng daan). May impormasyong lisensyado sa ilalim ng Open Government Licence, City of Ottawa. Ayon sa Lungsod, pinagsikapan lamang ang listahang ito at maaaring hindi kumpleto. Mapa ng trapiko ng Lungsod ng Ottawa ↗

Mga pagkansela sa rutang ito

Ano ang ibig sabihin ng mga salitang ito →

2 partial-capture days not counted.

1 scheduled trips with counted cancellation notices from Mar, Okt 6 to Lun, Nob 2.

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

Mga oras na may pinakamaraming kanseladong biyahe: 7 AM (1)

Mga pinakabagong kinanselang biyahe

Mar, Okt 27, scheduled 07:34

Hindi nagbibigay ang OC Transpo ng dahilan para sa isang biyahe, kaya walang ipinapakita.

Hindi dumating (walang nakitang bus, walang abiso), huling 7 araw: wala sa mga biyaheng nasuri namin.

Buksan ang may petsang pagsusuri ng hula

Hatol

What this route needs

Median provider predictions are 5.1 to 5.4 min later than the timetable in 4 hours of the day.

Predictions near the start are about 4.9 min later than the timetable, with a similar difference near the end. This does not establish the cause.

Provider predictions are about 5.1 min earlier than the timetable, 17:00.

Wide prediction spread 17:00: the 95th percentile is 24.7 min later than the median.

17:00 has 12% of predictions within five minutes of the timetable, against 33% the rest of the day.

Matched public positions cover 100% of scheduled trips. This is a lower bound on operated service, not an audited delivery result.

Next investigation: test terminal recovery and the preceding trip against operational records. Predictions alone do not establish the cause.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 5 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: not enough data
06:00: not enough data
07:00: 70.6% of final predictions within five minutes of the timetable, 841 predictions, typically 3.6 min late
08:00: 22.7% of final predictions within five minutes of the timetable, 392 predictions, typically 6.7 min late
09:00: not enough data
10:00: not enough data
11:00: not enough data
12:00: not enough data
13:00: not enough data
14:00: not enough data
15:00: 60.9% of final predictions within five minutes of the timetable, 491 predictions, typically 4.1 min late
16:00: 32.7% of final predictions within five minutes of the timetable, 834 predictions, typically 6.8 min late
17:00: 11.9% of final predictions within five minutes of the timetable, 495 predictions, typically 5.1 min early. Provider predictions have a wide spread.
18:00: not enough data
19:00: not enough data
20:00: not enough data
21:00: not enough data
22:00: not enough data
23:00: not enough data

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
prediction spread of 20 min or more between the 95th percentile and median

Findings
What	Kailan	Nasukat	Scenario or next investigation
ProblemPredictions later than timetable	07:00 to 09:00 · 15:00 to 17:00	5.1 min late · 5.4 min late	Recovery time at the terminal
ProblemPredictions earlier than timetable	17:00	5.1 min early	Less running time, or holding points
ProblemWide prediction spread	17:00	24.7 min swing	Operations, not the timetable
ProblemOne hour has a lower prediction match	17:00	12%	Operations, not the timetable
StrengthObserved-position lower bound	All measured hours	100%	Keep what works

Measurements

Predictions later than timetable · 15:00 to 17:00: Measured arrivals 1,325; Hours affected 2; Spread 9.2 min; Median delay 5.4 min; Suggested running time change 5.4 min
Predictions later than timetable · 07:00 to 09:00: Measured arrivals 1,233; Hours affected 2; Spread 6 min; Median delay 5.1 min; Suggested running time change 5.1 min
Predictions earlier than timetable · 17:00: Measured arrivals 495; Hours affected 1; Spread 24.7 min; Median delay -5.1 min; Suggested running time change -5.1 min
Wide prediction spread · 17:00: Measured arrivals 495; Hours affected 1; Spread 24.7 min; Median delay -5.1 min; Suggested running time change -5.1 min
One hour has a lower prediction match · 17:00: Oras 17:00; Nasa oras 11.9%; Measured arrivals 495; Shortfall 20.8 pts; Route median on time 32.7%
Observed-position lower bound · All measured hours: Target 99.5%; Trips with a matching position 100%; Mga araw ng serbisyo 5; Trips with a matching position 40; Mga biyaheng nakatakda sa iskedyul 40

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

How route 23 has been running

Maikling buod ng alam namin. Sinasabi namin kapag hindi namin masagot ang isang tanong.

Pangunahing punto

Madalas na malayo sa iskedyul ang mga hula ng tagapagbigay sa sample na may petsang ito.

43 in 100 eligible predictions were within 5 minutes of the timetable · 5,801 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

Based on 5,801 eligible provider predictions over 18 measured days, from Okt 5, 2026 to Nob 2, 2026.

Updated Nob 3, 2026, 6:32 PM

Saan at kailan paulit-ulit na nagkaiba ang mga hula?

Ito ay mga paulit-ulit na pagkakaiba ng hula at ng iskedyul, hindi mga pagkabigo sa serbisyo na sinukat nang hiwalay. Ginagamit nito ang parehong karapat-dapat na mga hula gaya ng resulta sa itaas, pero pinagsasama-sama ayon sa hintuan, hindi ayon sa oras. Kaya maaaring hindi magkapareho ang mga listahan sa bawat linya.

17–18: 88 in 100 eligible predictions differed from the timetable by more than 5 minutes (495 predictions over 10 days).
08–09: 77 in 100 eligible predictions differed from the timetable by more than 5 minutes (392 predictions over 10 days).
16–17: 67 in 100 eligible predictions differed from the timetable by more than 5 minutes (834 predictions over 10 days).
15–16: 39 in 100 eligible predictions differed from the timetable by more than 5 minutes (491 predictions over 10 days).

2 current notices affect this route

• DETOUR: Route 23 Rothwell and Blair near Blair and Massey
• Stop impacts: Blair Station stop I relocation (UPDATED)

Pagkakaiba ng hula ayon sa hintuan

CITY PARK / OGILVIE
79 in 100 eligible predictions differed from the timetable by more than 5 minutes (149 predictions over 20 days).
Buksan ang hintuang ito
OGILVIE / CITY PARK
70 in 100 eligible predictions differed from the timetable by more than 5 minutes (148 predictions over 20 days).
Buksan ang hintuang ito
SWANS / WREN
70 in 100 eligible predictions differed from the timetable by more than 5 minutes (155 predictions over 20 days).
Buksan ang hintuang ito
SWANS / WHIPPOORWILL
70 in 100 eligible predictions differed from the timetable by more than 5 minutes (154 predictions over 20 days).
Buksan ang hintuang ito

Ito ay mga hula ng provider para sa partikular na ruta, na inihambing sa iskedyul. Ipinapakita nito ang paulit-ulit na pagkakaiba ng hula sa isang lugar at oras. Hindi ito nasukat na pagdating at hindi nito sinasabi ang dahilan.

Suriin ang bawat biyahe at petsa

Magbukas ng yugto ng panahon para makita ang bawat araw ng serbisyo, nakatakdang biyahe, puwang sa feed, naobserbahang pampublikong ID ng sasakyan, at ang eksaktong bilang sa likod ng buod na ito.

Ang gustong malaman ng mga pasahero

May kanseladong biyahe ba ngayon?: Walang biyaheng aalis sa susunod na 4 na orasSinusuri ang mga biyaheng magsisimula sa dulo ng ruta sa susunod na 4 na oras. Hindi ito makasaysayang bilang ng pagkansela.
Posibleng hindi sumipot matapos suriin ang mga puwang sa feed?: 0 of 40 checked trips need a closer look0 of 40 trips with enough public-feed evidence had no matching position over 7 days. 0 of 40 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
Paano naiba ang mga hula ng tagapagbigay ng serbisyo sa iskedyul?: At the 95th percentile, the predicted difference was 17.1 min (positive means later; negative means earlier)43 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
Gaano katagal na paghihintay ang ipinahiwatig ng mga tinatayang oras ng operator?: Wala pang resulta sa antas ng ruta na umaabot sa pamantayan ng evidence. Hindi po ibig sabihin nito na walang nangyaring puwang sa serbisyo.

Pagsusuri ng pagbabago sa iskedyul

Nailathalang iskedyul: bago at pagkatapos

Ikinukumpara po nito ang kasalukuyang opisyal na iskedyul na iniingatan sa naunang bersyon na iniingatan. Ang mga pagbabago sa iskedyul ay mga katotohanan tungkol sa kung ano ang binalak. Hindi po nito pinatutunayan na naganap ang isang biyahe.

Current published schedule began Oktubre 30, 2026

Piniling araw ng serbisyo mula sa bawat inilathalang iskedyul

Sinusuri po namin ang unang Lunes pagkatapos magsimula ang bagong iskedyul at ang Lunes isang linggo bago nito. Ang bawat bilang ay galing sa mga opisyal na bersyon ng GTFS na itinabi at nakasaad sa ibaba.

Hindi bababa sa isa sa mga napiling petsa ang may idinagdag o inalis na serbisyo sa petsa ng kalendaryo. Ituring po ito bilang konteksto ng holiday o espesyal na serbisyo, hindi karaniwang paglago tuwing karaniwang araw.

Bago

Petsa ng serbisyo na sinuri: Oktubre 26, 2026

Mga biyaheng nakatakda sa iskedyul: 8
Mga natatanging hintuan na nasa iskedyul: 45
Iba't ibang inilathalang daanan: 1
Inilathalang oras ng serbisyo: 07:04–17:50

Operator calendar-date records: 0 added · 2 removed

Fingerprint ng feed: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

Bagong iskedyul

Petsa ng serbisyo na sinuri: Nobyembre 2, 2026

Mga biyaheng nakatakda sa iskedyul: 8
Mga natatanging hintuan na nasa iskedyul: 45
Iba't ibang inilathalang daanan: 1
Inilathalang oras ng serbisyo: 07:04–17:50

Operator calendar-date records: 0 added · 2 removed

Fingerprint ng feed: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

Gumanda po ba ang serbisyo pagkatapos ng pagbabago?

Ihahambing po namin ang mga natapos na dating ng sasakyan sa loob ng 14 na araw bago at pagkatapos ng pagbabago. Ilalathala lamang po namin ang paghahambing kapag may hindi bababa sa 7 araw ng serbisyo at 200 dating ang magkabilang panig.

Still collecting: before has 3,149 arrivals over 10 days; after has 609 arrivals over 2 days. No improvement or decline is claimed yet.

Sa checksum, maaaring tiyakin ng sinuman kung aling iskedyul na itinabi ang pinagmulan ng mga bilang. Ang pagbabago sa bilang ay hindi nagpapakita ng dahilan, pagkansela, desisyon ng operator, o epekto sa mga pasahero.

Paano hinuhusgahan ang rutang ito: Regular na ruta na humihinto sa lahat ng hintuan

Inihahambing namin ang huling karapat-dapat na hula ng provider para sa bawat nakaiskedyul na pagdating sa opisyal na iskedyul. Hindi ito mga pagdating na sinukat nang hiwalay. Kailangan ng hindi bababa sa 200 karapat-dapat na hula para magkaroon ng resulta. Ang loob ng 5 minuto ang target para sa mga sakay na ginagamit dito.

Ang hindi mapatutunayan ng datos na ito

Ang public feed po ay hindi nagbibigay ng maaasahang bilang ng pasahero o ng mga pagkakataong nilampasan ang mga naghihintay na pasahero. Ang kawalan ng posisyon ay hindi nangangahulugang patunay ng pagkansela, hindi pagdating, maikling biyahe o sanhi nito.

Tingnan ang mga kahulugan, hangganan at pagkakasunod-sunod ng ebidensya

Opisyal na kasalukuyang feed: mga tahasang pagkansela, mga nilaktawang hintuan, at mga aktibong abiso.
Mga tugmang obserbasyon: mga posisyon ng sasakyan at mga pinal na prediksyon na iniugnay sa opisyal na iskedyul.
Opisyal na iskedyul: ang plano, hiwalay sa naobserbahan.
Mga ulat ng pasahero at operator: mga lead tungkol sa ruta, oras, at lugar na dapat imbestigahan. Hindi ito sapat na patunay na numerikal sa sarili nito.

Pansamantalang resulta, inilathalang ebidensya

Paano ikinumpara ang mga hula sa iskedyul?

Sa bawat oras, inihahambing ang huling karapat-dapat na predicted na dating mula sa provider para sa isang scheduled na pagdating sa timetable. Ang "Within 5 minutes" ay naglalarawan ng pagkakaiba ng prediksyon, hindi ng nasukat na pagdating o patunay na bumiyahe ang bus.

Saklaw ng ebidensya: Oktubre 5, 2026 to Nobyembre 2, 2026

Sa loob ng 5 minuto mula sa iskedyul: 43.0%
Mga karapat-dapat na hula na nasuri: 5,801
Mga araw ng linggo na may datos: 18
Tinatayang pagkaantala sa ika-95 na percentile: 17.1 min late

Patterns by hour (5)

Patterns by hour (5)
Oras	Nasa oras	Median	95th percentile	Ebidensya
07:00	70.6%	3.6 min late	10.2 min late	841 · 10 days
08:00	22.7%	6.7 min late	12 min late	392 · 10 days
15:00	60.9%	4.1 min late	17.3 min late	491 · 10 days
16:00	32.7%	6.8 min late	12 min late	834 · 10 days
17:00	11.9%	5.1 min early	19.5 min late	495 · 10 days

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

Nakaiskedyul na bus, ngunit hindi naobserbahan sa real-time

40 / 40 scheduled trips published at least one position across 5 service days (100.0%).

07:000 / 10 trips without a position100.0%
08:000 / 5 trips without a position100.0%
15:000 / 10 trips without a position100.0%
16:000 / 10 trips without a position100.0%
17:000 / 5 trips without a position100.0%

Hindi ito kumpirmadong hindi pagsipot. Ang nawawalang posisyon ay maaaring mangahulugang kinansela o nalagpasang bus, pero maaari rin itong mangahulugang walang nakatalagang ID ng biyahe o may puwang sa feed ng operator. Inilalathala ng Otranspo ang puwang dahil mahalaga ito sa mga sakay, habang nananatiling tapat ang konklusyon.

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. Mga pinagmulan at limitasyon.

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

November 2, 2026 · 8 trips in the retained timetable · retained notices; capture coverage unverified

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

07:04– 07:30
Trip 12953020Vehicle position matchedFirst / last feed position: 6:59 a.m. EST / 7:37 a.m. EST; not actual start or end times.
07:34– 08:00
Trip 30437020Vehicle position matchedFirst / last feed position: 7:38 a.m. EST / 7:59 a.m. EST; not actual start or end times.
08:04– 08:29
Trip 10043020Vehicle position matchedFirst / last feed position: 8:00 a.m. EST / 8:57 a.m. EST; not actual start or end times.
15:26– 15:52
Trip 5811020Vehicle position matchedFirst / last feed position: 3:21 p.m. EST / 4:11 p.m. EST; not actual start or end times.
15:56– 16:22
Trip 4665020Vehicle position matchedFirst / last feed position: 3:51 p.m. EST / 4:27 p.m. EST; not actual start or end times.
16:26– 16:52
Trip 34351020Vehicle position matchedFirst / last feed position: 4:28 p.m. EST / 5:02 p.m. EST; not actual start or end times.
16:56– 17:20
Trip 1739020Vehicle position matchedFirst / last feed position: 5:03 p.m. EST / 5:20 p.m. EST; not actual start or end times.
17:26– 17:50
Trip 54020Vehicle position matchedFirst / last feed position: 5:21 p.m. EST / 5:58 p.m. EST; not actual start or end times.