Train RRReis A 17810 Zutphen – Apeldoorn

Zutphen 07:06 → Apeldoorn 07:25 Mon, Tue, Wed, Thu, Fri 0 h 19 min · 5 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Apeldoorn De Maten at 07:34 No data

  1. Zutphen07:06
  2. Voorst-Empe07:10
  3. Klarenbeek07:15
  4. Apeldoorn De Maten07:22
  5. Apeldoorn07:25

Next service: Monday 07:06 from Zutphen · Mon 9 Nov

Next departure 07:06 Monday · Zutphen
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 0 full · 18 partial · 4 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 0 full · 20 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Thu 15 Oct Max en route +12 min · last fix heading to Apeldoorn De Maten +12 min
  • Wed 14 Oct Max en route +4 min · last fix heading to Apeldoorn De Maten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 18
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=5
  • 80% W n=5
  • 75% T n=4
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 20 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
07:06on time on time
07:10— —
07:15 / 07:16— —
07:22— —
07:25— —

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 NovApeldoorn De Maten 07:34No data—
Thu 5 NovApeldoorn De Maten 07:34No data—
Wed 4 NovApeldoorn De Maten 07:34Partial coverage+2 min+2 min
Tue 3 NovApeldoorn De Maten 07:34Partial coverage0 min—
Mon 2 NovApeldoorn De Maten 07:34No data—
Fri 30 OctApeldoorn De Maten 07:36Partial coverage0 min—
Thu 29 OctApeldoorn De Maten 07:36Partial coverage0 min—
Wed 28 OctApeldoorn De Maten 07:36Partial coverage0 min—
Tue 27 OctApeldoorn De Maten 07:36Partial coverage0 min—
Mon 26 OctApeldoorn De Maten 07:36No data—
Fri 23 OctApeldoorn De Maten 07:36Partial coverage0 min—
Thu 22 OctApeldoorn De Maten 07:36Partial coverage0 min—
Wed 21 OctApeldoorn De Maten 07:36Partial coverage0 min—
Tue 20 OctApeldoorn De Maten 07:37Partial coverage0 min—
Mon 19 OctApeldoorn De Maten 07:36Partial coverage0 min—
Fri 16 OctApeldoorn De Maten 07:36Partial coverage0 min—
Thu 15 OctApeldoorn De Maten 07:43Partial coverage+12 min+12 min
Wed 14 OctApeldoorn De Maten 07:40Partial coverage+3 min+4 min
Tue 13 OctApeldoorn De Maten 07:36Partial coverage0 min—
Mon 12 OctApeldoorn De Maten 07:37Partial coverage0 min—
Fri 9 OctApeldoorn De Maten 07:37Partial coverage+1 min+1 min
Thu 8 OctApeldoorn De Maten 07:37Partial coverage+1 min+1 min
Wed 7 OctApeldoorn De Maten 07:37Partial coverage0 min—
Tue 6 OctApeldoorn De Maten 07:36Partial coverage0 min—
Mon 5 OctApeldoorn De Maten 07:37No data—
Fri 2 OctApeldoorn De Maten 07:36No data—
Thu 1 OctApeldoorn De Maten 07:36No data—
Wed 30 SeptApeldoorn De Maten 07:42No data—
Tue 29 SeptApeldoorn De Maten 07:36No data—
Mon 28 SeptApeldoorn De Maten 07:36No data—