Train RRReis A 30431 Apeldoorn – Winterswijk

Apeldoorn 11:24 → Winterswijk 12:10 Sat, Sun 0 h 46 min · 7 stops RRReis A

Running now · updated 11:46

Heading to Winterswijk 0 min

Estimated arrival at Winterswijk 12:10 · 178 km/h

  1. Apeldoorn11:24
  2. Zutphen11:37
  3. Vorden11:45
  4. Ruurlo11:52
  5. Lichtenvoorde-Groenlo12:00
  6. Winterswijk West12:07
  7. Winterswijk12:10

Today it is running no worse than usual: typical arrival delay is +1 min; 100% of the last 7 runs arrived on time.

On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 3 full · 4 partial · 2 no data
On-time · 90 days
100%
7/7 runs under 3 min
RT coverage: 3 full · 4 partial · 16 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 7
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 7 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 10Today
11:24on time on time
11:37 / 11:38— —
11:45 / 11:46— —
11:52— —
12:00— —
12:07— —
12: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
Sat 7 NovVorden 11:44Partial coverage0 min—
Sun 1 NovWinterswijk West 12:230 min—
Sat 31 OctWinterswijk West 12:23Partial coverage+2 min+2 min
Sun 25 OctWinterswijk West 12:22No data—
Sat 24 OctWinterswijk West 12:23Partial coverage+1 min+2 min
Sun 18 OctWinterswijk West 12:210 min—
Sat 17 OctWinterswijk West 12:23No data—
Sun 11 OctWinterswijk West 12:22+1 min—
Sat 10 OctWinterswijk West 12:22Partial coverage+1 min+1 min
Sun 4 OctWinterswijk West 12:22No data—
Sat 3 OctWinterswijk West 12:22No data—
Sun 27 SeptWinterswijk West 12:21No data—
Sat 26 SeptWinterswijk West 12:21No data—
Sun 20 SeptWinterswijk West 12:21No data—
Sat 19 SeptWinterswijk West 12:23No data—
Sun 6 SeptWinterswijk West 12:21No data—
Sat 5 SeptWinterswijk West 12:21No data—
Sun 30 AugWinterswijk West 12:21No data—
Sat 29 AugWinterswijk West 12:21No data—
Sun 23 AugWinterswijk West 12:22No data—
Sat 22 AugWinterswijk West 12:21No data—
Sun 16 AugWinterswijk West 12:22No data—
Sat 15 AugWinterswijk West 12:21No data—