No 84 trips cancelled now · 2 did not run in NobyembreCancellations →

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

Ruta 84: Centrepointe ⇄ Baseline

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

—

No retained notice returned; this does not prove zero cancellations.

Trips needing investigation

2 of 60 trips with a usable feed window (3.3%) had no matching position.

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

58 with position · 2 to investigate · 0 excluded · 60 scheduled trips

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

Coverage, exclusions and sources

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

Published position coverage: 58 / 60 (96.7%). 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, 9:48 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

96.8%

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

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

The hours we have evidence for

06100% · 244 predictions · 11 days
0795% · 224 predictions · 10 days
08100% · 230 predictions · 10 days
15100% · 229 predictions · 10 days
1683% · 230 predictions · 10 days
17100% · 227 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 4, 2026

2 partial-capture days not counted.

What about time of day?

6 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.

Too few buses were measured to judge bunching: 0 pairs checked, 30 needed.

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

Kung saan pinakamabagal ang rutang ito

Not enough trips yet to measure speed between timepoints (20 trips needed for each segment).

Paano ito sinusukat →

Mga pagkansela sa rutang ito

Ano ang ibig sabihin ng mga salitang ito →

2 partial-capture days not counted.

Walang nabilang na kanselasyon sa rutang ito sa nakaraang apat na linggo. Ililista sa ibaba ang mga abisong hindi namin nasuri.

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

Buksan ang may petsang pagsusuri ng hula

Hatol

What this route needs

100% of predictions are within five minutes of the timetable in a typical sampled hour; the lowest sampled hour is 83%.

Only 97% 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, 6 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: 100% of final predictions within five minutes of the timetable, 244 predictions, typically 0.3 min late
07:00: 95.1% of final predictions within five minutes of the timetable, 224 predictions, typically 0.2 min early
08:00: 100% of final predictions within five minutes of the timetable, 230 predictions, typically 0.5 min early
09:00: not enough data
10:00: not enough data
11:00: not enough data
12:00: not enough data
13:00: not enough data
14:00: not enough data
15:00: 100% of final predictions within five minutes of the timetable, 229 predictions, typically 0.7 min late
16:00: 82.6% of final predictions within five minutes of the timetable, 230 predictions, typically 2.4 min late
17:00: 100% of final predictions within five minutes of the timetable, 227 predictions, typically 0.4 min early
18:00: not enough data
19:00: not enough data
20:00: not enough data
21:00: not enough data
22:00: not enough data
23:00: not enough data

90% or more of predictions within five minutes
80 to 90% of predictions within five minutes
under 80% of predictions within five minutes
not enough data

Findings
What	Kailan	Nasukat	Scenario or next investigation
StrengthPredictions consistently close to timetable	06:00, 07:00, 08:00, 15:00, 16:00, 17:00	100%	Keep what works
CaveatCoverage gap	All measured hours	97%	More observation, not a service change

Measurements

Predictions consistently close to timetable · 06:00, 07:00, 08:00, 15:00, 16:00, 17:00: Measured arrivals 1,384; Hours measured 6; Worst hour on time 82.6%; Median hour on time 100%
Coverage gap · All measured hours: Target 99.5%; Trips with a matching position 96.7%; Mga araw ng serbisyo 5; Trips with a matching position 58; Mga biyaheng nakatakda sa iskedyul 60

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

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

97 in 100 eligible predictions were within 5 minutes of the timetable · 2,407 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

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

Updated Nob 3, 2026, 10: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.

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

