Train RRReis A 17861 Apeldoorn – Zutphen

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

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: Monday 18:36 from Apeldoorn · Mon 9 Nov

Next departure 18:36 Monday · Apeldoorn
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 5 full · 6 partial · 9 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 8 full · 6 partial · 27 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=4
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 100% F n=3
  • — S n=0
  • — S n=0

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:36on time on time
18:39≈ on time ≈ on time
18:44 / 18:45≈ on time ≈ on time
18:50≈ on time ≈ on time
18:55on time on time

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 NovKlarenbeek 18:59Partial coverage+1 min+2 min
Thu 5 Nov— 18:54No data—
Wed 4 Nov— 18:540 min—
Mon 2 Nov— 18:540 min—
Fri 30 OctVoorst-Empe 19:04No data—
Thu 29 Oct— 18:560 min—
Wed 28 Oct— 18:570 min—
Tue 27 Oct— 18:560 min—
Mon 26 Oct— 18:57No data—
Fri 23 OctVoorst-Empe 19:04Partial coverage+1 min—
Thu 22 OctKlarenbeek 18:59No data—
Wed 21 OctApeldoorn De Maten 18:59No data—
Tue 20 OctKlarenbeek 18:50Partial coverage0 min—
Mon 19 OctApeldoorn De Maten 18:57Partial coverage0 min—
Fri 16 OctVoorst-Empe 19:04No data—
Thu 15 Oct— 18:56No data—
Wed 14 OctVoorst-Empe 19:04No data—
Tue 13 OctApeldoorn De Maten 18:57No data—
Mon 12 OctKlarenbeek 18:59Partial coverage0 min—
Fri 9 OctApeldoorn 18:55Partial coverage0 min—
Thu 8 Oct— 18:570 min—
Wed 7 Oct— 18:58+1 min+2 min
Mon 5 Oct— 18:560 min—
Fri 2 OctKlarenbeek 18:59No data—
Fri 18 SeptKlarenbeek 18:59No data—
Fri 11 SeptVoorst-Empe 19:04No data—
Fri 4 SeptVoorst-Empe 19:04No data—
Fri 28 AugVoorst-Empe 19:04No data—
Thu 27 AugKlarenbeek 18:59No data—
Wed 26 AugVoorst-Empe 18:56No data—