Train Blauwnet K 17923 Zwolle – Enschede

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

✓ Today’s run finished

Today, last fix heading to Hengelo at 09:37 No data

  1. Zwolle08:42
  2. Raalte08:52
  3. Nijverdal09:00
  4. Almelo09:09
  5. Hengelo09:21
  6. Enschede09:29

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

Next departure 08:42 Monday · Zwolle
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 13 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 53 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 Enschede, 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

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

  • Early 0% · 0
  • On time 100% · 10
  • 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=3
  • 100% 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, 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
08:42on time on time
08:52— —
09:00 / 09:01— —
09:09 / 09:10— —
09:21 / 09:22— —
09: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 09:37No data—
Thu 5 NovHengelo 09:37No data—
Wed 4 NovHengelo 09:37Partial coverage0 min—
Tue 3 NovHengelo 09:43No data—
Mon 2 NovHengelo 09:37Partial coverage0 min—
Fri 30 OctHengelo 09:36No data—
Thu 29 OctHengelo 09:36Partial coverage0 min—
Wed 28 OctHengelo 09:38Partial coverage0 min—
Tue 27 OctHengelo 09:37Partial coverage0 min—
Mon 26 OctHengelo 09:37No data—
Fri 23 OctHengelo 09:37No data—
Thu 22 OctHengelo 09:41No data—
Wed 21 OctHengelo 09:36No data—
Tue 20 OctHengelo 09:41Partial coverage0 min—
Mon 19 OctHengelo 09:39Partial coverage0 min—
Fri 16 OctHengelo 09:36No data—
Thu 15 OctHengelo 09:36No data—
Tue 13 OctHengelo 09:36No data—
Mon 12 OctHengelo 09:37No data—
Fri 9 OctHengelo 09:38Partial coverage+1 min+2 min
Thu 8 OctHengelo 09:36Partial coverageNo data—
Wed 7 OctHengelo 09:37Partial coverage+1 min+1 min
Tue 6 OctHengelo 09:36Partial coverage0 min—
Mon 5 OctHengelo 09:39No data—
Fri 2 OctHengelo 09:37No data—
Thu 1 OctHengelo 09:38No data—
Wed 30 SeptHengelo 09:41No data—
Tue 29 SeptHengelo 09:37No data—
Mon 28 SeptHengelo 09:36No data—
Fri 25 SeptHengelo 09:36No data—