Train Blauwnet K 7916 Enschede – Zwolle

Enschede 05:06 → Zwolle 06:09 Mon, Tue, Wed, Thu, Fri 1 h 03 min · 11 stops Blauwnet K

✓ Today’s run finished

Today, last fix heading to Heino at 06:17 +2 min

  1. Enschede05:06
  2. Hengelo05:15
  3. Borne05:21
  4. Almelo05:30
  5. Nijverdal05:41
  6. Heino05:58
  7. Zwolle06:09

Next service: tomorrow 05:06 from Enschede · Thu 19 Nov

Next departure 05:06 tomorrow · Enschede
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 16 full · 5 partial · 1 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 24 full · 6 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Tue 10 Nov Max en route +3 min · last fix heading to Heino +3 min
  • Fri 13 Nov Max en route +3 min · last fix heading to Heino +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 28
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 86% T n=7
  • 100% W n=6
  • 100% T n=6
  • 80% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 30 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
05:06on time on time
05:11≈ on time ≈ on time
05:15 / 05:16≈ on time ≈ on time
05:21≈ on time ≈ on time
05:27≈ on time ≈ +1 min
05:30≈ on time ≈ +1 min
05:34 / 05:36≈ on time ≈ +1 min
05:41 / 05:43≈ on time ≈ +1 min
05:50 / 05:54≈ on time ≈ +1 min
05:58 / 06:00≈ on time ≈ +2 min
06:09on time +2 min

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 18 NovHeino 06:17Partial coverage+2 min+3 min
Tue 17 NovHeino 06:140 min—
Mon 16 NovHeino 06:140 min—
Fri 13 NovHeino 06:17+3 min+3 min
Thu 12 NovHeino 06:140 min—
Wed 11 NovHeino 06:14Partial coverage0 min—
Tue 10 NovHeino 06:17+3 min+3 min
Mon 9 NovHeino 06:14+2 min+2 min
Fri 6 NovHeino 06:14No data—
Thu 5 NovHeino 06:140 min—
Wed 4 NovHeino 06:14Partial coverage0 min—
Tue 3 NovHeino 06:140 min—
Mon 2 NovHeino 06:140 min—
Fri 30 OctHeino 06:150 min—
Thu 29 OctHeino 06:140 min—
Wed 28 OctHeino 06:15Partial coverage+1 min—
Tue 27 OctHeino 06:150 min—
Mon 26 OctHeino 06:17+2 min+2 min
Fri 23 OctHeino 06:150 min—
Thu 22 OctHeino 06:140 min—
Wed 21 OctHeino 06:14Partial coverage0 min—
Tue 20 OctHeino 06:140 min—
Mon 19 OctHeino 06:140 min—
Fri 16 OctHeino 06:140 min—
Thu 15 OctHeino 06:140 min—
Wed 14 OctHeino 06:14No data—
Tue 13 OctHeino 06:16+1 min+2 min
Mon 12 OctHeino 06:140 min—
Fri 9 OctHeino 06:150 min—
Thu 8 OctHeino 06:140 min—