GWR 682T32

View line GWR

Sat GWR

It does not run today

Last recorded run: Saturday 10 October +2 min

The mini-map returns when the train runs
On-time · 30 days
—
Too little data (2/2 runs with data)
RT coverage: 2 full · 0 partial · 0 no data
On-time · 90 days
57%
4/7 runs under 3 min
RT coverage: 7 full · 0 partial · 0 no data
Typical delay
+2min
Median at arrival, 90 days
P90
+15min
9 in 10 runs arrive with less than this

Last 30 days

Delay at the end of each run, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 26 Sept Max en route +22 min · last fix heading to 81304 +20 min
  • Sat 12 Sept Max en route +12 min · last fix heading to 81304 +12 min
  • Sat 5 Sept Max en route +8 min · last fix heading to 81304 +7 min

Distribution · 90 days

7 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 14% · 1
  • On time 43% · 3
  • 3–10 min 14% · 1
  • 10–30 min 29% · 2
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 57% S n=7
  • — S n=0

Recent runs

DateLast stopFinalMax
Sat 10 OctFilton Abbey Wood 21:07+2 min+6 min
Sat 26 Sept81304 21:22+20 min+22 min
Sat 12 Sept81304 21:18+12 min+12 min
Sat 5 Sept81304 21:08+7 min+8 min
Sat 22 Aug81304 21:02−1 min+3 min
Sat 8 Aug81304 21:00−2 min—
Sat 1 Aug81304 21:01−1 min—

Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 11 July 2026.