Train Arriva 17876 Zutphen – Apeldoorn

Zutphen 23:37 → Apeldoorn 23:56 Daily 0 h 19 min · 5 stops Arriva

It has not run yet today

Last recorded run: Friday 20 November +7 min

Next service: today 23:37 from Zutphen · Sat 21 Nov

Next departure 23:37 today · Zutphen
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 15 full · 3 partial · 6 no data
On-time · 90 days
85%
23/27 runs under 3 min
RT coverage: 22 full · 5 partial · 19 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Fri 20 Nov Max en route +8 min · last fix heading to — +7 min
  • Mon 19 Oct Max en route +7 min · last fix heading to — +7 min
  • Sun 18 Oct Max en route +6 min · last fix heading to Apeldoorn De Maten +5 min
  • Wed 11 Nov Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 23
  • 3–10 min 15% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=1
  • 83% W n=6
  • 100% T n=4
  • 80% F n=5
  • 100% S n=1
  • 80% S n=5

Stops and timetable

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

Last 90 days, 27 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
23:37on time +3 min
23:41≈ on time ≈ +2 min
23:46≈ on time ≈ +2 min
23:52≈ on time ≈ +3 min
23:56on time +3 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— 00:04+7 min+8 min
Thu 19 Nov— 23:59+2 min+2 min
Wed 18 Nov— 23:59+2 min+3 min
Mon 16 Nov— 23:59+1 min—
Sun 15 NovApeldoorn De Maten 00:07Partial coverage0 min—
Thu 12 Nov— 23:580 min—
Wed 11 Nov— 00:02+4 min+5 min
Tue 10 Nov— 23:58No data—
Mon 9 Nov— 23:590 min—
Sun 8 NovApeldoorn De Maten 00:04Partial coverage0 min—
Fri 6 Nov— 23:570 min—
Thu 5 Nov— 23:59No data—
Wed 4 Nov— 23:590 min—
Tue 3 Nov— 23:590 min—
Mon 2 Nov— 23:580 min—
Sun 1 NovApeldoorn De Maten 00:04Partial coverage0 min—
Sat 31 Oct— 23:57No data—
Fri 30 Oct— 00:03No data—
Thu 29 Oct— 23:59+1 min—
Wed 28 Oct— 00:010 min—
Mon 26 Oct— 00:010 min—
Sun 25 OctApeldoorn De Maten 00:07No data—
Sat 24 Oct— 00:08No data—
Fri 23 Oct— 00:00+2 min+2 min
Thu 22 Oct— 00:00No data—
Wed 21 Oct— 23:58No data—
Tue 20 Oct— 00:00No data—
Mon 19 Oct— 00:05+7 min+7 min
Sun 18 OctApeldoorn De Maten 00:12Partial coverage+5 min+6 min
Sat 17 OctApeldoorn De Maten 00:07No data—