Train Blauwnet K 8518 Kampen – Zwolle

Kampen 06:30 → Zwolle 06:41 Mon, Tue, Wed, Thu, Fri 0 h 11 min · 3 stops Blauwnet K

✓ Today’s run finished

Today, last fix heading to Zwolle Stadshagen at 06:49 0 min

  1. Kampen06:30
  2. Zwolle Stadshagen06:37
  3. Zwolle06:41

Next service: Monday 06:30 from Kampen · Mon 23 Nov

Next departure 06:30 Monday · Kampen
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 0 full · 18 partial · 4 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 4 full · 22 partial · 38 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Mon 19 Oct Max en route +6 min · last fix heading to Zwolle Stadshagen +6 min
  • Mon 16 Nov Max en route +4 min · last fix heading to Zwolle Stadshagen +4 min
  • Thu 12 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

  • 60% M n=5
  • 100% T n=7
  • 100% W n=6
  • 75% T n=4
  • 100% F n=4
  • — S n=0
  • — S n=0

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
06:30on time on time
06:37— —
06:41— —

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 06:49Partial coverage0 min—
Thu 19 NovZwolle Stadshagen 06:49Partial coverage0 min—
Wed 18 NovZwolle Stadshagen 06:52Partial coverage+1 min—
Tue 17 NovZwolle Stadshagen 06:52Partial coverage+1 min—
Mon 16 NovZwolle Stadshagen 06:54Partial coverage+4 min+4 min
Fri 13 NovZwolle Stadshagen 06:52Partial coverage+1 min+1 min
Thu 12 NovZwolle Stadshagen 06:54Partial coverage+4 min+4 min
Wed 11 NovZwolle Stadshagen 06:49Partial coverage0 min—
Tue 10 NovZwolle Stadshagen 06:53Partial coverage+2 min+2 min
Mon 9 NovZwolle Stadshagen 06:52Partial coverage+1 min—
Fri 6 NovZwolle Stadshagen 06:52No data—
Thu 5 NovZwolle Stadshagen 06:52No data—
Wed 4 NovZwolle Stadshagen 06:49Partial coverage0 min—
Tue 3 NovZwolle Stadshagen 06:49Partial coverage0 min—
Mon 2 NovZwolle Stadshagen 06:52No data—
Fri 30 OctZwolle Stadshagen 06:51Partial coverage0 min—
Thu 29 OctZwolle Stadshagen 06:51Partial coverage0 min—
Wed 28 OctZwolle Stadshagen 06:51Partial coverage0 min—
Tue 27 OctZwolle Stadshagen 06:51Partial coverage0 min—
Mon 26 OctZwolle Stadshagen 06:51Partial coverage0 min—
Fri 23 OctZwolle Stadshagen 06:51Partial coverage0 min—
Thu 22 OctZwolle Stadshagen 06:51No data—
Wed 21 OctZwolle Stadshagen 06:51Partial coverage0 min—
Tue 20 OctZwolle Stadshagen 06:51Partial coverage0 min—
Mon 19 OctZwolle Stadshagen 06:57+6 min+6 min
Fri 16 OctZwolle Stadshagen 06:51No data—
Thu 15 OctZwolle Stadshagen 06:52+1 min—
Wed 14 OctZwolle Stadshagen 06:51No data—
Tue 13 OctZwolle Stadshagen 06:510 min—
Mon 12 OctZwolle Stadshagen 06:510 min—