Train RRReis A 17834 Zutphen – Apeldoorn

Zutphen 13:06 → Apeldoorn 13: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 13:34 No data

  1. Zutphen13:06
  2. Voorst-Empe13:10
  3. Klarenbeek13:15
  4. Apeldoorn De Maten13:22
  5. Apeldoorn13:25

Next service: tomorrow 13:06 from Zutphen · Fri 6 Nov

Next departure 13:06 tomorrow · Zutphen
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 0 full · 7 partial · 15 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 55 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

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

  • Early 0% · 0
  • On time 100% · 8
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 8 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
13:06on time on time
13:10— —
13:15 / 13:16— —
13:22— —
13: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
Thu 5 NovApeldoorn De Maten 13:34No data—
Wed 4 NovApeldoorn De Maten 13:34Partial coverage0 min+1 min
Tue 3 NovApeldoorn De Maten 13:34No data—
Mon 2 NovApeldoorn De Maten 13:34No data—
Fri 30 OctApeldoorn De Maten 13:36No data—
Thu 29 OctApeldoorn De Maten 13:36No data—
Wed 28 OctApeldoorn De Maten 13:36Partial coverage0 min—
Tue 27 OctApeldoorn De Maten 13:36Partial coverage0 min—
Mon 26 OctApeldoorn De Maten 13:36No data—
Fri 23 OctApeldoorn De Maten 13:36No data—
Thu 22 OctApeldoorn De Maten 13:36No data—
Wed 21 OctApeldoorn De Maten 13:36No data—
Tue 20 OctApeldoorn De Maten 13:36Partial coverage0 min—
Mon 19 OctApeldoorn De Maten 13:36Partial coverage0 min—
Fri 16 OctApeldoorn De Maten 13:36No data—
Thu 15 OctApeldoorn De Maten 13:36No data—
Wed 14 OctApeldoorn De Maten 13:36No data—
Tue 13 OctApeldoorn De Maten 13:36No data—
Mon 12 OctApeldoorn De Maten 13:36No data—
Fri 9 OctApeldoorn De Maten 13:36Partial coverage0 min—
Thu 8 OctApeldoorn De Maten 13:36Partial coverage0 min—
Wed 7 OctApeldoorn De Maten 13:36No data—
Tue 6 OctApeldoorn De Maten 13:36No data—
Mon 5 OctApeldoorn De Maten 13:36Partial coverage0 min—
Fri 2 OctApeldoorn De Maten 13:36No data—
Thu 1 OctApeldoorn De Maten 13:36No data—
Wed 30 SeptApeldoorn De Maten 13:36No data—
Tue 29 SeptApeldoorn De Maten 13:36No data—
Mon 28 SeptApeldoorn De Maten 13:36No data—
Fri 25 SeptApeldoorn De Maten 13:36No data—