No 163 trips cancelled now · 2 did not run in novembreCancellations →

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

Linea 163: Terry Fox ⇄ Kittiwake

Ogni 30-32 min

Direzione Terry Fox2 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: 27 ott 2026 – 2 nov 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: 4 trips with qualifying later matching vehicle observations. Trips with any notice: 5.

Trips needing investigation

2 of 409 trips with a usable feed window (0,5%) had no matching position.

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

407 with position · 2 to investigate · 0 excluded · 409 scheduled trips

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

Coverage, exclusions and sources

0 of 11 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: 407 / 409 (99,5%). 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: 3 nov 2026, 18:17

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

77,6%

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

Predictions in the source: 57.205
Weekdays with evidence: 19
Evidence window: 5 ott 2026 – 2 nov 2026

The hours we have evidence for

691% · 1435 predictions · 13 days
773% · 1777 predictions · 14 days
879% · 1908 predictions · 14 days
982% · 2149 predictions · 14 days
1081% · 2070 predictions · 14 days
1178% · 2032 predictions · 14 days
1280% · 2071 predictions · 14 days
1376% · 2032 predictions · 14 days
1460% · 2035 predictions · 14 days
1570% · 2006 predictions · 14 days
1673% · 2019 predictions · 14 days
1767% · 1854 predictions · 14 days
1882% · 1798 predictions · 14 days
1986% · 1792 predictions · 14 days
2080% · 1273 predictions · 12 days
2196% · 897 predictions · 12 days
2290% · 791 predictions · 12 days
23100% · 40 predictions · 8 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: 3 nov 2026

2 partial-capture days not counted.

What about time of day?

18 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

Autobus che arrivano ravvicinati

Last 28 days, 6 ottobre 2026 to 2 novembre 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: 8 ottobre 2026, 15 ottobre 2026.

Valori e interpretazione

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

0% of pairs (55) had a long gap: more than 1.75 times the planned wait between them.

Autobus che arrivano ravvicinati
Ora del giorno	Coppie verificate	Corse ravvicinate	Lungo intervallo
Ora di punta del mattino (dalle 6 alle 9)	3335	0% (3)	0% (1)
Metà giornata (dalle 9 del mattino alle 3 del pomeriggio)	18.287	0% (19)	0% (23)
Ora di punta pomeridiana (dalle 3 alle 6 del pomeriggio)	8786	0% (22)	0% (31)
Sera (dalle 6 alle 10 di sera)	6503	0% (1)	0% (0)

Come viene misurato →How we got this numberBus ravvicinati e punti lenti su ogni linea →

Dove questa linea è più lenta

Slowest: KITTIWAKE / SUNDEW to STITTSVILLE MAIN / CARP, 17,6 km/h actual against 21,6 km/h planned.

Dove questa linea è più lenta
Da	A	Distanza	Velocità prevista	Velocità effettiva	Corse misurate	Corse lente
KITTIWAKE / SUNDEW	STITTSVILLE MAIN / CARP	1,6 km	21,6 km/h	17,6 km/h	741	20%
STITTSVILLE MAIN / CARP	KITTIWAKE / ABACA	1,7 km	29,3 km/h	19,7 km/h	718	45%
TERRY FOX 3C	CASTLEFRANK / MACNEIL	2,2 km	22 km/h	20,8 km/h	639	6%
STITTSVILLE MAIN / CARP	ABBOTT / GRANITE RIDGE	2,8 km	28,1 km/h	24,9 km/h	734	16%
CASTLEFRANK / MACNEIL	ABBOTT / GRANITE RIDGE	4,6 km	27,9 km/h	25 km/h	718	1%
ABBOTT / GRANITE RIDGE	CASTLEFRANK / MACNEIL	4,7 km	26,5 km/h	25,8 km/h	642	1%
HAZELDEAN / CARP	KITTIWAKE / SUNDEW	1,1 km	39,5 km/h	27,3 km/h	683	46%
ABBOTT / GRANITE RIDGE	STITTSVILLE MAIN / CARP	2,8 km	28,9 km/h	27,6 km/h	719	1%

