Stop impacts: #4036 -- Holly Acres (south-side) / Ramp temporary relocation: October 30 2026 - From 11:00 pm on Monday, November 2, until 11:00 pm on Friday, December 4, stop #4036 -- Holly Acres (south-side) / Ramp will be temporarily relocated 120 metres closer to Richmond Road due to construction work near the Highway 417 off-ramp. There will be no detours, but the routes below will be impacted by the stop relocation: 57 Carling Campus ~ Complexe Carling 60 Terry Fox / Tunney's Pasture 61 Tunney's Pasture & N Rideau 62 Tunney's Pasture 63 Tunney's Pasture 66 Tunneys Pasture 67 Terry Fox / Tunney's Pasture 88 Hurdman 261 Tunney's Pasture 262 Tunney's Pasture 263 Tunney's Pasture 265 Tunney's Pasture 266 Tunney's Pasture

No 88 trips cancelled now · 7 did not run in NobyembreCancellations →

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

Ruta 88: Hurdman ⇄ Bayshore

Bawat 10 hanggang 19 min

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

BAYSHORE C21 min sched.
HOLLY ACRES / BAYSHORE STATION21 min sched.
HOLLY ACRES / RAMP22 min sched.
JOHN SUTHERLAND / RICHMOND24 min sched.
QUEENSWAY CARLETON / IRVING GREENBERG25 min sched.
QUEENSWAY CARLETON / EMERGENCY26 min sched.
BASELINE / SIOUX27 min sched.
BASELINE / SANDCASTLE27 min sched.
BASELINE / MONTEREY28 min sched.
BASELINE / GUTHRIE29 min sched.
BASELINE / GREENBANK30 min sched.
BASELINE / MCWATTERS30 min sched.
BASELINE / ROCKWAY31 min sched.
BASELINE / AD. 232331 min sched.
BASELINE / CENTREPOINTE32 min sched.
BASELINE / HIGHGATE32 min sched.
BASELINE / CENTREPOINTE33 min sched.
CONSTELLATION / GEMINI33 min sched.
BASELINE 1A34 min sched.
NIGIG / ALGONQUIN COLLEGE
WAJASHK / ALGONQUIN COLLEGE RESIDENCE36 min sched.
BASELINE / NAVAHO37 min sched.
BASELINE / DEER FIELD38 min sched.
BASELINE / CORDOVA39 min sched.
BASELINE / BASSANO39 min sched.
BASELINE / PENDER40 min sched.
BASELINE / ST HELEN'S40 min sched.
BASELINE / CLYDE41 min sched.
BASELINE / LAURENTIAN PLACE41 min sched.
1305 BASELINE42 min sched.
BASELINE / MERIVALE43 min sched.
BASELINE / FARLANE43 min sched.
BASELINE / ZENA44 min sched.
BASELINE / MARSON45 min sched.
BASELINE / FISHER45 min sched.
BASELINE / LEXINGTON46 min sched.
BASELINE / PRINCE OF WALES46 min sched.
HERON / HERON BRIDGE47 min sched.
HERON / RIVERSIDE48 min sched.
HERON / RIVERSIDE49 min sched.
MOONEY'S BAY A50 min sched.
HERON 4A50 min sched.
DATA CENTRE / BILLINGS BRIDGE51 min sched.
BILLINGS BRIDGE 2A (B)52 min sched.
PLEASANT PARK 2A (A)55 min sched.
RIVERSIDE 2A (A)56 min sched.
SMYTH 2A (A)57 min sched.
LYCÉE CLAUDEL 2A (A)59 min sched.
HURDMAN B61 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: 10 trips with qualifying later matching vehicle observations. Trips with any notice: 12.

Trips needing investigation

8 of 1,043 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.

