Train RRReis A 30939 Arnhem Centraal – Winterswijk

Arnhem Centraal 13:05 → Winterswijk 14:10 Daily 1 h 05 min · 14 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Aalten at 14:14 0 min

  1. Arnhem Centraal13:05
  2. Westervoort13:11
  3. Zevenaar13:19
  4. Doetinchem De Huet13:33
  5. Gaanderen13:42
  6. Aalten13:59
  7. Winterswijk14:10

Next service: tomorrow 13:05 from Arnhem Centraal · Wed 18 Nov

Next departure 13:05 tomorrow · Arnhem Centraal
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 4 full · 16 partial · 10 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 4 full · 23 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Winterswijk, in minutes. One bar per run.

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

Worst days

  • Wed 4 Nov Max en route +4 min · last fix heading to Aalten +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 75% W n=4
  • 100% T n=3
  • 100% F n=2
  • 100% S n=5
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (14 stops).

Last 90 days, 27 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.

StopSched.Usually 9 days in 10
13:05on time on time
13:07— —
13:11— —
13:15— —
13:19 / 13:20— —
13:24— —
13:29 / 13:30— —
13:33— —
13:37 / 13:38— —
13:42— —
13:44 / 13:45— —
13:51— —
13:59 / 14:00— —
14:10— —

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

DateLast stopFinalMax
Tue 17 NovAalten 14:14Partial coverage0 min—
Mon 16 NovVarsseveld 14:05Partial coverage0 min—
Sun 15 NovAalten 14:15+1 min+1 min
Sat 14 NovAalten 14:14Partial coverage+2 min+2 min
Fri 13 NovAalten 14:14Partial coverage0 min+1 min
Thu 12 NovAalten 14:14Partial coverage0 min—
Wed 11 NovAalten 14:14Partial coverage+1 min+1 min
Tue 10 NovAalten 14:15Partial coverage+1 min+1 min
Mon 9 NovAalten 14:14Partial coverage0 min—
Sun 8 NovAalten 14:140 min—
Sat 7 NovAalten 14:140 min—
Fri 6 NovAalten 14:14No data—
Thu 5 NovAalten 14:14No data—
Wed 4 NovAalten 14:19Partial coverage+4 min+4 min
Tue 3 NovAalten 14:14Partial coverage0 min—
Mon 2 NovAalten 14:14Partial coverage0 min—
Sun 1 NovAalten 14:15No data—
Sat 31 OctAalten 14:140 min—
Fri 30 OctAalten 14:16No data—
Thu 29 OctAalten 14:15Partial coverage0 min—
Wed 28 OctAalten 14:14Partial coverage0 min—
Tue 27 OctAalten 14:15No data—
Mon 26 OctAalten 14:14No data—
Sun 25 OctAalten 14:14No data—
Sat 24 OctAalten 14:14Partial coverage0 min—
Fri 23 OctAalten 14:14No data—
Thu 22 OctAalten 14:14No data—
Wed 21 OctAalten 14:14No data—
Tue 20 OctAalten 14:14Partial coverage0 min—
Mon 19 OctAalten 14:14Partial coverage0 min—