Un viaggio lento ha richiesto almeno 1.5 volte il tempo previsto.

Come viene misurato →

Cancellazioni su questa linea

Che cosa significano queste parole →

2 partial-capture days not counted.

3 scheduled trips with counted cancellation notices from mar 6 ott to lun 2 nov.

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

Ore con più cancellazioni: 7 (1), 8 (1), 17 (1)

Ultime corse cancellate

lun 2 nov, scheduled 07:00
ven 16 ott, scheduled 17:11
mer 14 ott, scheduled 08:31

OC Transpo non indica un motivo per le singole corse, quindi non ne viene mostrato nessuno.

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

Aprire l'analisi datata delle previsioni

Verdetto

What this route needs

Median provider predictions are 3,6 to 3,9 min later than the timetable in 2 hours of the day.

Predictions near the start are about 2,9 min later than the timetable, with a similar difference near the end. This does not establish the cause.

14:00 has 60% of predictions within five minutes of the timetable, against 80% the rest of the day.

Matched public positions cover 100% of scheduled trips. This is a lower bound on operated service, not an audited delivery result.

Next investigation: test terminal recovery and the preceding trip against operational records. Predictions alone do not establish the cause.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 18 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: 90,5% of final predictions within five minutes of the timetable, 1435 predictions, typically 1,7 min late
07:00: 72,9% of final predictions within five minutes of the timetable, 1777 predictions, typically 2,7 min late
08:00: 79,1% of final predictions within five minutes of the timetable, 1908 predictions, typically 1,7 min late
09:00: 82,3% of final predictions within five minutes of the timetable, 2149 predictions, typically 2 min late
10:00: 81,3% of final predictions within five minutes of the timetable, 2070 predictions, typically 2 min late
11:00: 77,9% of final predictions within five minutes of the timetable, 2032 predictions, typically 2,4 min late
12:00: 79,8% of final predictions within five minutes of the timetable, 2071 predictions, typically 1,5 min late
13:00: 76,3% of final predictions within five minutes of the timetable, 2032 predictions, typically 2 min late
14:00: 59,7% of final predictions within five minutes of the timetable, 2035 predictions, typically 3,9 min late
15:00: 69,8% of final predictions within five minutes of the timetable, 2006 predictions, typically 2,8 min late
16:00: 72,7% of final predictions within five minutes of the timetable, 2019 predictions, typically 2,9 min late
17:00: 66,5% of final predictions within five minutes of the timetable, 1854 predictions, typically 3,6 min late
18:00: 81,6% of final predictions within five minutes of the timetable, 1798 predictions, typically 1,2 min late
19:00: 86,2% of final predictions within five minutes of the timetable, 1792 predictions, typically 1,4 min late
20:00: 80,3% of final predictions within five minutes of the timetable, 1273 predictions, typically 1,9 min late
21:00: 95,5% of final predictions within five minutes of the timetable, 897 predictions, typically 1,3 min late
22:00: 90,3% of final predictions within five minutes of the timetable, 791 predictions, typically 1,7 min late
23:00: 100% of final predictions within five minutes of the timetable, 40 predictions, typically 0,6 min early

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	Quando	Misurato	Scenario or next investigation
ProblemPredictions later than timetable	14:00 · 17:00	3,9 min late · 3,6 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	14:00	60%	Operations, not the timetable
StrengthObserved-position lower bound	All measured hours	100%	Keep what works

Measurements

Predictions later than timetable · 14:00: Measured arrivals 2035; Hours affected 1; Spread 10,8 min; Median delay 3,9 min; Suggested running time change 3,9 min
Predictions later than timetable · 17:00: Measured arrivals 1854; Hours affected 1; Spread 15,3 min; Median delay 3,6 min; Suggested running time change 3,6 min
One hour has a lower prediction match · 14:00: Ora 14:00; In orario 59,7%; Measured arrivals 2035; Shortfall 20,3 pts; Route median on time 80,1%
Observed-position lower bound · All measured hours: Obiettivo 99,5%; Trips with a matching position 99,5%; Giorni di servizio 6; Trips with a matching position 407; Corse programmate 409

