Detour: Routes 57, 61, 62, 63, 74, 75, 87 during nightly Kichi Zībī Mīkan closures: May 07 2026 - Until further notice, routes 57, 61, 62, 63, 74, 75, and 87 will detour on weeknights and weekends between 11:30 pm and 6 am in both directions around the Kichi Zībī Mīkan parkway, between Lincoln Fields station and Churchill Avenue. Please allow extra time for your travels. Affected stops Bus Stop (560#) not in use · Routes · Alternate Stop #3013 -- Dominion 2A · · 57 Tunney's Pasture · 61 Tunney's Pasture · 62 Tunney's Pasture · 63 Tunney's Pasture · 74 Tunney's Pasture · 75 Tunney's Pasture & N Rideau · 87 Tunney's Pasture · #4941 -- Richmond (south side) / Golden #3013 -- Dominion 1A · · 57 Crystal Bay · 61 Stittsville · 62 Stittsville · 63 Innovation · 74 Nepean Woods · 75 Barrhaven · #4922 -- Richmond (north side) / Golden #3014 -- Lincoln Fields 1A · · 61 Stittsville · 62 Stittsville · 63 Innovation · 74 Nepean Woods · 75 Barrhaven · 87 Baseline · #3014 -- Lincoln Fields 3B OR #3014 -- Lincoln Fields 5A #4944 -- Woodroffe (west side) / Saunders* · · 87 Baseline · #6244 -- Woodroffe (west side) / Knightsbridge #1832 -- Woodroffe (west side) / Richmond* · · 87 Baseline · #6244 -- Woodroffe (west side) / Knightsbridge #4942 -- Woodroffe (east side) / Saunders* · · 87 Tunney's Pasture · #6472 -- Woodroffe (east side) / Knightsbridge #2783 -- Woodroffe (east side) / Richmond* · · 87 Tunney's Pasture · #6472 -- Woodroffe (east side) / Knightsbridge *These stops are already not in use due to the closure of Woodroffe Avenue (Byron/Richmond to Kichi Zībī Mīkan) Detour routing 57 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 57 Bayshore: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe, right onto Carling, left onto J-Ramp, continue regular routing. 61 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 61 Stittsville / Terry Fox: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 62 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 62 Stittsville: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 63 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 63 Innovation/ Briarbrook: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 74 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 74 Limebank: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 75 Tunney's Pasture & N Rideau: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 75 Barrhaven Centre / Cambrian: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 87 Baseline: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe, right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 87 Tunney's Pasture: From Woodroffe and Byron, turn right onto Byron, continue on Richmond, left onto Churchill, right onto Scott to regular route. Detour Map+2 more notice

No 74 trips cancelled now · 3 did not run in NobyembreCancellations →

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

Ruta 74: Limebank ⇄ Tunney's Pasture

Bawat 15 hanggang 30 min

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

TUNNEY'S PASTURE F24 min sched.
WESTBORO A29 min sched.
DOMINION 1A30 min sched.
LINCOLN FIELDS 1B36 min sched.
QUEENSWAY 1A38 min sched.
IRIS 1A39 min sched.
BASELINE 1D43 min sched.
WOODROFFE / DAVID44 min sched.
WOODROFFE / TALLWOOD44 min sched.
WOODROFFE / NORICE45 min sched.
WOODROFFE / KNOXDALE46 min sched.
WOODROFFE / MAJESTIC46 min sched.
WOODROFFE / WEST HUNT CLUB46 min sched.
WOODROFFE / NEPEAN SPORTSPLEX47 min sched.
FALLOWFIELD A9 min sched.
FALLOWFIELD / FALLOWFIELD STATION12 min
WOODROFFE / FALLOWFIELD13 min
WOODROFFE / EARL MULLIGAN13 min
WOODROFFE / LONGFIELDS14 min
WOODROFFE / LONGFIELDS14 min
WOODROFFE / CLARIDGE15 min
WOODROFFE / QUEENSBURY16 min
WOODROFFE / DEER FOX17 min
WOODROFFE / HERITAGE GLEN17 min
WOODROFFE / STRANDHERD18 min
NEPEAN WOODS A19 min
STRANDHERD / CRESTHAVEN20 min
STRANDHERD / PRINCE OF WALES22 min
RIVERVIEW A24 min
EARL ARMSTRONG / RIVERVIEW P&R26 min
EARL ARMSTRONG / SPRATT26 min
EARL ARMSTRONG / RALPH HENNESSY27 min
EARL ARMSTRONG / SANDY FOREST PATHWAY28 min
EARL ARMSTRONG / PORTICO28 min
EARL ARMSTRONG / EYE BRIGHT PATHWAY28 min
LIMEBANK C27 min sched.

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Okt 29, 2026 – Nob 4, 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: 11 trips with qualifying later matching vehicle observations. Trips with any notice: 14.

Trips needing investigation

5 of 712 trips with a usable feed window (0.7%) had no matching position.

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

707 with position · 5 to investigate · 0 excluded · 712 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nob 5, 2026, 5:40 AM.

Coverage, exclusions and sources

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

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

Published position coverage: 707 / 712 (99.3%). 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 5, 2026, 4:19 AM

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

83.1%

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

Predictions in the source: 83,010
Weekdays with evidence: 19
Evidence window: Okt 6, 2026 – Nob 3, 2026

The hours we have evidence for

00100% · 463 predictions · 14 days
0595% · 297 predictions · 11 days
0694% · 1,664 predictions · 13 days
0792% · 2,629 predictions · 15 days
0891% · 2,962 predictions · 15 days
0980% · 3,349 predictions · 15 days
1087% · 3,469 predictions · 15 days
1189% · 3,491 predictions · 15 days
1287% · 3,468 predictions · 15 days
1384% · 3,447 predictions · 15 days
1488% · 3,451 predictions · 15 days
1577% · 3,331 predictions · 15 days
1663% · 3,688 predictions · 15 days
1768% · 3,376 predictions · 15 days
1880% · 2,743 predictions · 15 days
1989% · 1,754 predictions · 15 days
2085% · 1,645 predictions · 15 days
2189% · 1,436 predictions · 15 days
2293% · 914 predictions · 15 days
2387% · 405 predictions · 14 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 5, 2026

2 partial-capture days not counted.

What about time of day?

20 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 8, 2026 to Nobyembre 4, 2026: 25 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

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

2% of pairs (1,019) 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.)	8,049	1% (118)	1% (108)
Tanghali (9 a.m. hanggang 3 p.m.)	31,156	1% (334)	1% (262)
Rush hour sa hapon (3 hanggang 6 p.m.)	15,948	3% (479)	4% (591)
Gabi (6 hanggang 10 p.m.)	10,672	1% (74)	1% (58)
Gabi (10 p.m. hanggang 4 a.m.)	502	0% (0)	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: BASELINE 2B to QUEENSWAY 2A, 11.6 km/h actual against 13.1 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
BASELINE 2B	QUEENSWAY 2A	1.5 km	13.1 km/h	11.6 km/h	1,068	6%
RICHMOND / GOLDEN	WESTBORO B	750 m	9 km/h	12.5 km/h	56	0%
QUEENSWAY 1A	BASELINE 1D	1.6 km	13.6 km/h	13.6 km/h	1,073	1%
RIVERVIEW B	NEPEAN WOODS B	1.8 km	14.8 km/h	16.1 km/h	1,188	3%
WESTBORO A	RICHMOND / GOLDEN	820 m	24.7 km/h	17.1 km/h	60	43%
LINCOLN FIELDS 3B	RICHMOND / GOLDEN	3.2 km	20.2 km/h	18.2 km/h	56	0%
RIVERVIEW A	LIMEBANK C	2.6 km	25.9 km/h	19.7 km/h	20	20%
LIMEBANK H	RIVERVIEW B	2.6 km	26 km/h	19.8 km/h	1,169	21%

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.

