Train Blauwnet K 8544 Kampen – Zwolle

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

✓ Today’s run finished

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

  1. Kampen13:02
  2. Zwolle Stadshagen13:09
  3. Zwolle13:13

Next service: tomorrow 13:02 from Kampen · Sat 21 Nov

Next departure 13:02 tomorrow · Kampen
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 0 full · 17 partial · 13 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 0 full · 24 partial · 64 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

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=2
  • 100% T n=5
  • 100% W n=4
  • 100% 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, 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
13:02on time on time
13:09— —
13:13— —

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