Train RRReis A 17850 Zutphen – Apeldoorn

Zutphen 17:06 → Apeldoorn 17:25 Mon, Tue, Wed, Thu, Fri 0 h 19 min · 5 stops RRReis A

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 17:06 from Zutphen · Thu 5 Nov

Next departure 17:06 today · Zutphen
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 13 no data
On-time · 90 days
90%
9/10 runs under 3 min
RT coverage: 0 full · 10 partial · 52 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: 0 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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 9
  • 3–10 min 10% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=2
  • 100% W n=1
  • 100% T n=2
  • 100% F n=1
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 10 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
17:06on time on time
17:10— —
17:15 / 17:16— —
17:22— —
17:25— —

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
Wed 4 NovApeldoorn De Maten 17:34No data—
Tue 3 NovApeldoorn De Maten 17:34Partial coverage0 min—
Mon 2 NovApeldoorn De Maten 17:34Partial coverage0 min—
Fri 30 OctApeldoorn De Maten 17:36No data—
Thu 29 OctApeldoorn De Maten 17:33Partial coverage0 min—
Wed 28 OctApeldoorn De Maten 17:36Partial coverage0 min—
Tue 27 OctApeldoorn De Maten 17:36No data—
Mon 26 OctApeldoorn De Maten 17:36No data—
Fri 23 OctApeldoorn De Maten 17:36No data—
Thu 22 OctApeldoorn De Maten 17:36No data—
Wed 21 OctApeldoorn De Maten 17:37No data—
Tue 20 OctApeldoorn De Maten 17:36No data—
Mon 19 OctApeldoorn De Maten 17:36Partial coverage0 min—
Fri 16 OctApeldoorn De Maten 17:36No data—
Thu 15 OctApeldoorn De Maten 17:36No data—
Wed 14 OctApeldoorn De Maten 17:37No data—
Tue 13 OctApeldoorn De Maten 17:36No data—
Mon 12 OctApeldoorn De Maten 17:37Partial coverage0 min—
Fri 9 OctApeldoorn De Maten 17:36Partial coverage0 min—
Thu 8 OctApeldoorn De Maten 17:34Partial coverage+1 min—
Wed 7 OctApeldoorn De Maten 17:36No data—
Tue 6 OctApeldoorn De Maten 17:36Partial coverage0 min—
Mon 5 OctApeldoorn De Maten 17:36Partial coverage+4 min+4 min
Fri 2 OctApeldoorn De Maten 17:36No data—
Thu 1 OctApeldoorn De Maten 17:36No data—
Wed 30 SeptApeldoorn De Maten 17:36No data—
Tue 29 SeptApeldoorn De Maten 17:36No data—
Mon 28 SeptApeldoorn De Maten 17:36No data—
Fri 25 SeptApeldoorn De Maten 17:36No data—
Thu 24 SeptApeldoorn De Maten 17:36No data—