Hindi po mabasa ngayon ang listahan ng lungsod ng mga gawaing pangkalsada.

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.

23 scheduled trips with counted cancellation notices from Huw, Okt 8 to Miy, Nob 4.

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

Mga oras na may pinakamaraming kanseladong biyahe: 4 PM (6), 5 PM (5), 3 PM (4)

Mga pinakabagong kinanselang biyahe

Mar, Nob 3, scheduled 16:41
Huw, Okt 29, scheduled 15:43
Miy, Okt 28, scheduled 17:25
Miy, Okt 28, scheduled 16:11
Miy, Okt 28, scheduled 15:56

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

Did not come (no bus seen, no notice), last 7 days: 3 of 712 trips we could check.

Buksan ang may petsang pagsusuri ng hula

Hatol

What this route needs

Median provider predictions are 3.2 min later than the timetable in 2 hours of the day.

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

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

Only 99% of scheduled trips were seen; the rest are not counted as missed.

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, 20 hours with samples

00:00: 100% of final predictions within five minutes of the timetable, 463 predictions, typically 0.4 min early
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 94.6% of final predictions within five minutes of the timetable, 297 predictions, typically 1.1 min late
06:00: 94.2% of final predictions within five minutes of the timetable, 1,664 predictions, typically 1.1 min late
07:00: 92.1% of final predictions within five minutes of the timetable, 2,629 predictions, typically 0.7 min late
08:00: 91.3% of final predictions within five minutes of the timetable, 2,962 predictions, typically 1.1 min late
09:00: 80.3% of final predictions within five minutes of the timetable, 3,349 predictions, typically 1.7 min late
10:00: 86.6% of final predictions within five minutes of the timetable, 3,469 predictions, typically 1.1 min late
11:00: 89.3% of final predictions within five minutes of the timetable, 3,491 predictions, typically 1 min late
12:00: 87.2% of final predictions within five minutes of the timetable, 3,468 predictions, typically 1 min late
13:00: 84.4% of final predictions within five minutes of the timetable, 3,447 predictions, typically 1.5 min late
14:00: 88.2% of final predictions within five minutes of the timetable, 3,451 predictions, typically 1.4 min late
15:00: 76.7% of final predictions within five minutes of the timetable, 3,331 predictions, typically 2.2 min late
16:00: 62.6% of final predictions within five minutes of the timetable, 3,688 predictions, typically 3.3 min late
17:00: 67.6% of final predictions within five minutes of the timetable, 3,376 predictions, typically 3.1 min late
18:00: 80.4% of final predictions within five minutes of the timetable, 2,743 predictions, typically 1.7 min late
19:00: 88.8% of final predictions within five minutes of the timetable, 1,754 predictions, typically 0.7 min late
20:00: 84.5% of final predictions within five minutes of the timetable, 1,645 predictions, typically 1.4 min late
21:00: 89% of final predictions within five minutes of the timetable, 1,436 predictions, typically 0.7 min late
22:00: 92.5% of final predictions within five minutes of the timetable, 914 predictions, typically 0.4 min late
23:00: 87.4% of final predictions within five minutes of the timetable, 405 predictions, typically 0.9 min late

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	Kailan	Nasukat	Scenario or next investigation
ProblemPredictions later than timetable	16:00 to 18:00	3.2 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	16:00	63%	Operations, not the timetable
CaveatCoverage gap	All measured hours	99%	More observation, not a service change

