Train Blauwnet K 17951 Zwolle – Enschede

Zwolle 15:42 → Enschede 16:29 Mon, Tue, Wed, Thu, Fri 0 h 47 min · 6 stops Blauwnet K

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 15:42 from Zwolle · Mon 9 Nov

Next departure 15:42 Monday · Zwolle
On-time · 30 days
86%
6/7 runs under 3 min
RT coverage: 0 full · 7 partial · 13 no data
On-time · 90 days
82%
9/11 runs under 3 min
RT coverage: 0 full · 11 partial · 52 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 Enschede, 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 Hengelo +7 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Hengelo +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 9
  • 3–10 min 18% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=3
  • 67% W n=3
  • 100% T n=1
  • 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, 11 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
15:42on time on time
15:52— —
16:00 / 16:01— —
16:09 / 16:10— —
16:21 / 16:22— —
16:29— —

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 NovHengelo 16:34No data—
Thu 5 NovHengelo 16:37No data—
Wed 4 NovHengelo 16:38Partial coverage+3 min+3 min
Tue 3 NovHengelo 16:34No data—
Mon 2 NovHengelo 16:34No data—
Fri 30 OctHengelo 16:37No data—
Thu 29 OctHengelo 16:36No data—
Wed 28 OctHengelo 16:36Partial coverage0 min—
Tue 27 OctHengelo 16:39Partial coverage0 min—
Mon 26 OctHengelo 16:36No data—
Fri 23 OctHengelo 16:36No data—
Thu 22 OctHengelo 16:38No data—
Wed 21 OctHengelo 16:36No data—
Tue 20 OctHengelo 16:45Partial coverage0 min—
Mon 19 OctHengelo 16:37Partial coverage0 min—
Fri 16 OctHengelo 16:39No data—
Thu 15 OctHengelo 16:37No data—
Tue 13 OctHengelo 16:42No data—
Mon 12 OctHengelo 16:36Partial coverage0 min—
Fri 9 OctHengelo 16:39Partial coverage+3 min+5 min
Thu 8 OctHengelo 16:36Partial coverage0 min—
Wed 7 OctHengelo 16:36Partial coverage0 min—
Tue 6 OctHengelo 16:36Partial coverage0 min—
Mon 5 OctHengelo 16:43Partial coverage+7 min+7 min
Fri 2 OctHengelo 16:36No data—
Thu 1 OctHengelo 16:36No data—
Wed 30 SeptHengelo 16:36No data—
Tue 29 SeptHengelo 16:37No data—
Mon 28 SeptHengelo 16:37No data—
Fri 25 SeptHengelo 16:36No data—