Train Blauwnet K 8584 Kampen – Zwolle

Kampen 23:02 → Zwolle 23:13 Daily 0 h 11 min · 3 stops Blauwnet K

It has not run yet today

Last recorded run: Saturday 7 November +1 min

Next service: today 23:02 from Kampen · Sun 8 Nov

Next departure 23:02 today · Kampen
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 8 full · 1 partial · 11 no data
On-time · 90 days
91%
10/11 runs under 3 min
RT coverage: 10 full · 1 partial · 27 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: 0 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 +6 min · last fix heading to — +6 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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