Toronto Public Transit Service Pulse
Question 1 of 4 · Regularity

How regularly is service arriving?

On frequent routes, riders benefit when vehicles arrive at reasonably even intervals. Our current approach measures distance between vehicles on monitored routes while we build the stop-level history needed to estimate passenger waits.

Available now: early spacing evidence

Largest mapped gaps can flag routes worth examining. They are not yet stop-level headways, bunching rates or passenger wait times.

Passenger waiting and reliability framework

The measure should match how people use the service.

A frequent route and an infrequent route create different expectations. We keep their reliability questions separate instead of forcing both into one score.

See the TfL reference framework ↗
Frequent service

How much additional waiting does irregular service create?

When people normally arrive without consulting a timetable, even spacing matters more than a single scheduled minute.

Planned measures
Scheduled wait, actual wait, Excess Wait Time and the chance of a short or long wait.
Available today
Early mapped-spacing evidence only.
Scheduled service

Did the service appear when the timetable said it would?

When service is less frequent, leaving early, arriving late or not appearing can have a larger consequence.

Planned measures
On-time, early, late and non-arrival rates at consistent timing points.
Available today
Published schedules, without a validated operational adherence result.
Monitored routes

What vehicle spacing looks like now

These are mapped distances between reported vehicles, not final reliability scores or passenger wait times.

Loading spacing evidence...

Publication path

Build the passenger measure before publishing the result.

1Available now

Spacing screen

Use recent vehicle positions to identify route observations worth examining more closely.

2Building history

Stop passage record

Store direction-specific observations at consistent stops or timing points and measure data coverage.

3Needs validation

Passenger waiting and schedule adherence

Compare calculated results with known outcomes, publish missingness and suppress results when coverage is weak.