Stop impacts: #3019 -- Pinecrest A and B relocation: September 01 2026 - Updates to routing and alternate stops for routes 301, 303, 404, 406, and 454 made on September 14, 2026. From 5:00 am on Wednesday, September 9, until further notice, all bus platforms at Pinecrest Station will be relocated outside of the station bus loop and onto Pinecrest Road for ongoing work. As a result, routes 60, 61, 62, 63, 66, 67, 81, 82, 301, 303, 404, 406, 454, and 691 will service alternate stops. Please allow extra time for your travels. Affected stops Bus Stop (560#) not in use · Routes · Alternate Stop #3019 -- Pinecrest A · · 61 Stittsville · 62 Stittsville · 63 Innovation / Briarbrook · 81 Tunney's Pasture · 82 Baseline · 301 Richmond / Stittsville · 303 Carp · 404 Canadian Tire Centre · 406 Canadian Tire Centre · 454 Terry Fox · 691 Omer-Deslauriers · TEMP -- Pinecrest (west-side) / station entrance #3019 -- Pinecrest B · · 60 Terry Fox / Tunney's Pasture · 66 Tunneys Pasture · 67 Terry Fox / Tunney's Pasture · #5595 -- Pinecrest (east-side) / Queensview #3019 -- Pinecrest B · · 61 Tunney's Pasture & N Rideau · 62 Tunney's Pasture · 63 Tunney's Pasture No service to Pinecrest Station, September 19 – 20 · TEMP -- Pinecrest (east-side) / Iris (EB 417 on-ramp from Pinecrest) #3019 -- Pinecrest B · · 301 Bayshore / Carlingwood · 303 Carlingwood · #1946 -- Pinecrest Mall #3019 -- Pinecrest B · · 404 Tunney's Pasture · 406 Limebank · 454 Lansdowne · TEMP -- Pinecrest (east-side) / Iris (EB 417 on-ramp from Pinecrest) Detour routing 60 Terry Fox / Tunney's Pasture: From Pinecrest northbound, do not enter station, service temporary platform on Pinecrest at Quensview, continue regular route. 61 Tunney's Pasture: From Pinecrest northbound, do not enter station, service temporary platform on Pinecrest at Quensview, continue regular route. 61 Stittsville: From Highway 417 westbound off-ramp, do not enter station, left onto Pinecrest, service temporary stop outside station, right onto ramp to Highway 417 westbound. 62 Tunney's Pasture: From Pinecrest northbound, service temporary platform on Pinecrest at Quensview, continue regular route. 62 Stittsville: From Highway 417 westbound off-ramp, do not enter station, left onto Pinecrest, service temporary stop outside station, right onto ramp to Highway 417 westbound. 63 Tunney's Pasture: From Pinecrest northbound, do not enter station, service temporary platform on Pinecrest at Quensview, continue regular route. 63 Innovation/ Briarbrook: From Highway 417 westbound off-ramp, do not enter station, left onto Pinecrest, service temporary stop outside station, right onto ramp to Highway 417 westbound. 66 Tunney's Pasture: From Pinecrest northbound, do not enter station, service temporary platform on Pinecrest at Quensview, continue regular route. 67 Terry Fox / Tunney's Pasture: From Pinecrest northbound, do not enter station, service temporary platform on Pinecrest at Quensview, continue regular route. 81 Tunney's Pasture: From Pinecrest southbound, do not enter station, service, temporary stop outside station, continue Greenbank to regular route. 82 Baseline: From Pinecrest southbound, do not enter station, service, temporary stop outside station, continue Greenbank to regular route. 301 Richmond / Stittsville: From Highway 417 westbound off-ramp at Pinecrest, left onto Pinecrest Service temporary stop on Pinecrest, right onto Ramp to Highway 417 wesbtound. 301 Bayshore: From Highway 417 eastbound off-ramp at Pinecrest, continue Iris, Keep left and continue Mall Roadway, use Pinecrest Mall loop to turnaround, left onto Mall Roadway, right onto to remain on Iris, right onto Pinecrest, right onto Ramp to Highway 417 Eastbound, continue regular route. 303 Carp: From Highway 417 westbound off-ramp at Pinecrest, left onto Pinecrest Service temporary stop on Pinecrest, right onto Ramp to Highway 417 wesbtound. 303 Carlingwood: From Highway 417 eastbound off-ramp at Pinecrest, continue Iris, Keep left and continue Mall Roadway, use Pinecrest Mall loop to turnaround, left onto Mall Roadway, right onto to remain on Iris, right onto Pinecrest, right onto Ramp to Highway 417 Eastbound, continue regular route. 404 Tunney's Pasture: From Highway 417 eastbound off-ramp at Pinecrest, left onto Pinecrest, right onto Highway 417 eastbound, service stop on Pinecrest on-ramp. 404 Canadian Tire Centre: From Highway 417 westbound off-ramp at Pinecrest, left onto Pinecrest, service temporary stop, right onto ramp to Highway 417 westound. 406 Limebank: From Highway 417 eastbound off-ramp at Pinecrest, left onto Pinecrest, right onto Highway 417 eastbound, service stop on Pinecrest on-ramp. 406 Canadian Tire Centre: From Highway 417 westbound off-ramp at Pinecrest, left onto Pinecrest, service temporary stop, right onto ramp to Highway 417 westound. 454 Lansdowne: From Highway 417 eastbound off-ramp at Pinecrest, left onto Pinecrest, right onto Highway 417 eastbound, service stop on Pinecrest on-ramp. 454 Terry Fox: From Highway 417 westbound off-ramp at Pinecrest, left onto Pinecrest, service temporary stop, right onto ramp to Highway 417 westound. 691 Omer-Deslauriers: From Pinecrest southbound, do not enter station, continue southbound and service temporary stop, continue regular route.

