Train Blauwnet K 8528 Kampen → Zwolle

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

Blauwnet K 8528 Kampen–Zwolle: final delay under 3 min on 19 of its 19 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 23 Nov 2026, 00:24 (GMT+1).

It has not run yet today

Last recorded run: Sunday 22 November +1 min

Next service: today 09:02 from Kampen · Mon 23 Nov

Next departure 09:02 today · Kampen
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 13 full · 6 partial · 10 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 15 full · 9 partial · 63 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 24
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 100% W n=4
  • 100% T n=2
  • 100% F n=2
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

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