1,035 with position · 8 to investigate · 0 excluded · 1,043 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nob 5, 2026, 3:56 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: 1,035 / 1,043 (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 5, 2026, 3:08 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.2%

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

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

The hours we have evidence for

0089% · 2,168 predictions · 14 days
0188% · 815 predictions · 12 days
0495% · 1,323 predictions · 11 days
0585% · 2,142 predictions · 15 days
0690% · 4,534 predictions · 15 days
0787% · 6,711 predictions · 15 days
0880% · 5,628 predictions · 15 days
0982% · 4,499 predictions · 15 days
1083% · 4,283 predictions · 15 days
1192% · 4,429 predictions · 15 days
1282% · 4,478 predictions · 15 days
1383% · 4,466 predictions · 15 days
1483% · 5,514 predictions · 15 days
1583% · 6,321 predictions · 15 days
1674% · 6,982 predictions · 15 days
1779% · 6,140 predictions · 15 days
1883% · 5,038 predictions · 15 days
1983% · 4,273 predictions · 15 days
2087% · 4,220 predictions · 15 days
2183% · 3,758 predictions · 15 days
2284% · 3,614 predictions · 15 days
2391% · 2,564 predictions · 15 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?

22 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: 3,053 of 139,371 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

1% of pairs (2,071) 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
Madaling-araw (4 hanggang 6 a.m.)	1,504	0% (0)	0% (0)
Rush hour sa umaga (6 hanggang 9 a.m.)	23,848	2% (551)	1% (354)
Tanghali (9 a.m. hanggang 3 p.m.)	42,703	1% (569)	1% (396)
Rush hour sa hapon (3 hanggang 6 p.m.)	30,115	5% (1,448)	3% (1,003)
Gabi (6 hanggang 10 p.m.)	27,501	2% (457)	1% (273)
Gabi (10 p.m. hanggang 4 a.m.)	13,700	0% (28)	0% (45)

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 1A to WAJASHK / ALGONQUIN COLLEGE RESIDENCE, 8.3 km/h actual against 8 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 1A	WAJASHK / ALGONQUIN COLLEGE RESIDENCE	700 m	8 km/h	8.3 km/h	1,079	3%
QUEENSWAY CARLETON / EMERGENCY	BAYSHORE B	1.4 km	7.4 km/h	8.9 km/h	24	0%
WAJASHK / ALGONQUIN COLLEGE RESIDENCE	BASELINE 2A	640 m	10.9 km/h	9.4 km/h	876	13%
BASELINE 1A	1305 BASELINE	3 km	16.3 km/h	14.4 km/h	87	5%
BASELINE / MERIVALE	WAJASHK / ALGONQUIN COLLEGE RESIDENCE	2.7 km	14.4 km/h	15.3 km/h	1,066	0%
BASELINE / MERIVALE	BASELINE 2A	3.2 km	16.4 km/h	15.6 km/h	541	1%
WAJASHK / ALGONQUIN COLLEGE RESIDENCE	BASELINE / MERIVALE	2.8 km	16.5 km/h	16 km/h	798	1%
BASELINE 1A	BASELINE / MERIVALE	3.3 km	18.3 km/h	16.3 km/h	570	2%

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.

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

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

Mga oras na may pinakamaraming kanseladong biyahe: 3 PM (4), 11 AM (2), 5 PM (2)

Mga pinakabagong kinanselang biyahe

Mar, Nob 3, scheduled 09:42
Lin, Nob 1, scheduled 15:17
Miy, Okt 28, scheduled 17:36
Miy, Okt 28, scheduled 07:10
Sab, Okt 24, scheduled 21:47

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: 7 of 1,043 trips we could check.

Buksan ang may petsang pagsusuri ng hula

Hatol

What this route needs

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

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 22 hours with samples

00:00: 89% of final predictions within five minutes of the timetable, 2,168 predictions, typically 1.5 min late
01:00: 88.1% of final predictions within five minutes of the timetable, 815 predictions, typically 0.1 min early
02:00: not enough data
03:00: not enough data
04:00: 95.3% of final predictions within five minutes of the timetable, 1,323 predictions, typically 0.1 min early
05:00: 85.2% of final predictions within five minutes of the timetable, 2,142 predictions, typically 2.3 min late
06:00: 90.4% of final predictions within five minutes of the timetable, 4,534 predictions, typically 2.1 min late
07:00: 87.2% of final predictions within five minutes of the timetable, 6,711 predictions, typically 1.5 min late
08:00: 79.5% of final predictions within five minutes of the timetable, 5,628 predictions, typically 2 min late
09:00: 81.8% of final predictions within five minutes of the timetable, 4,499 predictions, typically 1.4 min late
10:00: 83.4% of final predictions within five minutes of the timetable, 4,283 predictions, typically 1.4 min late
11:00: 92.1% of final predictions within five minutes of the timetable, 4,429 predictions, typically 1 min late
12:00: 81.7% of final predictions within five minutes of the timetable, 4,478 predictions, typically 1.8 min late
13:00: 82.6% of final predictions within five minutes of the timetable, 4,466 predictions, typically 1.3 min late
14:00: 83.3% of final predictions within five minutes of the timetable, 5,514 predictions, typically 1.2 min late
15:00: 83% of final predictions within five minutes of the timetable, 6,321 predictions, typically 0.9 min late
16:00: 74.2% of final predictions within five minutes of the timetable, 6,982 predictions, typically 1.8 min late
17:00: 78.5% of final predictions within five minutes of the timetable, 6,140 predictions, typically 1.4 min late
18:00: 82.9% of final predictions within five minutes of the timetable, 5,038 predictions, typically 1 min late
19:00: 82.5% of final predictions within five minutes of the timetable, 4,273 predictions, typically 1.2 min late
20:00: 87% of final predictions within five minutes of the timetable, 4,220 predictions, typically 1.1 min late
21:00: 82.6% of final predictions within five minutes of the timetable, 3,758 predictions, typically 1.5 min late
22:00: 83.7% of final predictions within five minutes of the timetable, 3,614 predictions, typically 1.9 min late
23:00: 90.6% of final predictions within five minutes of the timetable, 2,564 predictions, typically 1.4 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
CaveatCoverage gap	All measured hours	99%	More observation, not a service change

Measurements

Coverage gap · All measured hours: Target 99.5%; Trips with a matching position 99.2%; Mga araw ng serbisyo 6; Trips with a matching position 1,035; Mga biyaheng nakatakda sa iskedyul 1,043

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

How route 88 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 provider sa sample na may petsang ito.

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

Laki ng sample ng prediksyon: Mas malaking sample

Based on 164,119 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.

Wala pang paulit-ulit na panahon ng pagkakaiba ng prediksyon na umabot sa threshold ng ebidensya.

1 current notice affects this route

• Stop impacts: #4036 -- Holly Acres (south-side) / Ramp temporary relocation

Pagkakaiba ng hula ayon sa hintuan

HOLLY ACRES / RAMP
40 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,606 predictions over 29 days).
Buksan ang hintuang ito
LYCÉE CLAUDEL 2A (A)
37 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,002 predictions over 29 days).
Buksan ang hintuang ito
HOLLY ACRES / RICHMOND
34 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,645 predictions over 29 days).
Buksan ang hintuang ito
BASELINE / HIGHGATE
34 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,680 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?: 8 of 1,043 checked trips need a closer look8 of 1,043 trips with enough public-feed evidence had no matching position over 7 days. 0 of 1,043 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.7 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?: 6.6 min average predicted wait1.1 min beyond the scheduled wait, based on 29,891 eligible predictions at 93 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: 167
Mga natatanging hintuan na nasa iskedyul: 141
Iba't ibang inilathalang daanan: 10
Inilathalang oras ng serbisyo: 04:16–01:43 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: 167
Mga natatanging hintuan na nasa iskedyul: 141
Iba't ibang inilathalang daanan: 10
Inilathalang oras ng serbisyo: 04:16–01:43 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 87,332 arrivals over 14 days; after has 36,691 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.2%
Mga karapat-dapat na hula na nasuri: 164,119
Mga araw ng linggo na may datos: 19
Tinatayang pagkaantala sa ika-95 na percentile: 8.7 min late