No 82 trips cancelled now · 1 did not run in NobyembreCancellations →

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

Ruta 82: Baseline ⇄ Lincoln Fields & Tunney's Pasture

Bawat 27 hanggang 31 min

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

Trips needing investigation

3 of 486 trips with a usable feed window (0.6%) had no matching position.

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

483 with position · 3 to investigate · 0 excluded · 486 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nob 3, 2026, 1:56 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: 483 / 486 (99.4%). 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, 12: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

84%

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

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

The hours we have evidence for

0095% · 486 predictions · 14 days
04100% · 121 predictions · 11 days
0591% · 1,397 predictions · 11 days
0694% · 1,613 predictions · 13 days
0797% · 1,836 predictions · 14 days
0890% · 2,965 predictions · 14 days
0989% · 2,842 predictions · 14 days
1082% · 2,880 predictions · 14 days
1182% · 3,021 predictions · 14 days
1284% · 2,977 predictions · 14 days
1381% · 2,988 predictions · 14 days
1485% · 3,013 predictions · 14 days
1572% · 2,856 predictions · 14 days
1669% · 3,007 predictions · 14 days
1768% · 3,181 predictions · 14 days
1882% · 2,982 predictions · 14 days
1984% · 2,893 predictions · 14 days
2088% · 2,750 predictions · 14 days
2192% · 2,666 predictions · 14 days
2291% · 2,331 predictions · 14 days
2398% · 1,417 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 3, 2026

2 partial-capture days not counted.

What about time of day?

21 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

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

0% of pairs (112) 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,131	1% (20)	2% (59)
Tanghali (9 a.m. hanggang 3 p.m.)	27,470	0% (42)	0% (7)
Rush hour sa hapon (3 hanggang 6 p.m.)	11,953	0% (51)	0% (39)
Gabi (6 hanggang 10 p.m.)	14,805	0% (22)	0% (7)
Gabi (10 p.m. hanggang 4 a.m.)	3,841	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: PINECREST A to PINECREST MALL, 7.4 km/h actual against 6 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
PINECREST A	PINECREST MALL	300 m	6 km/h	7.4 km/h	618	2%
LINCOLN FIELDS 4A	PINECREST A	2.2 km	15.7 km/h	13.7 km/h	795	7%
MORRISON / DRAPER	LINCOLN FIELDS 3A	4.4 km	18.1 km/h	16.8 km/h	116	3%
GREENBANK / CANFIELD	MORRISON / DRAPER	4.4 km	15.8 km/h	18.4 km/h	115	0%
TUNNEY'S PASTURE D	WESTBORO A	1.6 km	22 km/h	18.8 km/h	111	24%
MORRISON / BASELINE	PINECREST MALL	2.1 km	18.8 km/h	20.2 km/h	552	3%
PINECREST MALL	CRAIG HENRY / GREENBANK	6.2 km	22.1 km/h	20.3 km/h	618	2%
MAJESTIC / NEWHAVEN	GREENBANK / CANFIELD	3.3 km	24.4 km/h	21.1 km/h	116	3%

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.

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

Not counted: 15 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 PM (2), 5 PM (1)

Mga pinakabagong kinanselang biyahe

