Train RRReis A 17854 Zutphen – Apeldoorn

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

✓ Today’s run finished

Today, last fix heading to Apeldoorn De Maten at 18:34 0 min

  1. Zutphen18:06
  2. Voorst-Empe18:10
  3. Klarenbeek18:15
  4. Apeldoorn De Maten18:22
  5. Apeldoorn18:25

Next service: Monday 18:06 from Zutphen · Mon 9 Nov

Next departure 18:06 Monday · Zutphen
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 2 full · 7 partial · 13 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 2 full · 9 partial · 46 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 11 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
18:06on time on time
18:10— —
18:15 / 18:16— —
18:22— —
18: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
Fri 6 NovApeldoorn De Maten 18:34Partial coverage0 min—
Thu 5 NovVoorst-Empe 18:27No data—
Wed 4 NovVoorst-Empe 18:29Partial coverage0 min—
Tue 3 NovVoorst-Empe 18:24No data—
Mon 2 NovVoorst-Empe 18:28No data—
Fri 30 OctApeldoorn De Maten 18:36No data—
Thu 29 Oct— 18:27No data—
Wed 28 OctVoorst-Empe 18:28Partial coverage0 min—
Tue 27 Oct— 18:290 min—
Mon 26 OctZutphen 18:28No data—
Fri 23 OctApeldoorn De Maten 18:36No data—
Thu 22 OctApeldoorn De Maten 18:36No data—
Wed 21 OctApeldoorn De Maten 18:34No data—
Tue 20 OctApeldoorn De Maten 18:36Partial coverage0 min—
Mon 19 OctApeldoorn De Maten 18:36Partial coverage0 min—
Fri 16 OctApeldoorn De Maten 18:36No data—
Thu 15 OctApeldoorn De Maten 18:36No data—
Wed 14 OctApeldoorn De Maten 18:36No data—
Tue 13 OctApeldoorn De Maten 18:36No data—
Mon 12 OctApeldoorn De Maten 18:32Partial coverage0 min—
Fri 9 OctApeldoorn De Maten 18:36Partial coverage0 min—
Thu 8 Oct— 18:290 min—
Wed 7 OctZutphen 18:28Partial coverage0 min—
Mon 5 OctVoorst-Empe 18:26Partial coverage0 min—
Fri 2 OctApeldoorn De Maten 18:36No data—
Thu 1 OctZutphen 18:20No data—
Wed 30 SeptZutphen 18:18No data—
Tue 29 SeptZutphen 18:20No data—
Fri 25 SeptApeldoorn De Maten 18:36No data—
Wed 23 SeptVoorst-Empe 18:24No data—