Train Blauwnet K 8521 Zwolle – Kampen

Zwolle 08:15 → Kampen 08:26 Daily 0 h 11 min · 3 stops Blauwnet K

✓ Today’s run finished

Today, last fix heading to Zwolle Stadshagen at 08:33 No data

  1. Zwolle08:15
  2. Zwolle Stadshagen08:19
  3. Kampen08:26

Next service: tomorrow 08:15 from Zwolle · Fri 6 Nov

Full trip card
Next departure 08:15 tomorrow · Zwolle
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 3 full · 5 partial · 21 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 3 full · 5 partial · 80 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 Kampen, 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

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

  • Early 0% · 0
  • On time 100% · 8
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 100% W n=2
  • — T n=0
  • — F n=0
  • 100% S n=2
  • 100% S n=1

Stops and timetable

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

Last 90 days, 8 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
Zwolle
08:15on time on time
Zwolle Stadshagen
08:19— —
Kampen
08:26— —

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