Lin, Nob 1, scheduled 19:18
Lun, Okt 26, scheduled 17:44
Sab, Okt 17, scheduled 19:45

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: 1 of 486 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.

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

Scenario: 3 min more running time on 56 trips. The schedule-block model adds no 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, 21 hours with samples

00:00: 95.3% of final predictions within five minutes of the timetable, 486 predictions, typically 0.9 min late
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: 100% of final predictions within five minutes of the timetable, 121 predictions, typically 1.6 min late
05:00: 91.4% of final predictions within five minutes of the timetable, 1,397 predictions, typically 1.8 min late
06:00: 94.4% of final predictions within five minutes of the timetable, 1,613 predictions, typically 1.3 min late
07:00: 96.6% of final predictions within five minutes of the timetable, 1,836 predictions, typically 1.1 min late
08:00: 90.2% of final predictions within five minutes of the timetable, 2,965 predictions, typically 1.5 min late
09:00: 88.9% of final predictions within five minutes of the timetable, 2,842 predictions, typically 1.5 min late
10:00: 81.9% of final predictions within five minutes of the timetable, 2,880 predictions, typically 2.7 min late
11:00: 81.9% of final predictions within five minutes of the timetable, 3,021 predictions, typically 2.6 min late
12:00: 83.5% of final predictions within five minutes of the timetable, 2,977 predictions, typically 2.1 min late
13:00: 81.4% of final predictions within five minutes of the timetable, 2,988 predictions, typically 1.9 min late
14:00: 85.2% of final predictions within five minutes of the timetable, 3,013 predictions, typically 1.8 min late
15:00: 71.6% of final predictions within five minutes of the timetable, 2,856 predictions, typically 1.7 min late
16:00: 68.5% of final predictions within five minutes of the timetable, 3,007 predictions, typically 2.7 min late
17:00: 67.9% of final predictions within five minutes of the timetable, 3,181 predictions, typically 3.2 min late
18:00: 81.5% of final predictions within five minutes of the timetable, 2,982 predictions, typically 1.7 min late
19:00: 84.1% of final predictions within five minutes of the timetable, 2,893 predictions, typically 1.7 min late
20:00: 88.4% of final predictions within five minutes of the timetable, 2,750 predictions, typically 1.2 min late
21:00: 92.2% of final predictions within five minutes of the timetable, 2,666 predictions, typically 0.7 min late
22:00: 90.9% of final predictions within five minutes of the timetable, 2,331 predictions, typically 0.6 min late
23:00: 97.8% of final predictions within five minutes of the timetable, 1,417 predictions, typically 0.8 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	17:00	3.2 min late	More running time
ProblemOne hour has a lower prediction match	17:00	68%	Operations, not the timetable

Measurements

Predictions later than timetable · 17:00: Measured arrivals 3,181; Hours affected 1; Spread 7.8 min; Median delay 3.2 min; Suggested running time change 3.2 min
One hour has a lower prediction match · 17:00: Oras 17:00; Nasa oras 67.9%; Measured arrivals 3,181; Shortfall 20.5 pts; Route median on time 88.4%

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

How route 82 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.

84 in 100 eligible predictions were within 5 minutes of the timetable · 95,114 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

Based on 95,114 eligible provider predictions over 27 measured days, from Okt 5, 2026 to Nob 2, 2026.

Updated Nob 3, 2026, 12: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: 32 in 100 eligible predictions differed from the timetable by more than 5 minutes (3,181 predictions over 14 days).
16–17: 32 in 100 eligible predictions differed from the timetable by more than 5 minutes (3,007 predictions over 14 days).

1 current notice affects this route

• Stop impacts: #3019 -- Pinecrest A and B relocation

Pagkakaiba ng hula ayon sa hintuan

Wala pa kaming sapat na kasaysayan ng ruta bawat hintuan para pangalanan ang paulit-ulit na problemang hintuan. Ginagamit lang na pahiwatig ang mga ulat ng mga sakay, hindi patunay.

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?: 3 of 486 checked trips need a closer look3 of 486 trips with enough public-feed evidence had no matching position over 7 days. 0 of 486 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 8.0 min (positive means later; negative means earlier)84 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: 74
Mga natatanging hintuan na nasa iskedyul: 122
Iba't ibang inilathalang daanan: 10
Inilathalang oras ng serbisyo: 04:53–00:19 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: 74
Mga natatanging hintuan na nasa iskedyul: 122
Iba't ibang inilathalang daanan: 10
Inilathalang oras ng serbisyo: 04:53–00:19 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 50,056 arrivals over 14 days; after has 13,747 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: 84.0%
Mga karapat-dapat na hula na nasuri: 95,114
Mga araw ng linggo na may datos: 19
Tinatayang pagkaantala sa ika-95 na percentile: 8 min late

