Train Blauwnet K 7964 Enschede – Zwolle

Enschede 17:04 → Zwolle 18:09 Daily 1 h 05 min · 11 stops Blauwnet K

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 17:04 from Enschede · Wed 18 Nov

Next departure 17:04 today · Enschede
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 2 full · 15 partial · 12 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 5 full · 23 partial · 60 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: +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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 28
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 28 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
17:04on time on time
17:08≈ on time ≈ on time
17:12 / 17:16≈ on time ≈ on time
17:21≈ on time ≈ on time
17:27≈ on time ≈ on time
17:30≈ on time ≈ on time
17:34 / 17:36≈ on time ≈ on time
17:41 / 17:43≈ on time ≈ on time
17:50 / 17:54≈ on time ≈ on time
17:58 / 18:00≈ on time ≈ on time
18:09on time on time

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