Train Blauwnet K 17962 Enschede – Zwolle

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 16:31 from Enschede · Thu 5 Nov

Next departure 16:31 today · Enschede
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 12 no data
On-time · 90 days
90%
9/10 runs under 3 min
RT coverage: 0 full · 10 partial · 51 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: 0 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 5 Oct Max en route +7 min · last fix heading to Raalte +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 9
  • 3–10 min 10% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 10 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
16:31on time on time
16:38 / 16:39— —
16:49 / 16:50— —
16:59 / 17:00— —
17:08— —
17: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
Wed 4 NovRaalte 17:22No data—
Tue 3 NovRaalte 17:22Partial coverage0 min—
Mon 2 NovRaalte 17:22Partial coverage0 min—
Fri 30 OctRaalte 17:22No data—
Thu 29 OctRaalte 17:22Partial coverage0 min—
Wed 28 OctRaalte 17:22Partial coverage0 min—
Tue 27 OctRaalte 17:25No data—
Mon 26 OctRaalte 17:22No data—
Fri 23 OctRaalte 17:25No data—
Thu 22 OctRaalte 17:28No data—
Wed 21 OctRaalte 17:23No data—
Tue 20 OctRaalte 17:22No data—
Mon 19 OctRaalte 17:22Partial coverage0 min—
Fri 16 OctRaalte 17:23No data—
Thu 15 OctRaalte 17:21No data—
Tue 13 OctRaalte 17:24No data—
Mon 12 OctRaalte 17:22Partial coverage0 min—
Fri 9 OctRaalte 17:22Partial coverage0 min—
Thu 8 OctRaalte 17:22Partial coverage0 min—
Wed 7 OctRaalte 17:22No data—
Tue 6 OctRaalte 17:22Partial coverage0 min—
Mon 5 OctRaalte 17:27Partial coverage+6 min+7 min
Fri 2 OctRaalte 17:23No data—
Thu 1 OctRaalte 17:22No data—
Wed 30 SeptRaalte 17:22No data—
Tue 29 SeptRaalte 17:22No data—
Mon 28 SeptRaalte 17:22No data—
Fri 25 SeptRaalte 17:22No data—
Thu 24 SeptRaalte 17:19No data—
Wed 23 SeptRaalte 17:22No data—