Train RRReis A 17848 Zutphen – Apeldoorn

Zutphen 16:36 → Apeldoorn 16:55 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 16:36 from Zutphen · Thu 5 Nov

Next departure 16:36 today · Zutphen
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 5 full · 9 partial · 15 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 5 full · 11 partial · 70 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

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

  • Early 0% · 0
  • On time 100% · 16
  • 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=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 16 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
16:36on time on time
16:40≈ on time ≈ on time
16:45 / 16:46≈ on time ≈ on time
16:52≈ on time ≈ on time
16: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
Wed 4 NovApeldoorn De Maten 17:04Partial coverage0 min—
Tue 3 NovApeldoorn De Maten 17:05No data—
Mon 2 NovApeldoorn De Maten 17:04No data—
Sun 1 NovApeldoorn De Maten 17:060 min—
Sat 31 OctApeldoorn De Maten 17:070 min—
Fri 30 OctApeldoorn De Maten 17:06No data—
Thu 29 OctApeldoorn De Maten 17:06Partial coverage0 min—
Wed 28 OctApeldoorn De Maten 17:06Partial coverage0 min—
Tue 27 OctApeldoorn De Maten 17:06Partial coverage0 min—
Mon 26 OctApeldoorn De Maten 17:06No data—
Sun 25 OctApeldoorn De Maten 17:06No data—
Sat 24 OctApeldoorn De Maten 17:060 min—
Fri 23 OctApeldoorn De Maten 17:06No data—
Thu 22 OctApeldoorn De Maten 17:06No data—
Wed 21 OctApeldoorn De Maten 17:06No data—
Tue 20 OctApeldoorn De Maten 17:06Partial coverage0 min—
Mon 19 OctApeldoorn De Maten 17:08Partial coverage0 min—
Sun 18 OctApeldoorn De Maten 17:060 min—
Sat 17 OctApeldoorn De Maten 17:06No data—
Fri 16 OctApeldoorn De Maten 17:06No data—
Thu 15 OctApeldoorn De Maten 17:06No data—
Wed 14 OctApeldoorn De Maten 17:06No data—
Tue 13 OctApeldoorn De Maten 17:06No data—
Mon 12 OctApeldoorn De Maten 17:06Partial coverage0 min—
Sun 11 OctApeldoorn De Maten 17:06No data—
Sat 10 OctApeldoorn De Maten 17:060 min—
Fri 9 OctApeldoorn De Maten 17:06Partial coverage0 min—
Thu 8 OctApeldoorn De Maten 17:06No data—
Wed 7 OctApeldoorn De Maten 17:06Partial coverage0 min—
Tue 6 OctApeldoorn De Maten 17:06Partial coverage+3 min+3 min