Measurements

Predictions later than timetable · 16:00 to 18:00: Measured arrivals 7,064; Hours affected 2; Spread 12.3 min; Median delay 3.2 min; Suggested running time change 3.2 min
One hour has a lower prediction match · 16:00: Oras 16:00; Nasa oras 62.6%; Measured arrivals 3,688; Shortfall 25.2 pts; Route median on time 87.8%
Coverage gap · All measured hours: Target 99.5%; Trips with a matching position 99.3%; Mga araw ng serbisyo 6; Trips with a matching position 707; Mga biyaheng nakatakda sa iskedyul 712

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

How route 74 has been running

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

Pangunahing punto

Resultang may petsa, hindi live na serbisyo

This prediction-to-timetable result describes the dated period, not service right now. It was last calculated 3 hours ago. Current vehicle positions and official notices are checked separately.

83 in 100 eligible predictions were within 5 minutes of the timetable · 83,010 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

Based on 83,010 eligible provider predictions over 27 measured days, from Okt 6, 2026 to Nob 3, 2026.

Updated Nob 5, 2026, 2:32 AM

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.

16–17: 37 in 100 eligible predictions differed from the timetable by more than 5 minutes (3,688 predictions over 15 days).
17–18: 32 in 100 eligible predictions differed from the timetable by more than 5 minutes (3,376 predictions over 15 days).

3 current notices affect this route

• Detour: Routes 57, 61, 62, 63, 74, 75, 87 during nightly Kichi Zībī Mīkan closures
• Limebank Station: Passenger pick-up and drop-off area relocation
• Detour: Routes entering and exiting Limebank Station

Pagkakaiba ng hula ayon sa hintuan

IRIS 2A
32 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,289 predictions over 29 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?: 0 of 12Sinusuri 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?: 5 of 712 checked trips need a closer look5 of 712 trips with enough public-feed evidence had no matching position over 7 days. 0 of 712 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 9.6 min (positive means later; negative means earlier)83 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?: 7.4 min average predicted wait1.2 min beyond the scheduled wait, based on 2,387 eligible predictions at 36 high-frequency stops over 15 days.

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: 119
Mga natatanging hintuan na nasa iskedyul: 83
Iba't ibang inilathalang daanan: 7
Inilathalang oras ng serbisyo: 05:45–01:00 next day

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: 119
Mga natatanging hintuan na nasa iskedyul: 83
Iba't ibang inilathalang daanan: 7
Inilathalang oras ng serbisyo: 05:45–01:00 next day

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 44,155 arrivals over 14 days; after has 18,670 arrivals over 6 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 6, 2026 to Nobyembre 3, 2026

