No 222 trips cancelled now · 0 did not run in NovemberCancellations →

Route 222: Blair ⇄ Vars

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 28, 2026 – Nov 3, 2026

Scheduled trips with cancellation notices

—

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

Trips needing investigation

0 of 30 trips with a usable feed window (0%) had no matching position.

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

30 with position · 0 to investigate · 0 excluded · 30 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 4, 2026, 11:06 p.m..

Coverage, exclusions and sources

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

Published position coverage: 30 / 30 (100%). 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: Nov 4, 2026, 9:49 p.m.

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

No comparable percentage published

This service purpose needs a different method. A general percentage could give a misleading picture.

Predictions in the source: 2,967
Weekdays with evidence: 18
Evidence window: Oct 6, 2026 – Nov 3, 2026

These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.

Calculated: Nov 5, 2026

2 partial-capture days not counted.

What about time of day?

The general hourly comparison is not suitable for this service purpose. Source records remain available.

Improvement or decline requires comparable periods. This single result cannot establish a trend.

Explore the dated evidence Source of this result

Buses arriving bunched

Last 28 days, October 7, 2026 to November 3, 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: October 8, 2026, October 15, 2026.

Values and interpretation

No bunched buses were measured on this route in the last 28 days (447 pairs checked at stops).

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

Buses arriving bunched
Time of day	Pairs checked	Bunched	Long gap
Morning rush (6 to 9 a.m.)	447	0% (0)	0% (0)

How this is measured →How we got this numberBunching and slow spots on every route →

Where this route is slowest

Slowest: BLAIR A to PIPERVILLE / CARLSBAD SPRINGS COMMUNITY CENTRE, 43 km/h actual against 40.9 km/h planned.

Where this route is slowest
From	To	Distance	Planned speed	Actual speed	Trips measured	Slow trips
BLAIR A	PIPERVILLE / CARLSBAD SPRINGS COMMUNITY CENTRE	18.4 km	40.9 km/h	43 km/h	50	0%
ROCKDALE / RUSSELL	VARS PARK AND RIDE	5.1 km	38.6 km/h	48.3 km/h	50	0%
VARS PARK AND RIDE	PIPERVILLE / CARLSBAD SPRINGS COMMUNITY CENTRE	10.8 km	49.7 km/h	51.3 km/h	50	0%
PIPERVILLE / CARLSBAD SPRINGS COMMUNITY CENTRE	VARS PARK AND RIDE	10.8 km	54 km/h	62.1 km/h	50	0%

A slow trip took at least 1.5 times the planned time.

How this is measured →

Cancellations on this route

What these words mean →

2 partial-capture days not counted.

No counted cancellations on this route in the last four weeks. Notices we could not check would be listed below.

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

Open the dated prediction analysis

Verdict

What this route needs

Provider predictions are about 1.8 min earlier than the timetable, 17:00.

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

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

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: 100% of final predictions within five minutes of the timetable, 80 predictions, typically 1.7 min late
06:00: 97.9% of final predictions within five minutes of the timetable, 514 predictions, typically 0.8 min early
07:00: 93.1% of final predictions within five minutes of the timetable, 218 predictions, typically 0.1 min early
08:00: not enough data
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: not enough data
16:00: 93% of final predictions within five minutes of the timetable, 330 predictions, typically 0.9 min late
17:00: 95% of final predictions within five minutes of the timetable, 280 predictions, typically 1.8 min early
18:00: 81.7% of final predictions within five minutes of the timetable, 230 predictions, typically 0.4 min early
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	When	Measured	Scenario or next investigation
StrengthPredictions consistently close to timetable	05:00, 06:00, 07:00, 16:00, 17:00, 18:00	94%	Keep what works
ProblemPredictions earlier than timetable	17:00	1.8 min early	Less running time, or holding points
StrengthObserved-position lower bound	All measured hours	100%	Keep what works

Measurements

Predictions consistently close to timetable · 05:00, 06:00, 07:00, 16:00, 17:00, 18:00: Measured arrivals 1,652; Hours measured 6; Worst hour on time 81.7%; Median hour on time 94.1%
Predictions earlier than timetable · 17:00: Measured arrivals 280; Hours affected 1; Spread 6.3 min; Median delay -1.8 min; Suggested running time change -1.8 min
Observed-position lower bound · All measured hours: Target 99.5%; Trips with a matching position 100%; Service days 5; Trips with a matching position 30; Scheduled trips 30

Open history, reliability and route analysis

Route check

How route 222 has been running

A short summary of what we know. We say so when we cannot answer a question.

Bottom line

We need to know where this express route picks people up before we can rate it.

Prediction sample size: Larger sample

Based on 2,967 eligible provider predictions over 18 measured days, from Oct 6, 2026 to Nov 3, 2026.

Updated Nov 4, 2026, 10:32 p.m.

Where and when did predictions differ repeatedly?

These are repeated prediction-to-timetable differences, not independently measured service failures. They use the same eligible predictions as the result above, but group by stop rather than hour, so the lists need not match line for line.

