Train Blauwnet K 17915 Zwolle – Enschede

Zwolle 06:42 → Enschede 07:29 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 +6 min

Next service: today 06:42 from Zwolle · Thu 5 Nov

Next departure 06:42 today · Zwolle
On-time · 30 days
68%
13/19 runs under 3 min
RT coverage: 4 full · 15 partial · 2 no data
On-time · 90 days
65%
13/20 runs under 3 min
RT coverage: 4 full · 16 partial · 42 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Tue 6 Oct Max en route +7 min · last fix heading to Hengelo +7 min
  • Fri 9 Oct Max en route +7 min · last fix heading to Hengelo +7 min
  • Wed 4 Nov Max en route +6 min · last fix heading to Hengelo +6 min
  • Fri 30 Oct Max en route +8 min · last fix heading to Hengelo +6 min
  • Fri 23 Oct Max en route +6 min · last fix heading to Hengelo +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 65% · 13
  • 3–10 min 35% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 80% T n=5
  • 75% W n=4
  • 75% T n=4
  • 25% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 20 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
06:42on time on time
06:52— —
07:00 / 07:01— —
07:09 / 07:10— —
07:21 / 07:22— —
07: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
Wed 4 NovHengelo 07:42Partial coverage+6 min+6 min
Tue 3 NovHengelo 07:37Partial coverage+1 min+1 min
Mon 2 NovHengelo 07:37No data—
Fri 30 OctHengelo 07:42Partial coverage+6 min+8 min
Thu 29 OctHengelo 07:37Partial coverage+1 min+1 min
Wed 28 OctHengelo 07:37Partial coverage+1 min—
Tue 27 OctHengelo 07:36Partial coverage0 min—
Mon 26 OctHengelo 07:37Partial coverage+3 min+3 min
Fri 23 OctHengelo 07:40Partial coverage+4 min+6 min
Thu 22 OctHengelo 07:39Partial coverage+3 min+3 min
Wed 21 OctHengelo 07:36Partial coverage0 min—
Tue 20 OctHengelo 07:36Partial coverage+1 min—
Mon 19 OctHengelo 07:36Partial coverage+1 min—
Fri 16 OctHengelo 07:360 min—
Thu 15 OctHengelo 07:360 min—
Wed 14 OctHengelo 07:36No data—
Tue 13 OctHengelo 07:37+1 min+1 min
Mon 12 OctHengelo 07:38+2 min+2 min
Fri 9 OctHengelo 07:41Partial coverage+7 min+7 min
Thu 8 OctHengelo 07:36Partial coverage+1 min+1 min
Wed 7 OctHengelo 07:37Partial coverage+2 min+2 min
Tue 6 OctHengelo 07:36Partial coverage+7 min+7 min
Mon 5 OctHengelo 07:37No data—
Fri 2 OctHengelo 07:36No data—
Thu 1 OctHengelo 07:36No data—
Wed 30 SeptHengelo 07:38No data—
Tue 29 SeptHengelo 07:36No data—
Mon 28 SeptHengelo 07:38No data—
Fri 25 SeptHengelo 07:36No data—
Thu 24 SeptHengelo 07:36No data—