Sa loob ng 5 minuto mula sa iskedyul: 83.1%
Mga karapat-dapat na hula na nasuri: 83,010
Mga araw ng linggo na may datos: 19
Tinatayang pagkaantala sa ika-95 na percentile: 9.6 min late

Patterns by hour (20)

Patterns by hour (20)
Oras	Nasa oras	Median	95th percentile	Ebidensya
00:00	100.0%	0.4 min early	2.1 min late	463 · 14 days
05:00	94.6%	1.1 min late	5.9 min late	297 · 11 days
06:00	94.2%	1.1 min late	5.3 min late	1,664 · 13 days
07:00	92.1%	0.7 min late	5.8 min late	2,629 · 15 days
08:00	91.3%	1.1 min late	5.7 min late	2,962 · 15 days
09:00	80.3%	1.7 min late	8.4 min late	3,349 · 15 days
10:00	86.6%	1.1 min late	7 min late	3,469 · 15 days
11:00	89.3%	1 min late	6.4 min late	3,491 · 15 days
12:00	87.2%	1 min late	8.7 min late	3,468 · 15 days
13:00	84.4%	1.5 min late	9.1 min late	3,447 · 15 days
14:00	88.2%	1.4 min late	6.9 min late	3,451 · 15 days
15:00	76.7%	2.2 min late	10 min late	3,331 · 15 days
16:00	62.6%	3.3 min late	13.7 min late	3,688 · 15 days
17:00	67.6%	3.1 min late	17.4 min late	3,376 · 15 days
18:00	80.4%	1.7 min late	11 min late	2,743 · 15 days
19:00	88.8%	0.7 min late	9.5 min late	1,754 · 15 days
20:00	84.5%	1.4 min late	8.1 min late	1,645 · 15 days
21:00	89.0%	0.7 min late	6.2 min late	1,436 · 15 days
22:00	92.5%	0.4 min late	6 min late	914 · 15 days
23:00	87.4%	0.9 min late	8.2 min late	405 · 14 days

2 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

707 / 712 scheduled trips published at least one position across 6 service days (99.3%).

20:001 / 27 trips without a position96.3%
12:001 / 48 trips without a position97.9%
13:001 / 48 trips without a position97.9%
17:001 / 48 trips without a position97.9%
16:001 / 53 trips without a position98.1%
00:000 / 12 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 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

November 4, 2026 · 119 trips in the retained timetable · retained notices; capture coverage unverified

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

05:45– 06:35
Trip 24265040Vehicle position matchedFirst / last feed position: 5:26 a.m. EST / 6:52 a.m. EST; not actual start or end times.
05:50– 06:08
Trip 20698040Vehicle position matchedFirst / last feed position: 5:04 a.m. EST / 6:20 a.m. EST; not actual start or end times.
06:05– 06:51
Trip 12024040Vehicle position matchedFirst / last feed position: 5:38 a.m. EST / 7:16 a.m. EST; not actual start or end times.
06:09– 06:59
Trip 16977040Vehicle position matchedFirst / last feed position: 5:48 a.m. EST / 6:59 a.m. EST; not actual start or end times.
06:23– 07:17
Trip 35549040Vehicle position matchedFirst / last feed position: 5:37 a.m. EST / 7:23 a.m. EST; not actual start or end times.
06:39– 07:36
Trip 3055040Vehicle position matchedFirst / last feed position: 6:19 a.m. EST / 7:42 a.m. EST; not actual start or end times.
06:40– 07:27
Trip 28502040Vehicle position matchedFirst / last feed position: 6:43 a.m. EST / 7:34 a.m. EST; not actual start or end times.
06:52– 07:49
Trip 22401040Vehicle position matchedFirst / last feed position: 6:41 a.m. EST / 7:52 a.m. EST; not actual start or end times.
07:07– 08:04
Trip 9947040Vehicle position matchedFirst / last feed position: 6:47 a.m. EST / 8:08 a.m. EST; not actual start or end times.
07:10– 08:03
Trip 32035040Vehicle position matchedFirst / last feed position: 7:14 a.m. EST / 8:06 a.m. EST; not actual start or end times.
07:17– 07:59
Trip 15301040Vehicle position matchedFirst / last feed position: 7:12 a.m. EST / 7:59 a.m. EST; not actual start or end times.
07:19– 08:16
Trip 20998040Vehicle position matchedFirst / last feed position: 7:18 a.m. EST / 8:17 a.m. EST; not actual start or end times.

· Open all evidence for this day