Patterns by hour (22)

Patterns by hour (22)
Oras	Nasa oras	Median	95th percentile	Ebidensya
00:00	89.0%	1.5 min late	6.2 min late	2,168 · 14 days
01:00	88.1%	0.1 min early	6.4 min late	815 · 12 days
04:00	95.3%	0.1 min early	3.7 min late	1,323 · 11 days
05:00	85.2%	2.3 min late	6.4 min late	2,142 · 15 days
06:00	90.4%	2.1 min late	6.1 min late	4,534 · 15 days
07:00	87.2%	1.5 min late	6.6 min late	6,711 · 15 days
08:00	79.5%	2 min late	8.5 min late	5,628 · 15 days
09:00	81.8%	1.4 min late	9.7 min late	4,499 · 15 days
10:00	83.4%	1.4 min late	8.8 min late	4,283 · 15 days
11:00	92.1%	1 min late	5.6 min late	4,429 · 15 days
12:00	81.7%	1.8 min late	7.6 min late	4,478 · 15 days
13:00	82.6%	1.3 min late	8.2 min late	4,466 · 15 days
14:00	83.3%	1.2 min late	8.4 min late	5,514 · 15 days
15:00	83.0%	0.9 min late	9.9 min late	6,321 · 15 days
16:00	74.2%	1.8 min late	12.3 min late	6,982 · 15 days
17:00	78.5%	1.4 min late	11.1 min late	6,140 · 15 days
18:00	82.9%	1 min late	9.2 min late	5,038 · 15 days
19:00	82.5%	1.2 min late	8.7 min late	4,273 · 15 days
20:00	87.0%	1.1 min late	8.6 min late	4,220 · 15 days
21:00	82.6%	1.5 min late	8.7 min late	3,758 · 15 days
22:00	83.7%	1.9 min late	8.5 min late	3,614 · 15 days
23:00	90.6%	1.4 min late	6.2 min late	2,564 · 15 days

