Train RRReis A 30926 Winterswijk – Didam

Winterswijk 10:20 → Didam 11:05 Daily 0 h 45 min · 9 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Wehl at 11:14 0 min

  1. Winterswijk10:20
  2. Aalten10:29
  3. Terborg10:44
  4. Gaanderen10:47
  5. Doetinchem10:52
  6. Wehl10:59
  7. Didam11:05

Next service: tomorrow 10:20 from Winterswijk · Sun 8 Nov

Next departure 10:20 tomorrow · Winterswijk
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 11 full · 2 partial · 17 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 13 full · 2 partial · 74 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
10:20on time on time
10:29 / 10:30≈ on time ≈ on time
10:37≈ on time ≈ +1 min
10:44 / 10:45≈ on time ≈ +1 min
10:47≈ on time ≈ +1 min
10:52 / 10:53≈ on time ≈ +1 min
10:56≈ on time ≈ +1 min
10:59 / 11:00≈ on time ≈ +2 min
11:05on time +2 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

DateLast stopFinalMax
Sat 7 NovWehl 11:14Partial coverage0 min—
Fri 6 NovArnhem Velperpoort 11:34No data—
Thu 5 NovArnhem Velperpoort 11:38No data—
Wed 4 NovArnhem Velperpoort 11:38+1 min+1 min
Tue 3 NovArnhem Velperpoort 11:35No data—
Mon 2 NovArnhem Velperpoort 11:38No data—
Sun 1 NovWehl 11:15No data—
Sat 31 OctWehl 11:15Partial coverage0 min—
Fri 30 OctArnhem Velperpoort 11:36No data—
Thu 29 OctArnhem Velperpoort 11:370 min—
Wed 28 OctArnhem Velperpoort 11:390 min—
Tue 27 OctArnhem Velperpoort 11:390 min—
Mon 26 OctArnhem Velperpoort 11:36No data—
Sun 25 OctArnhem Velperpoort 11:38No data—
Sat 24 OctArnhem Velperpoort 11:38+2 min+2 min
Fri 23 OctArnhem Velperpoort 11:38No data—
Thu 22 OctArnhem Velperpoort 11:36No data—
Wed 21 OctArnhem Velperpoort 11:48No data—
Tue 20 OctArnhem Velperpoort 11:370 min—
Mon 19 OctArnhem Velperpoort 11:370 min—
Sun 18 OctArnhem Velperpoort 11:37+2 min+2 min
Sat 17 OctArnhem Velperpoort 11:39No data—
Fri 16 OctArnhem Velperpoort 11:36No data—
Thu 15 OctArnhem Velperpoort 11:38No data—
Wed 14 OctArnhem Velperpoort 11:38No data—
Tue 13 OctArnhem Velperpoort 11:38No data—
Mon 12 OctArnhem Velperpoort 11:36No data—
Sun 11 OctArnhem Velperpoort 11:38+1 min+1 min
Sat 10 OctArnhem Velperpoort 11:370 min—
Fri 9 OctArnhem Velperpoort 11:37+1 min+1 min