WECA bus punctuality audit
An independent monitor of bus punctuality across the West of England, built from the operators' own public real-time data.
Track buses live ↗Loading…
Where the delays are
On-time % by where the buses run. Which neighbourhoods get the better service, and which the worse.
Electric fleet
Vehicles by model
How each bus type performs, and the service numbers it runs. Buses are assigned to routes operationally, so treat by-model punctuality as indicative, not a verdict on the vehicle. Model names link to Wikipedia.
Every route as a tile, coloured by on-time %. Faded tiles have few readings (n<30), so treat those as indicative. Tap a tile for its full breakdown. Tiles marked freq run 6+ buses an hour, where the official standard judges wait time, not timetable punctuality.
A reading is a recorded approach within 150 m of a timing point. "Median/Mean" are seconds early (−) or late (+).
What we claim
- These figures are our independent measurement of on-time performance at timing points, computed from operators' public BODS real-time feeds against the published timetable.
- We use the DfT statistical on-time definition: a stop counts as on-time if the bus is between 1 minute early and 5 min 59 s late.
- The method, the code, and the limitations are all open. Anyone can reproduce or challenge them.
What we do not claim
- We do not claim any operator is breaking the law or withholding required data. Operators are legally required to publish timetables, vehicle locations and fares, and they do. Performance figures are not a statutory publication requirement.
- We do not claim these are the official figures. They are an independent estimate and will differ from any internal operator or regulator measurement.
- Low-sample routes, smaller operators with patchier real-time data, and partial collection days are not reliable on their own, and are flagged as such.
Full methodology
The complete method, data sources (including the routes drawn from TNDS that operators do not publish to BODS), the geography, fleet and frequent-service definitions, and every limitation are documented in AUDIT_METHODOLOGY.md in the GitHub repository.