Train Arriva 17875 Apeldoorn – Zutphen

Apeldoorn 22:01 → Zutphen 22:23 Daily 0 h 22 min · 5 stops Arriva

✓ Today’s run finished

Today, last fix heading to — at 22:24 0 min

  1. Apeldoorn22:01
  2. Apeldoorn De Maten22:04
  3. Klarenbeek22:10
  4. Voorst-Empe22:18
  5. Zutphen22:23

Next service: tomorrow 22:01 from Apeldoorn · Sat 21 Nov

Next departure 22:01 tomorrow · Apeldoorn
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 14 full · 4 partial · 9 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 19 full · 6 partial · 25 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: +1 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=4
  • 100% T n=4
  • 100% F n=5
  • 100% S n=2
  • 100% S n=4

Stops and timetable

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

Last 90 days, 25 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:01on time on time
22:04≈ on time ≈ on time
22:10 / 22:13≈ on time ≈ +1 min
22:18≈ on time ≈ +1 min
22:23on 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
Fri 20 Nov— 22:240 min—
Thu 19 Nov— 22:240 min—
Wed 18 Nov— 22:240 min—
Mon 16 Nov— 22:240 min—
Sun 15 NovVoorst-Empe 22:32Partial coverage0 min—
Sat 14 NovVoorst-Empe 22:32Partial coverage0 min—
Thu 12 Nov— 22:24+1 min+1 min
Wed 11 Nov— 22:230 min—
Tue 10 Nov— 22:27+2 min+2 min
Mon 9 Nov— 22:240 min—
Sun 8 NovVoorst-Empe 22:32Partial coverage0 min—
Sat 7 NovVoorst-Empe 22:32No data—
Fri 6 Nov— 22:240 min—
Thu 5 Nov— 22:24No data—
Wed 4 Nov— 22:240 min—
Tue 3 Nov— 22:24No data—
Mon 2 Nov— 22:240 min—
Sun 1 NovVoorst-Empe 22:32Partial coverage0 min—
Sat 31 OctVoorst-Empe 22:32No data—
Fri 30 Oct— 22:24No data—
Thu 29 Oct— 22:250 min—
Wed 28 Oct— 22:240 min—
Mon 26 Oct— 22:26No data—
Sun 25 OctVoorst-Empe 22:32No data—
Sat 24 OctVoorst-Empe 22:32No data—
Fri 23 Oct— 22:28+2 min+3 min
Thu 22 Oct— 22:26No data—
Wed 21 Oct— 22:25No data—
Tue 20 Oct— 22:260 min—
Mon 19 Oct— 22:240 min—