Train Blauwnet K 8568 Kampen – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Zwolle Stadshagen at 19:23 0 min

  1. Kampen19:02
  2. Zwolle Stadshagen19:09
  3. Zwolle19:13

Next service: tomorrow 19:02 from Kampen · Sun 8 Nov

Next departure 19:02 tomorrow · Kampen
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 6 full · 4 partial · 16 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 6 full · 4 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 10
  • 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=1
  • — W n=0
  • — T n=0
  • 100% F n=2
  • 100% S n=2
  • 100% S n=2

Stops and timetable

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

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