Patterns by hour (21)

Patterns by hour (21)
Oras	Nasa oras	Median	95th percentile	Ebidensya
00:00	95.3%	0.9 min late	4.8 min late	486 · 14 days
04:00	100.0%	1.6 min late	3.8 min late	121 · 11 days
05:00	91.4%	1.8 min late	7.1 min late	1,397 · 11 days
06:00	94.4%	1.3 min late	5 min late	1,613 · 13 days
07:00	96.6%	1.1 min late	4.6 min late	1,836 · 14 days
08:00	90.2%	1.5 min late	5.8 min late	2,965 · 14 days
09:00	88.9%	1.5 min late	6.3 min late	2,842 · 14 days
10:00	81.9%	2.7 min late	7.7 min late	2,880 · 14 days
11:00	81.9%	2.6 min late	8 min late	3,021 · 14 days
12:00	83.5%	2.1 min late	7.7 min late	2,977 · 14 days
13:00	81.4%	1.9 min late	7.6 min late	2,988 · 14 days
14:00	85.2%	1.8 min late	7.9 min late	3,013 · 14 days
15:00	71.6%	1.7 min late	11.2 min late	2,856 · 14 days
16:00	68.5%	2.7 min late	10.7 min late	3,007 · 14 days
17:00	67.9%	3.2 min late	11 min late	3,181 · 14 days
18:00	81.5%	1.7 min late	8.7 min late	2,982 · 14 days
19:00	84.1%	1.7 min late	7.7 min late	2,893 · 14 days
20:00	88.4%	1.2 min late	6.4 min late	2,750 · 14 days
21:00	92.2%	0.7 min late	6.1 min late	2,666 · 14 days
22:00	90.9%	0.6 min late	6.4 min late	2,331 · 14 days
23:00	97.8%	0.8 min late	4 min late	1,417 · 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

483 / 486 scheduled trips published at least one position across 1 service days (99.4%).

23:001 / 13 trips without a position92.3%
20:001 / 26 trips without a position96.2%
19:001 / 27 trips without a position96.3%
04:000 / 5 trips without a position100.0%
05:000 / 10 trips without a position100.0%
06:000 / 16 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 · 74 trips in the retained timetable · retained notices; capture coverage unverified

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

04:53– 05:46
Trip 7369020Vehicle position matchedFirst / last feed position: 4:36 a.m. EST / 5:55 a.m. EST; not actual start or end times.
05:10– 05:45
Trip 8219020Vehicle position matchedFirst / last feed position: 4:57 a.m. EST / 6:00 a.m. EST; not actual start or end times.
05:38– 06:30
Trip 35670020Vehicle position matchedFirst / last feed position: 5:41 a.m. EST / 6:30 a.m. EST; not actual start or end times.
06:04– 06:49
Trip 17757020Vehicle position matchedFirst / last feed position: 5:52 a.m. EST / 7:01 a.m. EST; not actual start or end times.
06:17– 07:16
Trip 36983020Vehicle position matchedFirst / last feed position: 6:13 a.m. EST / 7:11 a.m. EST; not actual start or end times.
06:47– 07:57
Trip 7755020Vehicle position matchedFirst / last feed position: 6:27 a.m. EST / 7:51 a.m. EST; not actual start or end times.
07:08– 08:00
Trip 36776020Vehicle position matchedFirst / last feed position: 7:03 a.m. EST / 8:02 a.m. EST; not actual start or end times.
07:18– 08:37
Trip 17852020Vehicle position matchedFirst / last feed position: 7:13 a.m. EST / 8:39 a.m. EST; not actual start or end times.
07:47– 09:04
Trip 24371020Vehicle position matchedFirst / last feed position: 7:47 a.m. EST / 9:58 a.m. EST; not actual start or end times.
08:06– 09:01
Trip 32945020Vehicle position matchedFirst / last feed position: 7:45 a.m. EST / 9:15 a.m. EST; not actual start or end times.
08:11– 08:28
Trip 6353020Vehicle position matchedFirst / last feed position: 7:56 a.m. EST / 8:30 a.m. EST; not actual start or end times.
08:11– 08:28
Trip 8703020Vehicle position matchedFirst / last feed position: 8:12 a.m. EST / 8:33 a.m. EST; not actual start or end times.

· Open all evidence for this day