This page compares independently calculated service metrics with the monthly figures published on AC Transit's Key Performance Indicators site. Percentages are recomputed from raw counts at every rollup; route percentages are never averaged equally.
Service Operated: following AC Transit's published formula, a planned GTFS trip counts as operated when at least one vehicle probe identified that trip. A trip that did not reach its last passenger-boarding stop still counts as operated and is tracked separately as partial.
On-Time Performance:
AC Transit defines on time as
departing a timepoint no more than one minute early and no more than five minutes late. Each interior, pickup-eligible GTFS
timepoint=1 counts once. This project detects stop arrivals rather than departures, so it uses
the detected arrival versus the scheduled arrival as a proxy and excludes origins and final terminals.
A timepoint passes when its delay is inclusively between −60 and +300 seconds. Missing observations on an
operated trip count as failures; the all-scheduled version also counts every timepoint on an unobserved trip
as a failure. This proxy is deliberately labeled because it is not the same underlying CAD/AVL measurement
used by AC Transit.
Operated planned trips divided by all planned trips. Select a month to see count-weighted weekly segments and the share of operated trips that were partial.
| Month | Our Service Operated | AC Transit reported | Expand |
|---|
The operated-service denominator includes timepoints on trips we observed. The all-scheduled denominator additionally treats timepoints on ghosted trips as failures.
| Month | Our OTP — operated trips | Our OTP — all scheduled | AC Transit reported | Expand |
|---|