Every departure this tracker has resolved over the last 7 days · Fri 9 Oct – Fri 16 Oct 2026 (8 days)
· generated Fri 16 Oct 2026, 23:47. The homepage only ever shows the last 24 hours;
this page is the record.
1256 of 2232 tracked journeys (56%) were late, severely late,
or never showed up.
2232
Journeys tracked
1256
Late or worse
976
On time
507
Never tracked
4m
Median delay
48m
Worst delay
What the data says
Route 4 is the worst performer: 81% of its 319 tracked journeys ran late, severely late, or never showed at all.
The network degrades through the afternoon: departures scheduled at 17:00 averaged 9 minutes late, against 6 minutes across the whole day.
The 21:00 hour fails most often: 75% of its 84 journeys.
507 scheduled journeys never reported a live position at all — the departure board simply stopped predicting them. These are the ghost buses this site exists for.
Day by day
Every resolved journey, stacked by outcome. The number above each bar is the share that went wrong.
On timeLateSeverely lateNo-show
A journey is counted once, on the day it was scheduled to depart, using the outcome at its final stop.
Time of day
Bars: how often departures in that hour go wrong. Line: how many minutes late they run on average, on the right-hand axis.
LateSeverely lateNo-show
Hollow dashed stubs are hours with fewer than 8 tracked journeys — shown, but not rated, because a percentage off two buses is noise.
Route by route
Each route's journeys as a share of its own total, worst first. Normalised, because route 1 runs far more services than route 4 and raw counts would just redraw the timetable.
On timeLateSeverely lateNo-show
Where and when it breaks
Share of journeys that went wrong, by route and hour. Darker is worse; faint cells are hours with too little data to rate.
Share of journeys late or worse0%100%
How late is late
Distribution of the worst delay recorded on each journey.
Buckets align with the thresholds used everywhere else on this site: over 5 minutes counts as late, over 10 as severely late.
Day of week
Same measure, grouped by weekday.
On timeLateSeverely lateNo-show
Departures that fail every time
Scheduled departures this tracker has seen at least twice and which have gone wrong on every single occasion. If you catch one of these regularly, this is the evidence.
Departs
Route
Towards
Times seen
Never tracked
Avg delay
17:36
Route 3
Kelvin Heights
7
2
22 min
16:54
Route 3
Quail Rise
7
2
19 min
15:36
Route 3
Kelvin Heights
7
2
16 min
10:00
Route 4
Arrowtown
7
1
16 min
20:42
Route 4
Jacks Point
7
1
15 min
17:13
Route 1
Sunshine Bay
7
3
15 min
11:00
Route 4
Arrowtown
7
0
14 min
21:42
Route 4
Jacks Point
7
2
14 min
07:30
Route 4
Arrowtown
7
0
14 min
12:05
Route 5
Lake Hayes Estate
7
2
13 min
21:08
Route 5
Lake Hayes Estate
7
2
13 min
14:00
Route 4
Arrowtown
7
1
13 min
How to read this
On time means the live departure board tracked the bus and it
arrived within 5 minutes of its published time.
Never tracked means the board never published a live position
for a scheduled departure — from a rider's point of view, a bus that
didn't come. It is not proof the bus was cancelled, and ORC's board does not
expose cancellations to us at all.
These figures come from the live departure-board API, the same source
ORC's own tracker uses. The
schedule reconciliation page
cross-checks a single day against the published GTFS timetable instead, which
is a stronger but narrower signal.
Only journeys this tracker was actually running for are counted, so a
restart or an outage on our side shows up as a smaller sample that day, never
as a run of no-shows.