Train RRReis A 17864 Zutphen – Apeldoorn

Zutphen 20:37 → Apeldoorn 20:56 Daily 0 h 19 min · 5 stops RRReis A

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 20:37 from Zutphen · Sun 8 Nov

Next departure 20:37 today · Zutphen
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 7 full · 5 partial · 13 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 9 full · 5 partial · 30 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

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

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

Worst days

  • Sun 11 Oct Max en route +4 min · last fix heading to Apeldoorn De Maten +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
20:37on time on time
20:41≈ on time ≈ +1 min
20:46≈ on time ≈ +1 min
20:52≈ on time ≈ +1 min
20:56on time +1 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 NovApeldoorn De Maten 21:04Partial coverage0 min—
Thu 5 Nov— 20:58No data—
Wed 4 Nov— 20:590 min—
Mon 2 Nov— 20:58No data—
Sun 1 NovApeldoorn De Maten 21:08Partial coverage+2 min+2 min
Sat 31 OctApeldoorn De Maten 21:06No data—
Fri 30 Oct— 21:00No data—
Thu 29 Oct— 20:580 min—
Wed 28 Oct— 21:010 min—
Tue 27 Oct— 20:590 min—
Mon 26 Oct— 21:03No data—
Sun 25 OctApeldoorn De Maten 21:13No data—
Sat 24 OctApeldoorn De Maten 21:07No data—
Fri 23 Oct— 20:59+1 min+1 min
Thu 22 Oct— 21:01No data—
Wed 21 Oct— 20:59No data—
Tue 20 Oct— 20:590 min—
Mon 19 Oct— 20:57No data—
Sun 18 OctApeldoorn De Maten 21:06Partial coverage0 min—
Sat 17 OctApeldoorn De Maten 21:06No data—
Thu 15 Oct— 20:59No data—
Wed 14 Oct— 21:00No data—
Mon 12 Oct— 20:590 min—
Sun 11 OctApeldoorn De Maten 21:10Partial coverage+4 min+4 min
Sat 10 OctApeldoorn De Maten 21:06Partial coverage0 min—
Wed 7 Oct— 20:580 min—
Tue 6 Oct— 21:00+3 min+4 min
Sun 4 OctApeldoorn De Maten 21:07No data—
Sat 3 OctApeldoorn De Maten 21:06No data—
Sun 27 SeptApeldoorn De Maten 21:07No data—