Train Blauwnet K 8526 Kampen → Zwolle

Kampen 08:32 → Zwolle 08:43 Daily 0 h 11 min · 3 stops Blauwnet K

✓ Today’s run finished

Today, last fix heading to Zwolle Stadshagen at 08:53 0 min

  1. Kampen08:32
  2. Zwolle Stadshagen08:39
  3. Zwolle08:43

Next service: tomorrow 08:32 from Kampen · Sun 22 Nov

Next departure 08:32 tomorrow · Kampen
On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 13 full · 6 partial · 11 no data
On-time · 90 days
85%
22/26 runs under 3 min
RT coverage: 18 full · 8 partial · 62 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: +3 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

  • Thu 19 Nov Max en route +4 min · last fix heading to Zwolle Stadshagen +4 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Zwolle Stadshagen +4 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Zwolle Stadshagen +3 min
  • Wed 11 Nov Max en route +3 min · last fix heading to Zwolle Stadshagen +3 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 85% · 22
  • 3–10 min 15% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 80% T n=5
  • 75% W n=4
  • 67% T n=3
  • 100% F n=3
  • 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, 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
08:32on time on time
08:39≈ on time ≈ +3 min
08:43on time +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 08:53Partial coverage0 min—
Fri 20 NovZwolle Stadshagen 08:490 min—
Thu 19 NovZwolle Stadshagen 08:54+4 min+4 min
Wed 18 NovZwolle Stadshagen 08:490 min—
Tue 17 NovZwolle Stadshagen 08:52+1 min+1 min
Mon 16 NovZwolle Stadshagen 08:53+2 min+2 min
Sun 15 NovZwolle Stadshagen 08:53Partial coverage0 min—
Sat 14 NovZwolle Stadshagen 08:53Partial coverage0 min—
Fri 13 NovZwolle Stadshagen 08:52+1 min+1 min
Thu 12 NovZwolle Stadshagen 08:52+1 min—
Wed 11 NovZwolle Stadshagen 08:54+3 min+3 min
Tue 10 NovZwolle Stadshagen 08:54+4 min+4 min
Mon 9 NovZwolle Stadshagen 08:54+3 min+3 min
Sun 8 NovZwolle Stadshagen 08:54Partial coverage+2 min+2 min
Sat 7 NovZwolle Stadshagen 08:53Partial coverage0 min—
Fri 6 NovZwolle Stadshagen 09:04No data—
Thu 5 NovZwolle Stadshagen 08:49No data—
Wed 4 NovZwolle Stadshagen 08:520 min—
Tue 3 NovZwolle Stadshagen 08:49No data—
Mon 2 NovZwolle Stadshagen 08:49No data—
Sun 1 NovZwolle Stadshagen 08:53No data—
Sat 31 OctZwolle Stadshagen 08:53No data—
Fri 30 OctZwolle Stadshagen 08:52No data—
Thu 29 OctZwolle Stadshagen 08:52No data—
Wed 28 OctZwolle Stadshagen 08:520 min—
Tue 27 OctZwolle Stadshagen 08:510 min—
Mon 26 OctZwolle Stadshagen 08:51No data—
Sun 25 OctZwolle Stadshagen 08:53No data—
Sat 24 OctZwolle Stadshagen 08:53Partial coverage0 min—
Fri 23 OctZwolle Stadshagen 08:58No data—