Skip to main content
Otranspo

Week report ending Aug 2, 2026

Every figure here is a count of arrivals this site observed and settled, added up over the service dates in the period. Routes are named for running well on the same evidence they are named for running badly.

Frozen publication

Published on Sep 15, 2026, 1:12 a.m. under settled-arrival-period-report-v2. This stored snapshot will not be recomputed when evidence or code changes.

Across the network

Jul 27, 2026 to Aug 2, 2026 · 2 of 7 calendar days measured

Arrivals on time
72.4%
Arrivals observed
322,270
Routes measured
70

The prior equal calendar period is unavailable or incomplete, so no change is calculated.

Dates absent from the figures

No completed rollup exists for these dates. They are shown as missing and are not treated as zero or as good service.

  • Jul 27, 2026
  • Jul 28, 2026
  • Jul 29, 2026
  • Jul 30, 2026
  • Jul 31, 2026

Most reliable this period

The routes with the highest share of settled arrivals within five minutes of the timetable. All use the same route class, evidence threshold and period. This is a relative ranking, not an operator target.

Furthest from the timetable

The routes with the lowest share of on-time arrivals. A low figure does not say whose fault it is: a route can be late because its timetable is wrong, because the service is failing, or because of the traffic it runs in. Each route page separates those.

Frozen publication

Calculation method
settled-arrival-period-report-v2
Evidence available through
Sep 15, 2026, 1:12 a.m.
Download this publication (CSV)