Walang kasalukuyang opisyal na abiso na tumutugma sa rutang ito.

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?: Walang live na sagot sa kanselasyonOC Transpo’s live trip-update feed did not answer this check. That is a feed gap. It does not mean zero cancellations, and it is not proof of a cancellation. Open the evidence to see the schedule, retained explicit cancellation notices, and every labelled data gap.
Posibleng hindi sumipot matapos suriin ang mga puwang sa feed?: 2 of 60 checked trips need a closer look2 of 60 trips with enough public-feed evidence had no matching position over 7 days. 0 of 60 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 3.9 min (positive means later; negative means earlier)97 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: 12
Mga natatanging hintuan na nasa iskedyul: 24
Iba't ibang inilathalang daanan: 2
Inilathalang oras ng serbisyo: 06:00–17:16

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: 12
Mga natatanging hintuan na nasa iskedyul: 24
Iba't ibang inilathalang daanan: 2
Inilathalang oras ng serbisyo: 06:00–17:16

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 1,362 arrivals over 10 days; after has 272 arrivals over 2 days. No improvement or decline is claimed yet.

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

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

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

Ang hindi mapatutunayan ng datos na ito

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

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

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

Pansamantalang resulta, inilathalang ebidensya

Paano ikinumpara ang mga hula sa iskedyul?

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

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

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

Patterns by hour (6)

Patterns by hour (6)
Oras	Nasa oras	Median	95th percentile	Ebidensya
06:00	100.0%	0.3 min late	1.6 min late	244 · 11 days
07:00	95.1%	0.2 min early	3.5 min late	224 · 10 days
08:00	100.0%	0.5 min early	1.6 min late	230 · 10 days
15:00	100.0%	0.7 min late	2.8 min late	229 · 10 days
16:00	82.6%	2.4 min late	11.2 min late	230 · 10 days
17:00	100.0%	0.4 min early	2.1 min late	227 · 10 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

58 / 60 scheduled trips published at least one position across 5 service days (96.7%).

16:002 / 10 trips without a position80.0%
06:000 / 10 trips without a position100.0%
07:000 / 10 trips without a position100.0%
08:000 / 10 trips without a position100.0%
15:000 / 10 trips without a position100.0%
17:000 / 10 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 · 12 trips in the retained timetable · retained notices; capture coverage unverified

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

06:00– 06:06
Trip 327020Vehicle position matchedFirst / last feed position: 6:01 a.m. EST / 6:06 a.m. EST; not actual start or end times.
06:06– 06:13
Trip 21705020Vehicle position matchedFirst / last feed position: 6:02 a.m. EST / 6:12 a.m. EST; not actual start or end times.
07:00– 07:08
Trip 1927020Vehicle position matchedFirst / last feed position: 7:02 a.m. EST / 7:05 a.m. EST; not actual start or end times.
07:08– 07:17
Trip 7687020Vehicle position matchedFirst / last feed position: 7:06 a.m. EST / 7:12 a.m. EST; not actual start or end times.
08:01– 08:09
Trip 14623020Vehicle position matchedFirst / last feed position: 8:01 a.m. EST / 8:08 a.m. EST; not actual start or end times.
08:09– 08:18
Trip 34702020Vehicle position matchedFirst / last feed position: 8:09 a.m. EST / 8:16 a.m. EST; not actual start or end times.
15:00– 15:08
Trip 15046020Vehicle position matchedFirst / last feed position: 3:02 p.m. EST / 3:07 p.m. EST; not actual start or end times.
15:08– 15:16
Trip 1118020Vehicle position matchedFirst / last feed position: 3:08 p.m. EST / 3:13 p.m. EST; not actual start or end times.
16:00– 16:08
Trip 36011020Vehicle position matchedFirst / last feed position: 4:01 p.m. EST / 4:07 p.m. EST; not actual start or end times.
16:08– 16:16
Trip 16777020Vehicle position matchedFirst / last feed position: 3:34 p.m. EST / 4:12 p.m. EST; not actual start or end times.
17:00– 17:08
Trip 12181020Vehicle position matchedFirst / last feed position: 5:00 p.m. EST / 5:06 p.m. EST; not actual start or end times.
17:08– 17:16
Trip 35519020Vehicle position matchedFirst / last feed position: 5:07 p.m. EST / 5:14 p.m. EST; not actual start or end times.