Train regional 871V00

Mon Unknown

It does not run today

Last recorded run: Monday 19 October +71 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
78%
7/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
Typical delay
−4min
Median at arrival, 90 days
P90
+17min
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 19 Oct Max en route +89 min · last fix heading to Haverfordwest +71 min
  • Mon 3 Aug Max en route +25 min · last fix heading to Haverfordwest +3 min

Distribution · 90 days

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

  • Early 56% · 5
  • On time 22% · 2
  • 3–10 min 11% · 1
  • 10–30 min 0% · 0
  • 30+ min 11% · 1

On-time by weekday

  • 75% M n=8
  • 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 OctHaverfordwest 00:19+71 min+89 min
Mon 28 SeptHaverfordwest 22:53−13 min+11 min
Mon 21 SeptHaverfordwest 23:08−1 min+19 min
Mon 14 SeptHaverfordwest 23:00−6 min+5 min
Mon 31 AugHaverfordwest 23:02−4 min+9 min
Mon 24 AugHaverfordwest 22:42−24 min+34 min
Mon 17 AugHaverfordwest 22:54−12 min+11 min
Tue 4 Aug— 02:490 min—
Mon 3 AugHaverfordwest 23:16+3 min+25 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.