Train Blauwnet K 8519 Zwolle → Kampen

Zwolle 07:47 → Kampen 07:58 Daily 0 h 11 min · 3 stops Blauwnet K

Running now · updated 07:52

Heading to Kampen 0 min

Estimated arrival at Kampen 07:58 · 99 km/h

  1. Zwolle07:47
  2. Zwolle Stadshagen07:51
  3. Kampen07:58

Today it is running no worse than usual: typical arrival delay is +1 min; 80% of the last 20 runs arrived on time.

On-time · 30 days
80%
16/20 runs under 3 min
RT coverage: 14 full · 6 partial · 10 no data
On-time · 90 days
85%
23/27 runs under 3 min
RT coverage: 19 full · 8 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: +3 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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 23
  • 3–10 min 15% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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 10Today
07:47on time +1 min
07:51≈ on time ≈ +2 min
07:58+1 min +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
Sat 21 NovZwolle Stadshagen 07:49Partial coverage0 min—
Fri 20 NovZwolle Stadshagen 08:040 min—
Thu 19 NovZwolle Stadshagen 08:04+3 min+3 min
Wed 18 NovZwolle Stadshagen 08:030 min—
Tue 17 NovZwolle Stadshagen 08:04+1 min+1 min
Mon 16 NovZwolle Stadshagen 08:04+2 min+2 min
Sun 15 NovZwolle Stadshagen 08:07Partial coverage+2 min+2 min
Sat 14 NovZwolle Stadshagen 08:04Partial coverage0 min—
Fri 13 NovZwolle Stadshagen 08:04+3 min+3 min
Thu 12 NovZwolle Stadshagen 08:04+1 min+1 min
Wed 11 NovZwolle Stadshagen 08:04+3 min+3 min
Tue 10 NovZwolle Stadshagen 08:07+4 min+4 min
Mon 9 NovZwolle Stadshagen 08:04+3 min+3 min
Sun 8 NovZwolle Stadshagen 08:04Partial coverage0 min—
Sat 7 NovZwolle Stadshagen 08:05Partial coverage0 min—
Fri 6 NovZwolle Stadshagen 08:07No data—
Thu 5 NovZwolle Stadshagen 08:03No data—
Wed 4 NovZwolle Stadshagen 08:030 min—
Tue 3 NovZwolle Stadshagen 08:03No data—
Mon 2 NovZwolle Stadshagen 08:04No data—
Sun 1 NovZwolle Stadshagen 08:05No data—
Sat 31 OctZwolle Stadshagen 08:05No data—
Fri 30 OctZwolle Stadshagen 08:03No data—
Thu 29 OctZwolle Stadshagen 08:03No data—
Wed 28 OctZwolle Stadshagen 08:030 min—
Tue 27 OctZwolle Stadshagen 08:030 min—
Mon 26 OctZwolle Stadshagen 08:03No data—
Sun 25 OctZwolle Stadshagen 08:05No data—
Sat 24 OctZwolle Stadshagen 08:05Partial coverage0 min—
Fri 23 OctZwolle Stadshagen 08:07+3 min+3 min