Train Blauwnet K 17966 Enschede – Zwolle

Enschede 17:31 → Zwolle 18:18 Mon, Tue, Wed, Thu, Fri 0 h 47 min · 6 stops Blauwnet K

It has not run yet today

Last recorded run: Monday 9 November +1 min

Next service: today 17:31 from Enschede · Tue 10 Nov

Next departure 17:31 today · Enschede
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 1 full · 8 partial · 11 no data
On-time · 90 days
86%
12/14 runs under 3 min
RT coverage: 2 full · 12 partial · 47 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: +1 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

  • Fri 9 Oct Max en route +5 min · last fix heading to Raalte +5 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Nijverdal +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 12
  • 3–10 min 14% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=3
  • 50% T n=2
  • 50% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 14 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
17:31on time +1 min
17:38 / 17:39— —
17:49 / 17:50— —
17:59 / 18:00— —
18:08— —
18:18— —

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
Mon 9 NovRaalte 18:22Partial coverage+1 min+2 min
Fri 6 NovRaalte 18:22Partial coverage0 min—
Thu 5 NovRaalte 18:22No data—
Wed 4 NovRaalte 18:22Partial coverage0 min—
Tue 3 NovRaalte 18:22No data—
Mon 2 NovRaalte 18:22No data—
Fri 30 OctRaalte 18:22No data—
Thu 29 OctNijverdal 18:14No data—
Wed 28 OctRaalte 18:22Partial coverage0 min—
Tue 27 OctNijverdal 18:14No data—
Mon 26 OctRaalte 18:22Partial coverage+1 min+1 min
Fri 23 OctRaalte 18:23No data—
Thu 22 OctRaalte 18:22No data—
Wed 21 OctRaalte 18:22No data—
Tue 20 OctRaalte 18:22Partial coverage0 min—
Mon 19 OctRaalte 18:22Partial coverage0 min—
Fri 16 OctRaalte 18:22No data—
Thu 15 OctRaalte 18:220 min—
Tue 13 OctRaalte 18:22No data—
Mon 12 OctRaalte 18:22Partial coverage0 min—
Fri 9 OctRaalte 18:22Partial coverage+5 min+5 min
Thu 8 OctNijverdal 18:14+4 min+5 min
Wed 7 OctRaalte 18:22Partial coverage+2 min+2 min
Tue 6 OctNijverdal 18:14Partial coverage0 min—
Mon 5 OctRaalte 18:22Partial coverage0 min—
Fri 2 OctRaalte 18:22No data—
Thu 1 OctNijverdal 18:15No data—
Wed 30 SeptRaalte 18:18No data—
Tue 29 SeptNijverdal 18:14No data—
Mon 28 SeptNijverdal 18:14No data—