Train Blauwnet K 8561 Zwolle – Kampen

Zwolle 18:19 → Kampen 18:30 Daily 0 h 11 min · 3 stops Blauwnet K

✓ Today’s run finished

Today, last fix heading to Zwolle Stadshagen at 18:37 +1 min

  1. Zwolle18:19
  2. Zwolle Stadshagen18:23
  3. Kampen18:30

Next service: tomorrow 18:19 from Zwolle · Sat 7 Nov

Next departure 18:19 tomorrow · Zwolle
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 4 full · 5 partial · 18 no data
On-time · 90 days
100%
9/9 runs under 3 min
RT coverage: 4 full · 5 partial · 56 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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

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

Stops and timetable

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

Last 90 days, 9 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
18:19on time on time
18:23— —
18:30— —

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