Train Arriva 8583 Zwolle – Kampen

Zwolle 23:47 → Kampen 23:58 Daily 0 h 11 min · 3 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 23:47 from Zwolle · Thu 5 Nov

Next departure 23:47 today · Zwolle
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 9 full · 3 partial · 7 no data
On-time · 90 days
92%
11/12 runs under 3 min
RT coverage: 9 full · 3 partial · 19 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Kampen, 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 +4 min · last fix heading to — +4 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 92% · 11
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • 100% W n=2
  • 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 (3 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
23:47on time +2 min
23:51≈ on time ≈ +3 min
23:58on 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
Wed 4 Nov— 23:590 min—
Tue 3 Nov— 23:590 min—
Mon 2 Nov— 00:02+1 min+1 min
Sun 1 NovZwolle Stadshagen 00:04Partial coverage+1 min—
Sun 25 OctZwolle Stadshagen 00:05No data—
Sat 24 Oct— 00:01No data—
Fri 23 Oct— 23:590 min—
Thu 22 Oct— 00:01No data—
Tue 20 Oct— 00:02No data—
Mon 19 Oct— 00:000 min—
Sun 18 OctZwolle Stadshagen 00:05Partial coverage0 min—
Sat 17 OctZwolle Stadshagen 00:05No data—
Tue 13 Oct— 00:04No data—
Mon 12 Oct— 00:01No data—
Sun 11 OctZwolle Stadshagen 00:06Partial coverage0 min—
Sat 10 Oct— 00:04+2 min+2 min
Fri 9 Oct— 00:05+4 min+4 min
Thu 8 Oct— 00:010 min—
Wed 7 Oct— 00:03+3 min+3 min
Tue 6 Oct— 00:01No data—
Sun 4 OctZwolle Stadshagen 00:05No data—
Sat 3 OctZwolle Stadshagen 23:54No data—
Sun 27 SeptZwolle Stadshagen 00:05No data—
Sun 20 SeptZwolle Stadshagen 00:06No data—
Sun 13 SeptZwolle Stadshagen 00:05No data—
Sun 6 SeptZwolle Stadshagen 00:06No data—
Sun 30 AugZwolle Stadshagen 00:05No data—
Sun 23 AugZwolle Stadshagen 00:06No data—
Sat 22 AugZwolle Stadshagen 00:05No data—
Sun 16 AugZwolle Stadshagen 00:05No data—