Train RRReis A 17872 Zutphen – Apeldoorn

Zutphen 22:37 → Apeldoorn 22:56 Daily 0 h 19 min · 5 stops RRReis A

It has not run yet today

Last recorded run: Saturday 7 November No data

Next service: today 22:37 from Zutphen · Sun 8 Nov

Next departure 22:37 today · Zutphen
On-time · 30 days
80%
8/10 runs under 3 min
RT coverage: 7 full · 3 partial · 16 no data
On-time · 90 days
85%
11/13 runs under 3 min
RT coverage: 10 full · 3 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Fri 6 Nov Max en route +6 min · last fix heading to — +5 min
  • Fri 23 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 11
  • 3–10 min 15% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
22:37on time +2 min
22:41≈ on time ≈ +3 min
22:46≈ on time ≈ +3 min
22:52≈ on time ≈ +3 min
22:56on time +4 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 NovApeldoorn De Maten 23:04No data—
Fri 6 Nov— 23:03+5 min+6 min
Thu 5 Nov— 22:58No data—
Wed 4 Nov— 22:59+1 min—
Tue 3 Nov— 22:59No data—
Mon 2 Nov— 22:590 min—
Sun 1 NovApeldoorn De Maten 23:04Partial coverage0 min—
Sat 31 OctApeldoorn De Maten 23:06No data—
Fri 30 Oct— 23:01No data—
Thu 29 Oct— 23:000 min+2 min
Wed 28 Oct— 22:59No data—
Mon 26 Oct— 22:59No data—
Sun 25 OctApeldoorn De Maten 23:06No data—
Sat 24 OctZutphen 22:58No data—
Fri 23 Oct— 23:02+4 min+4 min
Thu 22 Oct— 22:59No data—
Wed 21 Oct— 23:00No data—
Tue 20 Oct— 23:00No data—
Mon 19 Oct— 22:58No data—
Sun 18 OctApeldoorn De Maten 23:09Partial coverage+2 min+3 min
Sat 17 OctApeldoorn De Maten 23:06No data—
Fri 16 Oct— 22:59+1 min+1 min
Wed 14 Oct— 22:57No data—
Tue 13 Oct— 23:00No data—
Sun 11 OctApeldoorn De Maten 23:06Partial coverage0 min—
Sat 10 Oct— 22:59+1 min—
Fri 9 Oct— 22:590 min—
Thu 8 Oct— 22:590 min+1 min
Wed 7 Oct— 22:540 min—
Tue 6 Oct— 22:58No data—