Aprire storico, affidabilità e analisi della linea

Verifica della linea

How route 163 has been running

Un breve riepilogo di ciò che sappiamo. Lo diciamo quando non possiamo rispondere a una domanda.

In sintesi

Le previsioni del fornitore sono spesso risultate diverse dall'orario; gli arrivi effettivi non sono stati misurati in modo indipendente.

78 in 100 eligible predictions were within 5 minutes of the timetable · 57.205 predictions checked

Dimensione del campione delle previsioni: Campione più ampio

Based on 57.205 eligible provider predictions over 27 measured days, from 5 ott 2026 to 2 nov 2026.

Updated 3 nov 2026, 18:32

Dove e quando le previsioni sono state diverse più volte?

Sono differenze ripetute tra previsione e orario, non disservizi misurati in modo indipendente. Usano le stesse previsioni idonee del risultato qui sopra, ma sono raggruppate per fermata anziché per ora, quindi gli elenchi possono non coincidere riga per riga.

14–15: 40 in 100 eligible predictions differed from the timetable by more than 5 minutes (2035 predictions over 14 days).
17–18: 34 in 100 eligible predictions differed from the timetable by more than 5 minutes (1854 predictions over 14 days).
15–16: 30 in 100 eligible predictions differed from the timetable by more than 5 minutes (2006 predictions over 14 days).

Nessun avviso ufficiale attuale riguarda questa ligne.

Differenze di previsione per fermata

KITTIWAKE / ABACA
34 in 100 eligible predictions differed from the timetable by more than 5 minutes (1682 predictions over 30 days).
Aprire questa fermata
ABBOTT / ROBERT GRANT
33 in 100 eligible predictions differed from the timetable by more than 5 minutes (844 predictions over 30 days).
Aprire questa fermata
ABBOTT / TALLTREE
32 in 100 eligible predictions differed from the timetable by more than 5 minutes (846 predictions over 30 days).
Aprire questa fermata
HAZELDEAN / CARP
32 in 100 eligible predictions differed from the timetable by more than 5 minutes (854 predictions over 30 days).
Aprire questa fermata

Sono previsioni del fornitore specifiche per la linea, confrontate con l'orario. Mostrano differenze di previsione ripetute in un luogo e a un'ora precisi. Non sono arrivi misurati e non ne indicano la causa.

Controlli ogni corsa e ogni data

Apra un periodo per vedere ogni giorno di servizio, ogni corsa programmata, ogni lacuna nei dati, l'ID del veicolo pubblico osservato e i conteggi esatti alla base di questo riepilogo.

Cosa vogliono sapere i passeggeri

Qualche corsa è cancellata in questo momento?: 0 of 11Vengono controllate le corse che partono dai capolinea della linea nelle prossime 4 ore. Non è un tasso storico di cancellazioni.
Possibili corse saltate dopo il controllo delle lacune del feed?: 2 of 409 checked trips need a closer look2 of 409 trips with enough public-feed evidence had no matching position over 7 days. 0 of 409 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
Come sono differite le previsioni dell'operatore rispetto all'orario?: At the 95th percentile, the predicted difference was 15,8 min (positive means later; negative means earlier)78 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
Quale attesa implicavano le previsioni del fornitore?: Nessun risultato per singola ligne raggiunge ancora la soglia dei dati probanti. Ciò non significa che le interruzioni non siano avvenute.

Verifica della modifica dell'orario

Orario pubblicato: prima e dopo

Questo confronto riguarda l'orario ufficiale conservato attualmente e la versione conservata in precedenza. Le modifiche dell'orario sono fatti su ciò che era stato pianificato. Non provano che una corsa sia stata effettuata.

