Train RRReis A 31128 Arnhem Centraal → Tiel
RRReis A 31128 Arnhem Centraal–Tiel: final delay under 3 min on 9 of its 12 runs with data in the last 30 days (75%). Median final delay: +2 min. TrainsRadar data as of 22 Nov 2026, 09:59 (GMT+1).
An alert on this phone or computer when the 31128 is 5 min or more late, every day it runs. No account, no email.
It does not run today
Last recorded run: Friday 20 November +2 min
Next service: tomorrow 12:08 from Arnhem Centraal · Mon 23 Nov
Last 30 days
Arrival delay at Tiel, 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 9 Nov Max en route +8 min · last fix heading to Kesteren +8 min
- Fri 13 Nov Max en route +5 min · last fix heading to Kesteren +5 min
- Wed 4 Nov Max en route +4 min · last fix heading to Kesteren +4 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 83% · 15
- 3–10 min 17% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 75% M n=4
- 100% T n=5
- 75% W n=4
- 100% T n=2
- 67% F n=3
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 18 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 12:08 | on time | on time | |
| 12:14 / 12:15 | — | — | |
| 12:24 | — | — | |
| 12:27 | — | — | |
| 12:30 | — | — | |
| 12:34 | — | — | |
| 12:43 | — | — |
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.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 20 Nov | Kesteren 12:49Partial coverage | +2 min | +2 min |
| Thu 19 Nov | Kesteren 12:49Partial coverage | +1 min | +1 min |
| Wed 18 Nov | Kesteren 12:49Partial coverage | +1 min | +1 min |
| Tue 17 Nov | Kesteren 12:49Partial coverage | +2 min | +2 min |
| Mon 16 Nov | Kesteren 12:49Partial coverage | +1 min | +1 min |
| Fri 13 Nov | Kesteren 12:53Partial coverage | +5 min | +5 min |
| Thu 12 Nov | Kesteren 12:49Partial coverage | +2 min | +2 min |
| Wed 11 Nov | Kesteren 12:49 | No data | — |
| Tue 10 Nov | Kesteren 12:49Partial coverage | +1 min | — |
| Mon 9 Nov | Kesteren 12:57Partial coverage | +8 min | +8 min |
| Fri 6 Nov | Kesteren 12:49 | No data | — |
| Thu 5 Nov | Kesteren 12:49 | No data | — |
| Wed 4 Nov | Kesteren 12:53Partial coverage | +4 min | +4 min |
| Tue 3 Nov | Kesteren 12:49 | No data | — |
| Mon 2 Nov | Kesteren 12:49 | No data | — |
| Fri 30 Oct | Kesteren 12:49 | No data | — |
| Thu 29 Oct | Kesteren 12:50 | No data | — |
| Wed 28 Oct | Kesteren 12:50Partial coverage | 0 min | — |
| Tue 27 Oct | Kesteren 12:51Partial coverage | 0 min | — |
| Mon 26 Oct | Kesteren 12:48 | No data | — |
| Fri 23 Oct | Kesteren 12:50 | No data | — |
| Thu 22 Oct | Kesteren 12:49 | No data | — |
| Wed 21 Oct | Kesteren 12:50 | No data | — |
| Tue 20 Oct | Kesteren 12:49Partial coverage | 0 min | — |
| Mon 19 Oct | Kesteren 12:48Partial coverage | 0 min | — |
| Fri 16 Oct | Kesteren 12:53 | No data | — |
| Thu 15 Oct | Kesteren 12:50 | No data | — |
| Tue 13 Oct | Kesteren 12:50 | No data | — |
| Mon 12 Oct | Kesteren 12:53 | No data | — |
| Fri 9 Oct | Kesteren 12:49Partial coverage | 0 min | — |