Train regional 862Q10

Mon, Tue Unknown

It does not run today

Last recorded run: Monday 19 October 0 min

The mini-map returns when the train runs
On-time · 30 days
67%
2/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
On-time · 90 days
60%
6/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+20min
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

  • Mon 7 Sept Max en route +37 min · last fix heading to 86998 +20 min
  • Mon 17 Aug Max en route +26 min · last fix heading to 87696 +20 min
  • Mon 21 Sept Max en route +13 min · last fix heading to Haslemere +7 min
  • Mon 5 Oct Max en route +6 min · last fix heading to Haslemere +3 min

Distribution · 90 days

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

  • Early 30% · 3
  • On time 30% · 3
  • 3–10 min 20% · 2
  • 10–30 min 20% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 56% M n=9
  • 100% T n=1
  • — W n=0
  • — T n=0
  • — F n=0
  • — S n=0
  • — S n=0

Recent runs

DateLast stopFinalMax
Mon 19 OctHaslemere 14:310 min+6 min
Tue 6 Oct— 00:36+2 min+2 min
Mon 5 OctHaslemere 09:53+3 min+6 min
Mon 21 SeptHaslemere 15:26+7 min+13 min
Mon 14 Sept87696 08:320 min+9 min
Mon 7 Sept86998 09:11+20 min+37 min
Mon 31 Aug87714 08:36−22 min+7 min
Mon 24 AugHaslemere 14:24−4 min+4 min
Mon 17 Aug87696 09:03+20 min+26 min
Mon 10 AugHaslemere 14:28−4 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.