Train Arriva 8590 Kampen – Zwolle

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

✓ Today’s run finished

Today, last fix heading to — at 00:48 +1 min

  1. Kampen00:32
  2. Zwolle Stadshagen00:39
  3. Zwolle00:43

Next service: tomorrow 00:32 from Kampen · Sun 8 Nov

Full trip card
Next departure 00:32 tomorrow · Kampen
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 11 full · 2 partial · 6 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 12 full · 2 partial · 17 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sat 10 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
Kampen
00:32on time on time
Zwolle Stadshagen
00:39≈ on time ≈ +1 min
Zwolle
00:43on time +1 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
Sat 7 Nov— 00:48+1 min—
Fri 6 Nov— 00:44No data—
Thu 5 Nov— 00:440 min—
Wed 4 Nov— 00:440 min—
Tue 3 Nov— 00:440 min—
Mon 2 NovZwolle Stadshagen 00:54Partial coverage0 min—
Mon 26 OctZwolle Stadshagen 00:53No data—
Sun 25 Oct— 00:46No data—
Sat 24 Oct— 00:470 min—
Fri 23 Oct— 00:46No data—
Tue 20 Oct— 00:450 min—
Mon 19 OctZwolle Stadshagen 00:54Partial coverage0 min—
Sun 18 OctZwolle Stadshagen 00:53No data—
Wed 14 Oct— 00:46No data—
Tue 13 Oct— 00:460 min—
Mon 12 OctZwolle Stadshagen 00:530 min—
Sun 11 Oct— 00:480 min—
Sat 10 Oct— 00:50+3 min+3 min
Fri 9 Oct— 00:460 min—
Thu 8 Oct— 00:46+1 min—
Wed 7 Oct— 00:46No data—
Mon 5 OctZwolle Stadshagen 00:53No data—
Sun 4 OctKampen 00:46No data—
Mon 28 SeptZwolle Stadshagen 00:55No data—
Mon 21 SeptZwolle Stadshagen 00:54No data—
Mon 14 SeptZwolle Stadshagen 00:53No data—
Mon 7 SeptZwolle Stadshagen 00:54No data—
Mon 31 AugZwolle Stadshagen 00:53No data—
Mon 24 AugZwolle Stadshagen 00:53No data—
Mon 17 AugZwolle Stadshagen 00:59No data—