Current published schedule began 30 ottobre 2026

Giorno di servizio selezionato da ciascun orario pubblicato

Controlliamo il primo lunedì dopo l'inizio del nuovo orario e il lunedì di una settimana prima. Ogni dato proviene dalle versioni GTFS ufficiali conservate indicate qui sotto.

Almeno una data selezionata ha un servizio aggiunto o rimosso nel calendario. Lo consideri un contesto di giorno festivo o di servizio speciale, non una normale crescita dei giorni feriali.

Prima

Data di servizio verificata: 26 ottobre 2026

Corse programmate: 63
Fermate previste all'orario distinte: 73
Percorsi pubblicati distinti: 2
Fascia oraria del servizio pubblicata: 6:00–23:07

Operator calendar-date records: 0 added · 2 removed

Impronta del feed: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

Nuovo orario

Data di servizio verificata: 2 novembre 2026

Corse programmate: 63
Fermate previste all'orario distinte: 73
Percorsi pubblicati distinti: 2
Fascia oraria del servizio pubblicata: 6:00–23:07

Operator calendar-date records: 0 added · 2 removed

Impronta del feed: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

Il servizio è migliorato dopo la modifica?

Confronteremo gli arrivi consolidati nei 14 giorni prima e dopo la modifica. Pubblichiamo il confronto solo quando entrambi i periodi hanno almeno 7 giorni di servizio e 200 arrivi.

Still collecting: before has 30.032 arrivals over 14 days; after has 8092 arrivals over 4 days. No improvement or decline is claimed yet.

I checksum permettono a chiunque di verificare quale orario conservato ha prodotto i conteggi. Una variazione del conteggio non indica una causa, una cancellazione, una decisione dell'esercente o un effetto sui passeggeri.

Come viene valutata questa ligne: Linea regolare con tutte le fermate

Confrontiamo l'ultima previsione idonea del fornitore per ogni arrivo programmato con l'orario ufficiale. Non sono arrivi misurati in modo indipendente. Per un risultato servono almeno 200 previsioni idonee. Qui si usa come obiettivo per i passeggeri "entro 5 minuti".

Che cosa questi dati non possono dimostrare

Il feed pubblico non fornisce conteggi affidabili dei passeggeri né eventi di passeggeri non imbarcati. Una posizione mancante non prova da sola una cancellazione, una mancata corsa, un'inversione anticipata o una causa.

Vedere le definizioni, le soglie e l'ordine dei dati

Feed ufficiale attuale: cancellazioni esplicite, fermate saltate e avvisi attivi.
Osservazioni abbinate: posizioni dei veicoli e previsioni consolidate collegate all'orario ufficiale.
Orario ufficiale: ciò che era previsto, tenuto separato da ciò che è stato osservato.
Segnalazioni di passeggeri e operatori: indizi su linee, orari e luoghi da verificare, non prove numeriche di per sé.

Risultati provvisori, dati probanti pubblicati

Come si sono confrontate le previsioni con l'orario?

Ogni ora confronta l'ultima previsione idonea del fornitore per un arrivo previsto a orario con l'orario ufficiale. «Entro 5 minuti» indica la differenza tra le previsioni, non un arrivo misurato né la prova che un autobus abbia circolato.

Periodo dei dati probatori: 5 ottobre 2026 to 2 novembre 2026

Entro 5 minuti dall'orario: 77,6%
Previsioni idonee verificate: 57.205
Giorni feriali con dati: 19
Ritardo previsto al 95º percentile: 15,8 min late

Patterns by hour (18)

