How many buses it took
Peak vehicle requirement, counted from the vehicles that actually reported — not from the timetable’s blocks, which only 42% of journeys carry. Back to the overview.
Data held 4 Aug 2026 – 3 Oct 2026. A gap of up to 20 minutes between two journeys on the same vehicle counts as layover rather than the bus going away.
Peak by day
A peak across a fortnight is the busiest minute of the busiest day — true, and not much use. The headline is the median of the daily peaks; the days are here so an unusual one can be seen for what it is.
Vehicle diagrams
One row per bus, one bar per journey, for a single day. Pick a route in the filters above — a whole network is four hundred rows of bars, which is a picture of nothing.
Why this is measured from vehicles
Blocks are mostly per service
Where a bus ran two journeys back to back and the block changed, 95% of the time the route changed too — so a block is largely a working within one service, not one bus’s day. Where block and vehicle ought to agree (same route, gap under ten minutes) they disagree on 50 pairs in 5,666.
In service and required are different
A bus standing at a terminus for eight minutes is not available for anything else, so it still counts. That is the larger figure and the more useful one. The smaller counts a bus only while it is running.
It is a floor, not the fleet
A vehicle that never reported never appears. This counts buses seen in the open feed, so the true requirement is this or higher — never lower.
The layover threshold is a dial
It moves the answer, so it is printed rather than buried. Longer, and more of a bus’s day counts as held by the route; shorter, and a genuine layover reads as the bus going away.