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

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

Ruta 117: Baseline ⇄ Greenboro

Bawat 28 hanggang 30 min

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

Trips needing investigation

1 of 45 trips with a usable feed window (2.2%) had no matching position.

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

44 with position · 1 to investigate · 0 excluded · 45 scheduled trips

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

Coverage, exclusions and sources

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

Published position coverage: 44 / 45 (97.8%). 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, 10:08 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

82.9%

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

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

The hours we have evidence for

0695% · 448 predictions · 10 days
0789% · 851 predictions · 10 days
0853% · 284 predictions · 10 days
1587% · 245 predictions · 10 days
1678% · 830 predictions · 10 days
1788% · 868 predictions · 10 days
1889% · 120 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?

7 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: 6 of 4,120 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

0% of pairs (6) 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.)	1,352	0% (0)	0% (0)
Rush hour sa hapon (3 hanggang 6 p.m.)	2,576	0% (6)	0% (6)
Gabi (6 hanggang 10 p.m.)	192	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: MACFARLANE / BRIGGS to HUNT CLUB / RIVERSIDE, 15.7 km/h actual against 15.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
MACFARLANE / BRIGGS	HUNT CLUB / RIVERSIDE	3.6 km	15.8 km/h	15.7 km/h	83	0%
HUNT CLUB / RIVERSIDE	MACFARLANE / MERIVALE	3.8 km	22.6 km/h	23.9 km/h	66	3%
BASELINE 1C	VAAN / WOODROFFE	3 km	25.9 km/h	24.5 km/h	72	4%
MACFARLANE / MERIVALE	VAAN / COLEWAY	2.3 km	25 km/h	25.4 km/h	65	5%
VAAN / WOODROFFE	MACFARLANE / BRIGGS	2.6 km	25.5 km/h	26.5 km/h	83	0%
HUNT CLUB / RIVERSIDE	SOUTH KEYS A	4.1 km	27 km/h	28.8 km/h	83	2%
GREENBORO B	HUNT CLUB / RIVERSIDE	4.4 km	36.5 km/h	32.3 km/h	67	7%

Ang mabagal na biyahe ay inabot nang hindi bababa sa 1.5 beses ng planadong oras.

Paano ito sinusukat →

Mga pagkansela sa rutang ito

Ano ang ibig sabihin ng mga salitang ito →

2 partial-capture days not counted.

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

Not counted: 5 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 (1)

Mga pinakabagong kinanselang biyahe

Huw, Okt 22, scheduled 15:40

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 45 trips we could check.

Buksan ang may petsang pagsusuri ng hula

Hatol

What this route needs

Median provider predictions are 4.6 min later than the timetable in 1 hours of the day.

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

Only 98% 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, 7 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: 94.6% of final predictions within five minutes of the timetable, 448 predictions, typically 0 min late
07:00: 88.8% of final predictions within five minutes of the timetable, 851 predictions, typically 2 min late
08:00: 52.5% of final predictions within five minutes of the timetable, 284 predictions, typically 4.6 min late
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: 86.5% of final predictions within five minutes of the timetable, 245 predictions, typically 1.9 min late
16:00: 77.6% of final predictions within five minutes of the timetable, 830 predictions, typically 2.6 min late
17:00: 87.8% of final predictions within five minutes of the timetable, 868 predictions, typically 2.1 min late
18:00: 89.2% of final predictions within five minutes of the timetable, 120 predictions, typically 1.3 min late
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
ProblemPredictions later than timetable	08:00	4.6 min late	More running time
ProblemOne hour has a lower prediction match	08:00	53%	Operations, not the timetable
CaveatCoverage gap	All measured hours	98%	More observation, not a service change

Measurements

Predictions later than timetable · 08:00: Measured arrivals 284; Hours affected 1; Spread 7.4 min; Median delay 4.6 min; Suggested running time change 4.6 min
One hour has a lower prediction match · 08:00: Oras 08:00; Nasa oras 52.5%; Measured arrivals 284; Shortfall 35.3 pts; Route median on time 87.8%
Coverage gap · All measured hours: Target 99.5%; Trips with a matching position 97.8%; Mga araw ng serbisyo 5; Trips with a matching position 44; Mga biyaheng nakatakda sa iskedyul 45

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

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

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

Laki ng sample ng prediksyon: Mas malaking sample

