Train RRReis A 17859 Apeldoorn – Zutphen

Apeldoorn 18:06 → Zutphen 18:25 Daily 0 h 19 min · 5 stops RRReis A

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 18:06 from Apeldoorn · Thu 5 Nov

Next departure 18:06 today · Apeldoorn
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 6 full · 7 partial · 15 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 6 full · 8 partial · 64 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: +1 min

Last 30 days

Arrival delay at Zutphen, 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 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
  • — T n=0
  • 100% F n=1
  • 100% S n=2
  • 100% 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
18:06on time on time
18:09≈ on time ≈ +1 min
18:14 / 18:15≈ on time ≈ +1 min
18:20≈ +1 min ≈ +1 min
18:25+1 min +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
Wed 4 NovKlarenbeek 18:29Partial coverage0 min—
Tue 3 NovApeldoorn De Maten 18:23No data—
Mon 2 NovApeldoorn De Maten 18:28No data—
Sun 1 NovVoorst-Empe 18:340 min—
Sat 31 OctVoorst-Empe 18:35+1 min—
Fri 30 OctVoorst-Empe 18:34No data—
Thu 29 Oct— 18:27No data—
Wed 28 OctApeldoorn De Maten 18:28Partial coverage0 min—
Tue 27 Oct— 18:290 min—
Mon 26 OctApeldoorn De Maten 18:27No data—
Sun 25 OctVoorst-Empe 18:34No data—
Sat 24 OctVoorst-Empe 18:35No data—
Fri 23 OctVoorst-Empe 18:34No data—
Thu 22 OctVoorst-Empe 18:34No data—
Wed 21 OctVoorst-Empe 18:34No data—
Tue 20 OctVoorst-Empe 18:34Partial coverage0 min—
Mon 19 OctVoorst-Empe 18:34Partial coverage0 min—
Sun 18 OctVoorst-Empe 18:35+1 min—
Sat 17 OctVoorst-Empe 18:34No data—
Fri 16 OctVoorst-Empe 18:36No data—
Thu 15 OctVoorst-Empe 18:34No data—
Wed 14 OctVoorst-Empe 18:34No data—
Tue 13 OctVoorst-Empe 18:34No data—
Mon 12 OctVoorst-Empe 18:32Partial coverage0 min—
Sun 11 OctVoorst-Empe 18:36+1 min+1 min
Sat 10 OctVoorst-Empe 18:37+2 min+3 min
Fri 9 OctVoorst-Empe 18:34Partial coverage0 min—
Wed 7 OctApeldoorn De Maten 18:29Partial coverage+2 min+2 min
Mon 5 OctApeldoorn De Maten 18:23Partial coverage0 min—
Sun 4 OctVoorst-Empe 18:35No data—