Train RRReis A 30462 Zutphen – Apeldoorn

Zutphen 20:05 → Apeldoorn 20:17 Daily 0 h 12 min · 2 stops RRReis A

It has not run yet today

Last recorded run: Saturday 7 November 0 min

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

Next departure 20:05 today · Zutphen
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 5 full · 6 partial · 14 no data
On-time · 90 days
80%
12/15 runs under 3 min
RT coverage: 9 full · 6 partial · 33 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +1 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 18 Oct Max en route +7 min · last fix heading to Zutphen +7 min
  • Wed 7 Oct Max en route +4 min · last fix heading to — +4 min
  • Mon 5 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 12
  • 3–10 min 20% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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:05on time +1 min
20:17+1 min +3 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 NovZutphen 20:19Partial coverage0 min—
Fri 6 Nov— 20:19+1 min—
Thu 5 Nov— 20:20No data—
Wed 4 Nov— 20:190 min—
Mon 2 Nov— 20:23No data—
Sun 1 NovZutphen 20:19Partial coverage+1 min+1 min
Sat 31 OctZutphen 20:21Partial coverage+1 min+1 min
Fri 30 Oct— 20:20No data—
Thu 29 Oct— 20:21+1 min+1 min
Wed 28 Oct— 20:21No data—
Tue 27 Oct— 20:21No data—
Mon 26 Oct— 20:200 min—
Sun 25 OctZutphen 20:26No data—
Sat 24 OctZutphen 20:26No data—
Thu 22 Oct— 20:22No data—
Wed 21 Oct— 20:43No data—
Mon 19 Oct— 20:21No data—
Sun 18 OctZutphen 20:27Partial coverage+7 min+7 min
Sat 17 OctZutphen 20:21No data—
Fri 16 Oct— 20:26No data—
Thu 15 Oct— 21:16No data—
Tue 13 Oct— 20:30No data—
Mon 12 Oct— 20:290 min—
Sun 11 OctZutphen 20:19Partial coverage+1 min—
Sat 10 OctZutphen 20:19Partial coverage+1 min+1 min
Fri 9 Oct— 20:21+2 min+2 min
Thu 8 Oct— 20:20+1 min+1 min
Wed 7 Oct— 20:24+4 min+4 min
Mon 5 Oct— 20:23+3 min+3 min
Sun 4 OctZutphen 20:19No data—