Train RRReis A 30930 Winterswijk – Didam
✓ Today’s run finished
Today, last fix heading to Wehl at 12:27 0 min
- Winterswijk11:20
- Aalten11:29
- Terborg11:44
- Gaanderen11:47
- Doetinchem11:52
- Wehl11:59
- Didam12:05
Next service: tomorrow 11:20 from Winterswijk · Sun 8 Nov
Last 30 days
Arrival delay at Didam, 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 5 Oct Max en route +6 min · last fix heading to Arnhem Velperpoort +5 min
- Fri 9 Oct Max en route +4 min · last fix heading to Arnhem Velperpoort +4 min
- Thu 8 Oct Max en route +4 min · last fix heading to Arnhem Velperpoort +4 min
Distribution · 90 days
16 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 81% · 13
- 3–10 min 19% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 0% M n=1
- 100% T n=3
- 100% W n=3
- 0% T n=1
- 0% F n=1
- 100% S n=4
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 16 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 |
|---|---|---|---|
| 11:20 | on time | on time | |
| 11:29 / 11:30 | ≈ on time | ≈ +1 min | |
| 11:37 | ≈ +1 min | ≈ +2 min | |
| 11:44 / 11:45 | ≈ +1 min | ≈ +2 min | |
| 11:47 | ≈ +1 min | ≈ +3 min | |
| 11:52 / 11:53 | ≈ +2 min | ≈ +3 min | |
| 11:56 | ≈ +2 min | ≈ +3 min | |
| 11:59 / 12:00 | ≈ +2 min | ≈ +4 min | |
| 12:05 | +2 min | +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.
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 |
|---|---|---|---|
| Sat 7 Nov | Wehl 12:27Partial coverage | 0 min | — |
| Fri 6 Nov | Arnhem Velperpoort 12:37 | No data | — |
| Thu 5 Nov | Arnhem Velperpoort 12:39 | No data | — |
| Wed 4 Nov | Arnhem Velperpoort 12:38 | +2 min | +2 min |
| Tue 3 Nov | Arnhem Velperpoort 12:38 | No data | — |
| Mon 2 Nov | Arnhem Velperpoort 12:43 | No data | — |
| Sun 1 Nov | Wehl 12:15Partial coverage | 0 min | — |
| Sat 31 Oct | Wehl 12:15Partial coverage | +1 min | — |
| Fri 30 Oct | Arnhem Velperpoort 12:37 | No data | — |
| Thu 29 Oct | Arnhem Velperpoort 12:39 | No data | — |
| Wed 28 Oct | Arnhem Velperpoort 12:41 | 0 min | — |
| Tue 27 Oct | Arnhem Velperpoort 12:37 | 0 min | — |
| Mon 26 Oct | Arnhem Velperpoort 12:40 | No data | — |
| Sun 25 Oct | Arnhem Velperpoort 12:43 | No data | — |
| Sat 24 Oct | Arnhem Velperpoort 12:38 | +3 min | +3 min |
| Fri 23 Oct | Arnhem Velperpoort 12:37 | No data | — |
| Thu 22 Oct | Arnhem Velperpoort 12:36 | No data | — |
| Wed 21 Oct | Arnhem Velperpoort 12:40 | No data | — |
| Tue 20 Oct | Arnhem Velperpoort 12:37 | 0 min | — |
| Mon 19 Oct | Arnhem Velperpoort 12:36 | No data | — |
| Sun 18 Oct | Arnhem Velperpoort 12:37 | +2 min | +2 min |
| Sat 17 Oct | Arnhem Velperpoort 12:37 | No data | — |
| Fri 16 Oct | Arnhem Velperpoort 12:38 | No data | — |
| Thu 15 Oct | Arnhem Velperpoort 12:37 | No data | — |
| Wed 14 Oct | Arnhem Velperpoort 12:39 | No data | — |
| Tue 13 Oct | Arnhem Velperpoort 12:38 | No data | — |
| Mon 12 Oct | Arnhem Velperpoort 12:37 | No data | — |
| Sun 11 Oct | Arnhem Velperpoort 12:38 | +2 min | +2 min |
| Sat 10 Oct | Arnhem Velperpoort 12:38 | +3 min | +3 min |
| Fri 9 Oct | Arnhem Velperpoort 12:40 | +4 min | +4 min |