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+1 more notice

No 87 trips cancelled now · 4 did not run in NobyembreCancellations →

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

Ruta 87: Tunney's Pasture ⇄ Baseline

Bawat 15 hanggang 30 min

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

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: 3 trips with qualifying later matching vehicle observations. Trips with any notice: 7.

Trips needing investigation

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

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

610 with position · 5 to investigate · 0 excluded · 615 scheduled trips

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

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: 610 / 615 (99.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: Nob 3, 2026, 6:09 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

86.9%

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

Predictions in the source: 42,022
Weekdays with evidence: 19
Evidence window: Okt 5, 2026 – Nob 2, 2026

The hours we have evidence for

0697% · 408 predictions · 11 days
0796% · 907 predictions · 12 days
0892% · 1,520 predictions · 12 days
0990% · 1,714 predictions · 12 days
1090% · 1,752 predictions · 14 days
1193% · 1,861 predictions · 14 days
1293% · 1,868 predictions · 14 days
1388% · 1,868 predictions · 14 days
1487% · 1,896 predictions · 14 days
1580% · 1,802 predictions · 14 days
1661% · 1,819 predictions · 14 days
1772% · 1,437 predictions · 14 days
1892% · 1,304 predictions · 14 days
1991% · 884 predictions · 14 days
2084% · 760 predictions · 10 days
2183% · 763 predictions · 10 days
2296% · 129 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?

17 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

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

1% of pairs (262) 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.)	3,965	0% (14)	0% (17)
Tanghali (9 a.m. hanggang 3 p.m.)	19,032	0% (93)	0% (83)
Rush hour sa hapon (3 hanggang 6 p.m.)	8,950	2% (159)	2% (161)
Gabi (6 hanggang 10 p.m.)	5,278	0% (19)	0% (1)
Gabi (10 p.m. hanggang 4 a.m.)	219	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 2A to CARLINGWOOD MALL - REXALL, 16 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 2A	CARLINGWOOD MALL - REXALL	3 km	13.1 km/h	16 km/h	939	1%
RICHMOND / GOLDEN	CARLINGWOOD MALL - REXALL	2.6 km	12.1 km/h	18.2 km/h	57	0%
TUNNEY'S PASTURE D	CARLINGWOOD MALL - REXALL	5.3 km	16.6 km/h	19.8 km/h	969	1%
TUNNEY'S PASTURE D	RICHMOND / GOLDEN	2.5 km	18.4 km/h	21.1 km/h	56	2%
CARLINGWOOD MALL - REXALL	RICHMOND / GOLDEN	2.9 km	34.5 km/h	22.1 km/h	57	60%

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
FAIRLAWN between LENESTER and ESTERLAWN
Okt 15, 2026, 12:00 AM to Nob 13, 2026, 5:00 PM
FAIRLAWN off-peak lane reductions between LENESTER and ESTERLAWN due to construction, from October 15th to November 13th.
Minarkahan ito ng Lungsod na nakakaapekto sa transit.
about 0 m from the route
City record updated Okt 16, 2026, 11:20 AM.
Gawaing kalsada
RICHMOND W/B between CLEARY and WOODROFFE
Okt 26, 2026, 12:00 AM to Nob 6, 2026, 5:00 PM
RICHMOND westbound lane reduction between CLEARY and WOODROFFE due to construction, until November 6th.
Minarkahan ito ng Lungsod na nakakaapekto sa transit.
about 0 m from the route
City record updated Nob 3, 2026, 6:40 AM.
Gawaing kalsada
Kichi Zibi Mikan between ISLAND PARK and WOODROFFE
Okt 30, 2026, 9:30 AM to Nob 20, 2026, 3:00 PM
Kichi Zibi Mikan reduced to 1 lane in each direction between ISLAND PARK and WOODROFFE due to construction, from November 2nd to 20th between 9:30am and 3:00pm.
about 0 m from the route
City record updated Okt 30, 2026, 9:28 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.

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

Not counted: 16 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 (4), 2 PM (2), 8 AM (1)

Mga pinakabagong kinanselang biyahe

Lun, Nob 2, scheduled 16:28
Lun, Nob 2, scheduled 14:27
Miy, Okt 28, scheduled 08:40
Mar, Okt 27, scheduled 16:50
Miy, Okt 21, scheduled 16:50

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: 4 of 615 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 1 hours of the day.

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

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

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

