Train Arriva 8580 Kampen – Zwolle

Kampen 22:02 → Zwolle 22:13 Daily 0 h 11 min · 3 stops Arriva

✓ Today’s run finished

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

  1. Kampen22:02
  2. Zwolle Stadshagen22:09
  3. Zwolle22:13

Next service: tomorrow 22:02 from Kampen · Sat 7 Nov

Next departure 22:02 tomorrow · Kampen
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 8 full · 2 partial · 11 no data
On-time · 90 days
90%
9/10 runs under 3 min
RT coverage: 8 full · 2 partial · 30 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: +3 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

  • Sun 11 Oct Max en route +4 min · last fix heading to Zwolle Stadshagen +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 10 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:02on time on time
22:09≈ on time ≈ +1 min
22:13on time +2 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 6 Nov— 22:180 min—
Thu 5 Nov— 22:14No data—
Wed 4 Nov— 22:140 min—
Tue 3 Nov— 22:14No data—
Mon 2 Nov— 22:14+1 min—
Sun 1 NovZwolle Stadshagen 22:23No data—
Sat 31 OctZwolle Stadshagen 22:23No data—
Sun 25 OctZwolle Stadshagen 22:23No data—
Sat 24 OctZwolle Stadshagen 22:20No data—
Fri 23 Oct— 22:160 min—
Thu 22 Oct— 22:16No data—
Wed 21 Oct— 22:16No data—
Mon 19 Oct— 22:150 min—
Sun 18 OctZwolle Stadshagen 22:23No data—
Sat 17 OctZwolle Stadshagen 22:23No data—
Tue 13 Oct— 22:18No data—
Mon 12 Oct— 22:150 min—
Sun 11 OctZwolle Stadshagen 22:27Partial coverage+4 min+4 min
Sat 10 OctKampen 22:16Partial coverage0 min—
Fri 9 Oct— 22:18+3 min+3 min
Thu 8 Oct— 22:150 min—
Wed 7 Oct— 22:15No data—
Tue 6 Oct— 22:15No data—
Sun 4 OctZwolle Stadshagen 22:24No data—
Sat 3 OctZwolle Stadshagen 22:23No data—
Sun 27 SeptZwolle Stadshagen 22:23No data—
Sat 26 SeptZwolle Stadshagen 22:23No data—
Sun 20 SeptZwolle Stadshagen 22:31No data—
Sat 19 SeptZwolle Stadshagen 22:23No data—
Sun 13 SeptZwolle Stadshagen 22:23No data—