Train Arriva 17858 Zutphen – Apeldoorn

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 19:06 from Zutphen · Fri 6 Nov

Next departure 19:06 today · Zutphen
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 7 full · 1 partial · 11 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 8 full · 1 partial · 24 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 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 9 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
19:06on time on time
19:10≈ on time ≈ on time
19:15 / 19:16≈ on time ≈ on time
19:22≈ on time ≈ on time
19:25on time on time

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 Nov— 19:28No data—
Wed 4 Nov— 19:290 min—
Mon 2 Nov— 19:29No data—
Fri 30 Oct— 19:28No data—
Thu 29 Oct— 19:290 min—
Wed 28 Oct— 19:28No data—
Tue 27 Oct— 19:310 min—
Mon 26 Oct— 19:26No data—
Fri 23 OctApeldoorn De Maten 19:36Partial coverage+2 min+2 min
Thu 22 Oct— 19:28No data—
Wed 21 Oct— 19:30No data—
Mon 19 Oct— 19:280 min—
Fri 16 OctApeldoorn De Maten 19:36No data—
Thu 15 Oct— 19:27No data—
Wed 14 OctApeldoorn De Maten 19:36No data—
Tue 13 Oct— 19:28No data—
Mon 12 Oct— 19:280 min—
Fri 9 Oct— 19:280 min—
Thu 8 Oct— 19:290 min—
Wed 7 Oct— 19:27No data—
Mon 5 Oct— 19:280 min—
Fri 28 AugApeldoorn De Maten 19:36No data—
Wed 26 AugZutphen 19:20No data—
Fri 21 AugApeldoorn De Maten 19:36No data—
Thu 20 AugVoorst-Empe 19:24No data—
Wed 19 AugApeldoorn De Maten 19:36No data—
Tue 18 AugKlarenbeek 19:30No data—
Mon 17 AugApeldoorn De Maten 19:32No data—
Fri 14 AugApeldoorn De Maten 19:36No data—
Thu 13 AugApeldoorn De Maten 19:32No data—