Scenario: 3 min more running time on 86 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, 17 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: 96.8% of final predictions within five minutes of the timetable, 408 predictions, typically 1 min late
07:00: 96.1% of final predictions within five minutes of the timetable, 907 predictions, typically 0.1 min early
08:00: 91.5% of final predictions within five minutes of the timetable, 1,520 predictions, typically 0.5 min late
09:00: 89.6% of final predictions within five minutes of the timetable, 1,714 predictions, typically 1.3 min late
10:00: 90.2% of final predictions within five minutes of the timetable, 1,752 predictions, typically 0.5 min late
11:00: 92.6% of final predictions within five minutes of the timetable, 1,861 predictions, typically 1.1 min late
12:00: 92.6% of final predictions within five minutes of the timetable, 1,868 predictions, typically 1.2 min late
13:00: 87.9% of final predictions within five minutes of the timetable, 1,868 predictions, typically 1.1 min late
14:00: 87.3% of final predictions within five minutes of the timetable, 1,896 predictions, typically 0.9 min late
15:00: 79.5% of final predictions within five minutes of the timetable, 1,802 predictions, typically 2 min late
16:00: 60.5% of final predictions within five minutes of the timetable, 1,819 predictions, typically 3.2 min late
17:00: 72.1% of final predictions within five minutes of the timetable, 1,437 predictions, typically 2.2 min late
18:00: 92% of final predictions within five minutes of the timetable, 1,304 predictions, typically 0.7 min late
19:00: 90.8% of final predictions within five minutes of the timetable, 884 predictions, typically 1.1 min late
20:00: 84.1% of final predictions within five minutes of the timetable, 760 predictions, typically 1.7 min late
21:00: 83.4% of final predictions within five minutes of the timetable, 763 predictions, typically 1.3 min late
22:00: 96.1% of final predictions within five minutes of the timetable, 129 predictions, typically 1.8 min late
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

Findings
What	Kailan	Nasukat	Scenario or next investigation
ProblemPredictions later than timetable	16:00	3.2 min late	More running time
ProblemOne hour has a lower prediction match	16:00	61%	Operations, not the timetable
CaveatCoverage gap	All measured hours	99%	More observation, not a service change

Measurements

Predictions later than timetable · 16:00: Measured arrivals 1,819; Hours affected 1; Spread 11.6 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 60.5%; Measured arrivals 1,819; Shortfall 29.7 pts; Route median on time 90.2%
Coverage gap · All measured hours: Target 99.5%; Trips with a matching position 99.2%; Mga araw ng serbisyo 5; Trips with a matching position 610; Mga biyaheng nakatakda sa iskedyul 615

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

How route 87 has been running

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

Pangunahing punto

Karaniwang malapit sa iskedyul ang mga hula ng tagapagbigay ng serbisyo, pero tingnan po ang mga oras na may problema sa ibaba.

87 in 100 eligible predictions were within 5 minutes of the timetable · 42,022 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

Based on 42,022 eligible provider predictions over 27 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.

16–17: 40 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,819 predictions over 14 days).

2 current notices affect this route

• Detour: Routes 57, 61, 62, 63, 74, 75, 87 during nightly Kichi Zībī Mīkan closures
• Detour: Route 87 during Woodroffe Avenue closure (Byron/Richmond to Kichi Zibi Mikan)

Pagkakaiba ng hula ayon sa hintuan