Patterns by hour (18)
Ora	In orario	Mediana	95º percentile	Dati probanti
06:00	90,5%	1,7 min late	8,1 min late	1435 · 13 days
07:00	72,9%	2,7 min late	16,3 min late	1777 · 14 days
08:00	79,1%	1,7 min late	14,7 min late	1908 · 14 days
09:00	82,3%	2 min late	16,5 min late	2149 · 14 days
10:00	81,3%	2 min late	16,6 min late	2070 · 14 days
11:00	77,9%	2,4 min late	14,8 min late	2032 · 14 days
12:00	79,8%	1,5 min late	13,5 min late	2071 · 14 days
13:00	76,3%	2 min late	15,4 min late	2032 · 14 days
14:00	59,7%	3,9 min late	14,7 min late	2035 · 14 days
15:00	69,8%	2,8 min late	18,1 min late	2006 · 14 days
16:00	72,7%	2,9 min late	18,9 min late	2019 · 14 days
17:00	66,5%	3,6 min late	18,9 min late	1854 · 14 days
18:00	81,6%	1,2 min late	15,6 min late	1798 · 14 days
19:00	86,2%	1,4 min late	13,7 min late	1792 · 14 days
20:00	80,3%	1,9 min late	14,5 min late	1273 · 12 days
21:00	95,5%	1,3 min late	3,9 min late	897 · 12 days
22:00	90,3%	1,7 min late	16,5 min late	791 · 12 days
23:00	100,0%	0,6 min early	2,4 min late	40 · 8 days

3 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.

Autobus previsto a orario, ma non osservato in tempo reale

407 / 409 scheduled trips published at least one position across 6 service days (99,5%).

17:001 / 24 trips without a position95,8%
16:001 / 28 trips without a position96,4%
06:000 / 21 trips without a position100,0%
07:000 / 25 trips without a position100,0%
08:000 / 26 trips without a position100,0%
09:000 / 28 trips without a position100,0%

Questa non è una mancata corsa confermata. Una posizione mancante può indicare una corsa soppressa o saltata, ma può anche indicare un ID di corsa non assegnato o un'interruzione nel feed del gestore. Otranspo pubblica questa mancanza perché è importante per chi viaggia, senza trarre conclusioni non verificate.

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. Fonti e limiti.

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

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

06:00– 06:32
Trip 13962020Vehicle position matchedFirst / last feed position: 5:51 a.m. EST / 6:37 a.m. EST; not actual start or end times.
06:00– 06:31
Trip 17662020Vehicle position matchedFirst / last feed position: 5:31 a.m. EST / 6:30 a.m. EST; not actual start or end times.
06:30– 07:02
Trip 12192020Vehicle position matchedFirst / last feed position: 6:13 a.m. EST / 6:59 a.m. EST; not actual start or end times.
06:35– 07:10
Trip 32234020Vehicle position matchedFirst / last feed position: 5:52 a.m. EST / 7:24 a.m. EST; not actual start or end times.
07:00– 07:34
Trip 26015020Explicit notice: CANCELEDVehicle position matchedFirst / last feed position: 6:55 a.m. EST / 10:18 a.m. EST; not actual start or end times.
07:05– 07:40
Trip 27400020Vehicle position matchedFirst / last feed position: 6:22 a.m. EST / 7:58 a.m. EST; not actual start or end times.
07:30– 08:06
Trip 26640020Vehicle position matchedFirst / last feed position: 6:45 a.m. EST / 8:09 a.m. EST; not actual start or end times.
07:36– 08:14
Trip 21593020Vehicle position matchedFirst / last feed position: 6:55 a.m. EST / 8:16 a.m. EST; not actual start or end times.
08:00– 08:33
Trip 17219020Vehicle position matchedFirst / last feed position: 7:59 a.m. EST / 8:26 a.m. EST; not actual start or end times.
08:09– 08:45
Trip 22923020Vehicle position matchedFirst / last feed position: 8:10 a.m. EST / 8:54 a.m. EST; not actual start or end times.
08:31– 09:05
Trip 31726020Vehicle position matchedFirst / last feed position: 8:18 a.m. EST / 10:02 a.m. EST; not actual start or end times.
08:36– 09:09
Trip 5905020Vehicle position matchedFirst / last feed position: 8:28 a.m. EST / 9:28 a.m. EST; not actual start or end times.

· Open all evidence for this day