Problem times are not ranked because this service needs a purpose-specific test.

No current official notice matches this route.

Prediction differences by stop

We do not yet have enough route-by-stop history to name a recurring problem stop. Rider reports are used as leads, not proof.

Check every trip and date

Open a time period to see each service day, scheduled trip, feed gap, observed public vehicle ID, and the exact counts behind this summary.

What riders want to know

Is any trip cancelled right now?: No live cancellation answerOC 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.
Possible no-shows after checking feed gaps?: 0 of 30 checked trips need a closer look0 of 30 trips with enough public-feed evidence had no matching position over 7 days. 0 of 30 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
How did provider predictions differ from the timetable?: Not enough evidence yet
What wait did provider predictions imply?: No route-level result meets the evidence threshold yet. This does not mean gaps did not happen.

Schedule change check

Published schedule: before and after

This compares the current retained official schedule with the prior retained version. Schedule changes are facts about what was planned; they do not prove that a trip ran.

Current published schedule began October 30, 2026

Selected service day from each published schedule

We check the first Monday after the new schedule began and the Monday one week earlier. Every figure comes from the retained official GTFS versions named below.

At least one selected date uses added or removed calendar-date service. Treat this as holiday or special-service context, not ordinary weekday growth.

Before

Service date checked: October 26, 2026

Scheduled trips: 6
Distinct scheduled stops: 57
Distinct published paths: 2
Published service span: 5:55 a.m.–6:27 p.m.

Operator calendar-date records: 0 added · 2 removed

Feed fingerprint: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

New schedule

Service date checked: November 2, 2026

Scheduled trips: 6
Distinct scheduled stops: 57
Distinct published paths: 2
Published service span: 5:55 a.m.–6:27 p.m.

Operator calendar-date records: 0 added · 2 removed

Feed fingerprint: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

Did service improve after the change?

We will compare settled arrivals for the 14 days before and after the change. We publish the comparison only after both sides have at least 7 service days and 200 arrivals.

Ordinary on-time scoring does not fit this route’s service purpose. The schedule counts remain visible, but the result waits for the purpose-specific evidence described below.

Checksums let anyone verify which retained timetable produced the counts. A changed count does not identify a cause, cancellation, operator decision, or passenger impact.

How this route is judged: Express / commuter route

Inbound performance must be checked at pickup points. Early outbound running after pickups are finished is not treated like early service on a regular route.

Route 222 has a park-and-ride dwell hypothesis to check. A long stop is not called a failure or intentional without operating evidence.

What this data cannot prove

The public feed does not provide dependable passenger counts or passed-up-rider events. A missing position does not by itself prove a cancellation, no-show, short turn or cause.

See the definitions, thresholds and evidence order

Official current feed: explicit cancellations, skipped stops and active notices.
Matched observations: vehicle positions and settled predictions tied to the official schedule.
Official timetable: what was planned, kept separate from what was observed.
Rider and operator reports: leads about routes, times and places to investigate, not numeric proof by themselves.

Provisional results, published evidence

Data behind this result

An ordinary on-time grade is not appropriate for this service without checking its purpose. The route check above explains the pickup, community-service or event evidence needed. You can still inspect the recorded trips and data gaps below.

Evidence window: October 6, 2026 to November 3, 2026

Eligible predictions checked: 2,967
Weekdays with data: 18

Scheduled bus, but not observed in realtime

30 / 30 scheduled trips published at least one position across 5 service days (100.0%).

05:000 / 5 trips without a position100.0%
06:000 / 10 trips without a position100.0%
16:000 / 10 trips without a position100.0%
17:000 / 5 trips without a position100.0%

This is not a confirmed no-show. A missing position can mean a cancelled or missed bus, but it can also mean an unassigned trip ID or an operator-feed gap. Otranspo publishes the gap because it matters to riders while keeping the conclusion honest.

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. Sources and limitations.

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 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

November 3, 2026 · 6 trips in the retained timetable · retained notices; capture coverage unverified

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

05:55– 06:41
Trip 1757030Vehicle position matchedFirst / last feed position: 5:24 a.m. EST / 6:38 a.m. EST; not actual start or end times.
06:28– 07:14
Trip 2770030Vehicle position matchedFirst / last feed position: 6:00 a.m. EST / 7:08 a.m. EST; not actual start or end times.
06:56– 07:42
Trip 2249030Vehicle position matchedFirst / last feed position: 6:25 a.m. EST / 7:39 a.m. EST; not actual start or end times.
16:07– 16:54
Trip 15033030Vehicle position matchedFirst / last feed position: 3:37 p.m. EST / 4:51 p.m. EST; not actual start or end times.
16:40– 17:27
Trip 29091030Vehicle position matchedFirst / last feed position: 4:17 p.m. EST / 5:22 p.m. EST; not actual start or end times.
17:40– 18:27
Trip 8537030Vehicle position matchedFirst / last feed position: 5:50 p.m. EST / 6:34 p.m. EST; not actual start or end times.