Based on 6,585 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.

08–09: 48 in 100 eligible predictions differed from the timetable by more than 5 minutes (284 predictions over 10 days).

Walang kasalukuyang opisyal na abiso na tumutugma sa rutang ito.

Pagkakaiba ng hula ayon sa hintuan

HUNT CLUB / PRINCE OF WALES
35 in 100 eligible predictions differed from the timetable by more than 5 minutes (79 predictions over 20 days).
Buksan ang hintuang ito
ANTARES / WEST HUNT CLUB
35 in 100 eligible predictions differed from the timetable by more than 5 minutes (79 predictions over 20 days).
Buksan ang hintuang ito
ANTARES / CAPELLA
35 in 100 eligible predictions differed from the timetable by more than 5 minutes (79 predictions over 20 days).
Buksan ang hintuang ito
ANTARES / AURIGA
35 in 100 eligible predictions differed from the timetable by more than 5 minutes (79 predictions over 20 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?: 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?: 1 of 45 checked trips need a closer look1 of 45 trips with enough public-feed evidence had no matching position over 7 days. 0 of 45 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.6 min (positive means later; negative means earlier)83 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
Gaano katagal na paghihintay ang ipinahiwatig ng mga tinatayang oras ng operator?: 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: 9
Mga natatanging hintuan na nasa iskedyul: 85
Iba't ibang inilathalang daanan: 2
Inilathalang oras ng serbisyo: 06:26–18: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: 9
Mga natatanging hintuan na nasa iskedyul: 85
Iba't ibang inilathalang daanan: 2
Inilathalang oras ng serbisyo: 06:26–18: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 3,651 arrivals over 10 days; after has 743 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: 82.9%
Mga karapat-dapat na hula na nasuri: 6,585
Mga araw ng linggo na may datos: 18
Tinatayang pagkaantala sa ika-95 na percentile: 8.6 min late

Patterns by hour (7)

Patterns by hour (7)
Oras	Nasa oras	Median	95th percentile	Ebidensya
06:00	94.6%	0 min late	2.5 min late	448 · 10 days
07:00	88.8%	2 min late	7.8 min late	851 · 10 days
08:00	52.5%	4.6 min late	12 min late	284 · 10 days
15:00	86.5%	1.9 min late	7.5 min late	245 · 10 days
16:00	77.6%	2.6 min late	10 min late	830 · 10 days
17:00	87.8%	2.1 min late	7.1 min late	868 · 10 days
18:00	89.2%	1.3 min late	6.5 min late	120 · 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

44 / 45 scheduled trips published at least one position across 5 service days (97.8%).

06:001 / 10 trips without a position90.0%
07:000 / 10 trips without a position100.0%
15:000 / 5 trips without a position100.0%
16: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 · 9 trips in the retained timetable · retained notices; capture coverage unverified

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

06:26– 06:59
Trip 8281020Vehicle position matchedFirst / last feed position: 6:17 a.m. EST / 6:54 a.m. EST; not actual start or end times.
06:54– 07:29
Trip 32074020Vehicle position matchedFirst / last feed position: 6:23 a.m. EST / 8:08 a.m. EST; not actual start or end times.
07:19– 07:56
Trip 11314020Vehicle position matchedFirst / last feed position: 7:21 a.m. EST / 8:00 a.m. EST; not actual start or end times.
07:50– 08:29
Trip 36854020Vehicle position matchedFirst / last feed position: 7:52 a.m. EST / 8:40 a.m. EST; not actual start or end times.
15:40– 16:24
Trip 16372020Vehicle position matchedFirst / last feed position: 3:30 p.m. EST / 4:23 p.m. EST; not actual start or end times.
16:10– 16:54
Trip 25782020Vehicle position matchedFirst / last feed position: 4:20 p.m. EST / 4:57 p.m. EST; not actual start or end times.
16:40– 17:23
Trip 28337020Vehicle position matchedFirst / last feed position: 4:41 p.m. EST / 5:24 p.m. EST; not actual start or end times.
17:10– 17:51
Trip 18980020Vehicle position matchedFirst / last feed position: 4:51 p.m. EST / 5:54 p.m. EST; not actual start or end times.
17:40– 18:16
Trip 34791020Vehicle position matchedFirst / last feed position: 5:44 p.m. EST / 6:14 p.m. EST; not actual start or end times.