Wala pang natatag na paulit-ulit na pattern na mas mababa sa 70% sa hindi bababa sa tatlong araw ng serbisyo.

Nakaiskedyul na bus, ngunit hindi naobserbahan sa real-time

1,035 / 1,043 scheduled trips published at least one position across 6 service days (99.2%).

20:002 / 50 trips without a position96.0%
22:001 / 33 trips without a position97.0%
15:002 / 84 trips without a position97.6%
18:001 / 47 trips without a position97.9%
17:001 / 53 trips without a position98.1%
16:001 / 69 trips without a position98.6%

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 · 167 trips in the retained timetable · retained notices; capture coverage unverified

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

04:16– 04:59
Trip 21559040Vehicle position matchedFirst / last feed position: 4:08 a.m. EST / 4:54 a.m. EST; not actual start or end times.
04:18– 04:58
Trip 10612040Vehicle position matchedFirst / last feed position: 4:06 a.m. EST / 4:54 a.m. EST; not actual start or end times.
04:46– 05:29
Trip 26063040Vehicle position matchedFirst / last feed position: 4:33 a.m. EST / 5:27 a.m. EST; not actual start or end times.
04:52– 05:32
Trip 34807040Vehicle position matchedFirst / last feed position: 4:40 a.m. EST / 5:38 a.m. EST; not actual start or end times.
05:16– 06:02
Trip 32579040Vehicle position matchedFirst / last feed position: 5:02 a.m. EST / 6:14 a.m. EST; not actual start or end times.
05:22– 06:05
Trip 13578040Vehicle position matchedFirst / last feed position: 5:10 a.m. EST / 6:10 a.m. EST; not actual start or end times.
05:46– 06:34
Trip 24980040Vehicle position matchedFirst / last feed position: 5:30 a.m. EST / 6:39 a.m. EST; not actual start or end times.
05:50– 06:37
Trip 24573040Vehicle position matchedFirst / last feed position: 5:39 a.m. EST / 6:56 a.m. EST; not actual start or end times.
06:01– 06:52
Trip 14976040Vehicle position matchedFirst / last feed position: 5:48 a.m. EST / 6:58 a.m. EST; not actual start or end times.
06:05– 06:54
Trip 11519040Vehicle position matchedFirst / last feed position: 5:37 a.m. EST / 6:57 a.m. EST; not actual start or end times.
06:15– 07:06
Trip 25761040Vehicle position matchedFirst / last feed position: 6:06 a.m. EST / 7:09 a.m. EST; not actual start or end times.
06:20– 07:11
Trip 17325040Vehicle position matchedFirst / last feed position: 6:15 a.m. EST / 7:14 a.m. EST; not actual start or end times.

· Open all evidence for this day