THE DATABRISTOL • GPS-DERIVED • AUDITABLEPARK STREET WATCH
↘PARK STREETWATCH ●
THE NUMBERS BEHIND THE HILL

THE RECEIPTS.

Every completed bus traversal, translated into hourly congestion patterns, weekday comparisons and the journey-time percentiles that matter for reliability.

Default excludes readings with gaps over 60 seconds; counts remain visible.

Connecting to overnight GPS results…

COMPLETE TRAVERSALS—Awaiting records
AVERAGE TIME—Arithmetic mean
85TH PERCENTILE—85% of observed times at or below
SLOWEST OBSERVED—Check extreme GPS cases before quoting
01 / WEEKDAY × HOUR

When does the hill bite?

Each cell shows the selected statistic pooled across the same weekday and hour in the report window. Hover or tap for the observation count.

P85 • MINUTES
Quicker Slower△ Fewer than 20 observations · — No data
Loading…
Colour is relative to the selected corridor and period, not a fixed definition of acceptable congestion. Hours and weekdays are Bristol local time.
02 / ANY DAY AGAINST ANY DAY

The weekday face-off

Select any pair of weekdays. The chart compares matching hours; the headline comparison uses the selected time band.

Awaiting enough observations to compare weekdays.
WednesdayFridayHourly points require at least 3 observed journeys

All-against-all weekday matrix

Difference in the selected metric, in minutes: column day minus row day. Positive means the column day was slower. Both cohorts need at least 20 observations.

Loading…
03 / WEEKDAY × PERIOD

The timetable-planning view

Daypart summaries across all seven weekdays, so AM, interpeak and PM conditions can be compared directly.

Loading…
04 / ACTUAL CALENDAR DAYS

Daily results

Mean, minimum, maximum and every requested percentile, with observation counts for each actual date.

Loading…
05 / SPECIFIC DATES × HOURS

What happened on that day?

Actual individual date/hour results — useful for examining a particular Friday afternoon, not just the pooled Friday pattern. Only hours with observed traversals are listed; omitted hours are not assumed to have zero delay.

Loading…
06 / POOLED HOURLY RESULTS

Hour-by-hour detail

One row for every weekday and hour — all journey-time statistics and the underlying sample count.

Loading…
07 / WEEK ON WEEK

Is it getting better?

Completed Monday–Sunday weeks and comparison against the immediately preceding week, where both have observations.

Loading…
Weekly commentary will appear when enough journeys are available.

C8 dwell adjustment

A→D times deduct the greater of an assumed 90-second C8 stop allowance or observed qualifying stationary C8 dwell. These are not added together. A→B and A→C are unaffected. Original observed times are preserved in the CSV. This is a modelling assumption and may remove some traffic delay at C8.

What these numbers do — and don't — show

Based on real BODS SIRI-VM GPS fixes intersecting our directional virtual gates. Times are interpolated between fixes, not stopwatch measurements. Different gate sequences are different corridor measures and should not be added together as separate buses.

Percentiles use all individual qualifying journeys within the selected group, not an average of daily percentiles. A sample below 20 is indicative, especially for P85/P90/P95; missing feeds and empty days are never treated as zero congestion. Very slow or unusually gappy traversals should be reviewed before external quotation.

Initial collection began on Sunday evening, 18 October 2026. That date is partial, and individual subsequent dates may also have AVL outages. Comparisons are descriptive and not adjusted for traffic incidents, school terms or changes in demand.

← Back to the live downhill derby