Train Arriva 30466 Zutphen – Apeldoorn

Zutphen 21:05 → Apeldoorn 21:17 Daily 0 h 12 min · 2 stops Arriva

✓ Today’s run finished

Today, last fix heading to — at 21:19 No data

  1. Zutphen21:05
  2. Apeldoorn21:17

Next service: tomorrow 21:05 from Zutphen · Fri 6 Nov

Next departure 21:05 tomorrow · Zutphen
On-time · 30 days
83%
10/12 runs under 3 min
RT coverage: 8 full · 4 partial · 11 no data
On-time · 90 days
83%
10/12 runs under 3 min
RT coverage: 8 full · 4 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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 23 Oct Max en route +13 min · last fix heading to — +12 min
  • Mon 2 Nov Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 12 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
21:05on time on time
21:17on time +8 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
Thu 5 Nov— 21:19No data—
Wed 4 Nov— 21:190 min—
Mon 2 Nov— 21:24+6 min+6 min
Sun 1 NovZutphen 21:19Partial coverage0 min—
Sat 31 OctZutphen 21:21No data—
Fri 30 Oct— 21:20No data—
Wed 28 Oct— 21:280 min—
Sun 25 OctZutphen 21:21No data—
Sat 24 OctZutphen 21:21No data—
Fri 23 Oct— 21:32+12 min+13 min
Thu 22 Oct— 21:22No data—
Wed 21 Oct— 21:22No data—
Sun 18 OctZutphen 21:21Partial coverage+1 min—
Sat 17 OctZutphen 21:20No data—
Thu 15 Oct— 21:22No data—
Wed 14 Oct— 21:21No data—
Tue 13 Oct— 21:25No data—
Mon 12 Oct— 21:230 min—
Sun 11 OctZutphen 21:20Partial coverage+1 min+1 min
Sat 10 OctZutphen 21:21Partial coverage+1 min—
Fri 9 Oct— 21:200 min—
Thu 8 Oct— 21:200 min—
Wed 7 Oct— 21:190 min—
Sun 4 OctZutphen 21:20No data—
Sat 3 OctZutphen 21:19No data—
Sun 27 SeptZutphen 21:19No data—
Sat 26 SeptZutphen 21:19No data—
Sun 20 SeptZutphen 21:19No data—
Sat 19 SeptZutphen 21:19No data—
Sun 6 SeptZutphen 21:19No data—