Train Blauwnet K 8524 Kampen → Zwolle

Kampen 08:00 → Zwolle 08:11 Daily 0 h 11 min · 3 stops Blauwnet K

It has not run yet today

Last recorded run: Friday 20 November +1 min

Next service: today 08:00 from Kampen · Sat 21 Nov

Next departure 08:00 today · Kampen
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 5 full · 14 partial · 10 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 7 full · 19 partial · 61 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Tue 10 Nov Max en route +4 min · last fix heading to Zwolle Stadshagen +4 min
  • Thu 19 Nov Max en route +4 min · last fix heading to Zwolle Stadshagen +4 min
  • Mon 9 Nov Max en route +4 min · last fix heading to Zwolle Stadshagen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 23
  • 3–10 min 12% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 80% T n=5
  • 100% W n=4
  • 67% T n=3
  • 100% F n=3
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 26 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
08:00on time on time
08:07≈ on time ≈ on time
08:11on time on time

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 NovZwolle Stadshagen 08:22Partial coverage+1 min—
Thu 19 NovZwolle Stadshagen 08:24Partial coverage+4 min+4 min
Wed 18 NovZwolle Stadshagen 08:22Partial coverage+1 min—
Tue 17 NovZwolle Stadshagen 08:22Partial coverage+2 min+2 min
Mon 16 NovZwolle Stadshagen 08:24Partial coverage+2 min+2 min
Sun 15 NovZwolle Stadshagen 08:24+1 min—
Sat 14 NovZwolle Stadshagen 08:230 min—
Fri 13 NovZwolle Stadshagen 08:23Partial coverage+2 min+2 min
Thu 12 NovZwolle Stadshagen 08:19Partial coverage0 min—
Wed 11 NovZwolle Stadshagen 08:24Partial coverage+3 min+3 min
Tue 10 NovZwolle Stadshagen 08:24Partial coverage+4 min+4 min
Mon 9 NovZwolle Stadshagen 08:24Partial coverage+4 min+4 min
Sun 8 NovZwolle Stadshagen 08:230 min—
Sat 7 NovZwolle Stadshagen 08:230 min—
Fri 6 NovZwolle Stadshagen 08:34No data—
Thu 5 NovZwolle Stadshagen 08:19No data—
Wed 4 NovZwolle Stadshagen 08:22Partial coverage+1 min—
Tue 3 NovZwolle Stadshagen 08:19No data—
Mon 2 NovZwolle Stadshagen 08:22No data—
Sun 1 NovZwolle Stadshagen 08:23No data—
Sat 31 OctZwolle Stadshagen 08:23No data—
Fri 30 OctZwolle Stadshagen 08:22No data—
Thu 29 OctZwolle Stadshagen 08:22No data—
Wed 28 OctZwolle Stadshagen 08:21Partial coverage0 min—
Tue 27 OctZwolle Stadshagen 08:22Partial coverage0 min—
Mon 26 OctZwolle Stadshagen 08:21Partial coverage0 min—
Sun 25 OctZwolle Stadshagen 08:23No data—
Sat 24 OctZwolle Stadshagen 08:230 min—
Fri 23 OctZwolle Stadshagen 08:26No data—
Thu 22 OctZwolle Stadshagen 08:21No data—