Train RRReis A 17827 Apeldoorn – Zutphen

Apeldoorn 10:07 → Zutphen 10:25 Daily 0 h 18 min · 5 stops RRReis A

✓ Today’s run finished

Today, last fix heading to Voorst-Empe at 10:34 0 min

  1. Apeldoorn10:07
  2. Apeldoorn De Maten10:10
  3. Klarenbeek10:16
  4. Voorst-Empe10:20
  5. Zutphen10:25

Next service: tomorrow 10:07 from Apeldoorn · Sun 8 Nov

Next departure 10:07 tomorrow · Apeldoorn
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 6 full · 8 partial · 16 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 7 full · 8 partial · 72 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 Zutphen, 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 Voorst-Empe +7 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 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
10:07on time on time
10:10≈ on time ≈ on time
10:16≈ on time ≈ on time
10:20≈ on time ≈ +1 min
10:25on time +1 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 NovVoorst-Empe 10:34Partial coverage0 min—
Fri 6 NovVoorst-Empe 10:34No data—
Thu 5 NovVoorst-Empe 10:34No data—
Wed 4 NovVoorst-Empe 10:340 min—
Tue 3 NovVoorst-Empe 10:34No data—
Mon 2 NovVoorst-Empe 10:34No data—
Sun 1 NovVoorst-Empe 10:35Partial coverage0 min—
Sat 31 OctVoorst-Empe 10:35Partial coverage+1 min—
Fri 30 OctVoorst-Empe 10:34No data—
Thu 29 OctVoorst-Empe 10:34No data—
Wed 28 OctVoorst-Empe 10:340 min—
Tue 27 OctVoorst-Empe 10:340 min—
Mon 26 OctVoorst-Empe 10:34No data—
Sun 25 OctVoorst-Empe 10:36No data—
Sat 24 OctVoorst-Empe 10:37Partial coverage+2 min+3 min
Fri 23 OctVoorst-Empe 10:34No data—
Thu 22 OctVoorst-Empe 10:34No data—
Wed 21 OctVoorst-Empe 10:34No data—
Tue 20 OctVoorst-Empe 10:340 min—
Mon 19 OctVoorst-Empe 10:340 min—
Sun 18 OctVoorst-Empe 10:35Partial coverage+7 min+7 min
Sat 17 OctVoorst-Empe 10:35Partial coverage0 min—
Fri 16 OctVoorst-Empe 10:34No data—
Thu 15 OctVoorst-Empe 10:35No data—
Wed 14 OctVoorst-Empe 10:34No data—
Tue 13 OctVoorst-Empe 10:34No data—
Mon 12 OctVoorst-Empe 10:34No data—
Sun 11 OctVoorst-Empe 10:34Partial coverage0 min—
Sat 10 OctVoorst-Empe 10:37Partial coverage+2 min+3 min
Fri 9 OctVoorst-Empe 10:35+2 min+2 min