RICHMOND / GOLDEN
32 in 100 eligible predictions differed from the timetable by more than 5 minutes (74 predictions over 4 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 615 checked trips need a closer look5 of 615 trips with enough public-feed evidence had no matching position over 7 days. 0 of 615 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 7.8 min (positive means later; negative means earlier)87 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?: Ang karaniwang inaasahang dagdag na paghihintay ay wala pang 30 segundo sa hintuang kinunan ng sample0.2 min less than the scheduled wait, based on 1,134 eligible predictions at 1 stop hours across 13 service 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: 107
Mga natatanging hintuan na nasa iskedyul: 40
Iba't ibang inilathalang daanan: 4
Inilathalang oras ng serbisyo: 05:59–22:09

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: 107
Mga natatanging hintuan na nasa iskedyul: 40
Iba't ibang inilathalang daanan: 4
Inilathalang oras ng serbisyo: 05:59–22:09

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 22,730 arrivals over 14 days; after has 5,470 arrivals over 4 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: 86.9%
Mga karapat-dapat na hula na nasuri: 42,022
Mga araw ng linggo na may datos: 19
Tinatayang pagkaantala sa ika-95 na percentile: 7.8 min late

Patterns by hour (18)

Patterns by hour (18)
Oras	Nasa oras	Median	95th percentile	Ebidensya
05:00	100.0%	1.3 min late	3.1 min late	22 · 11 days
06:00	96.8%	1 min late	4 min late	408 · 11 days
07:00	96.1%	0.1 min early	3.5 min late	907 · 12 days
08:00	91.5%	0.5 min late	6 min late	1,520 · 12 days
09:00	89.6%	1.3 min late	7.4 min late	1,714 · 12 days
10:00	90.2%	0.5 min late	6.5 min late	1,752 · 14 days
11:00	92.6%	1.1 min late	5.7 min late	1,861 · 14 days
12:00	92.6%	1.2 min late	5.8 min late	1,868 · 14 days
13:00	87.9%	1.1 min late	6.6 min late	1,868 · 14 days
14:00	87.3%	0.9 min late	7.2 min late	1,896 · 14 days
15:00	79.5%	2 min late	9.5 min late	1,802 · 14 days
16:00	60.5%	3.2 min late	14.8 min late	1,819 · 14 days
17:00	72.1%	2.2 min late	17 min late	1,437 · 14 days
18:00	92.0%	0.7 min late	5.9 min late	1,304 · 14 days
19:00	90.8%	1.1 min late	6.2 min late	884 · 14 days
20:00	84.1%	1.7 min late	6.7 min late	760 · 10 days
21:00	83.4%	1.3 min late	8 min late	763 · 10 days
22:00	96.1%	1.8 min late	4.8 min late	129 · 10 days

1 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

610 / 615 scheduled trips published at least one position across 5 service days (99.2%).

07:002 / 41 trips without a position95.1%
08:002 / 49 trips without a position95.9%
16:001 / 43 trips without a position97.7%
05:000 / 5 trips without a position100.0%
06:000 / 20 trips without a position100.0%
09:000 / 44 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 · 107 trips in the retained timetable · retained notices; capture coverage unverified

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

05:59– 06:14
Trip 10048020Vehicle position matchedFirst / last feed position: 6:00 a.m. EST / 6:12 a.m. EST; not actual start or end times.
06:27– 06:42
Trip 18016020Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 6:38 a.m. EST; not actual start or end times.
06:29– 06:44
Trip 3882020Vehicle position matchedFirst / last feed position: 6:30 a.m. EST / 6:49 a.m. EST; not actual start or end times.
06:48– 07:03
Trip 3370020Vehicle position matchedFirst / last feed position: 6:12 a.m. EST / 6:59 a.m. EST; not actual start or end times.
06:48– 07:03
Trip 5521020Vehicle position matchedFirst / last feed position: 6:40 a.m. EST / 7:14 a.m. EST; not actual start or end times.
07:05– 07:20
Trip 8202020Vehicle position matchedFirst / last feed position: 7:00 a.m. EST / 7:23 a.m. EST; not actual start or end times.
07:10– 07:29
Trip 30955020Vehicle position matchedFirst / last feed position: 7:15 a.m. EST / 7:25 a.m. EST; not actual start or end times.
07:17– 07:32
Trip 30641020Vehicle position matchedFirst / last feed position: 7:10 a.m. EST / 7:32 a.m. EST; not actual start or end times.
07:23– 07:52
Trip 32845020Vehicle position matchedFirst / last feed position: 7:23 a.m. EST / 7:50 a.m. EST; not actual start or end times.
07:32– 07:47
Trip 16628020Vehicle position matchedFirst / last feed position: 7:27 a.m. EST / 7:47 a.m. EST; not actual start or end times.
07:38– 08:07
Trip 24966020Vehicle position matchedFirst / last feed position: 6:55 a.m. EST / 8:04 a.m. EST; not actual start or end times.
07:39– 08:08
Trip 17800020Vehicle position matchedFirst / last feed position: 6:54 a.m. EST / 8:15 a.m. EST; not actual start or end times.

· Open all evidence for this day