Train Arriva 8586 Kampen → Zwolle

Kampen 23:32 → Zwolle 23:43 Daily 0 h 11 min · 3 stops Arriva

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 23:32 from Kampen · Sat 21 Nov

Next departure 23:32 today · Kampen
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 9 full · 2 partial · 5 no data
On-time · 90 days
82%
14/17 runs under 3 min
RT coverage: 15 full · 2 partial · 21 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Zwolle, 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 9 Oct Max en route +5 min · last fix heading to — +5 min
  • Sat 10 Oct Max en route +4 min · last fix heading to — +4 min
  • Fri 6 Nov Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 14
  • 3–10 min 18% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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:32on time +2 min
23:39≈ on time ≈ +3 min
23:43on 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— 23:440 min—
Thu 19 Nov— 23:470 min—
Sun 15 NovZwolle Stadshagen 23:54Partial coverage+1 min+1 min
Sat 14 Nov— 23:440 min—
Fri 13 Nov— 23:47+1 min+1 min
Sun 8 NovZwolle Stadshagen 23:54No data—
Sat 7 Nov— 23:470 min—
Fri 6 Nov— 23:49+3 min+3 min
Thu 5 Nov— 23:47No data—
Wed 4 Nov— 23:440 min—
Tue 3 Nov— 23:47No data—
Mon 2 Nov— 23:47+2 min+2 min
Sun 1 NovZwolle Stadshagen 23:54Partial coverage+1 min—
Sun 25 OctZwolle Stadshagen 23:53No data—
Sat 24 Oct— 23:46No data—
Fri 23 Oct— 23:470 min—
Thu 22 Oct— 23:46No data—
Tue 20 Oct— 23:46No data—
Mon 19 Oct— 23:460 min—
Sun 18 OctZwolle Stadshagen 23:53No data—
Sat 17 OctZwolle Stadshagen 23:53No data—
Tue 13 Oct— 23:50No data—
Mon 12 Oct— 23:460 min—
Sun 11 OctZwolle Stadshagen 23:53No data—
Sat 10 Oct— 23:50+4 min+4 min
Fri 9 Oct— 23:51+5 min+5 min
Thu 8 Oct— 23:410 min—
Wed 7 Oct— 23:49+3 min+3 min
Tue 6 Oct— 23:45No data—
Sun 4 OctZwolle Stadshagen 23:54No data—