Train Blauwnet K 7958 Enschede – Zwolle

Enschede 15:34 → Zwolle 16:39 Daily 1 h 05 min · 11 stops Blauwnet K

✓ Today’s run finished

Today, last fix heading to Heino at 16:44 0 min

  1. Enschede15:34
  2. Hengelo15:43
  3. Borne15:51
  4. Almelo16:00
  5. Nijverdal16:12
  6. Heino16:28
  7. Zwolle16:39

Next service: tomorrow 15:34 from Enschede · Thu 19 Nov

Next departure 15:34 tomorrow · Enschede
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 7 full · 11 partial · 12 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 9 full · 18 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Thu 8 Oct Max en route +8 min · last fix heading to Heino +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 100% W n=5
  • 67% T n=3
  • 100% F n=2
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 27 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:34on time on time
15:38≈ on time ≈ on time
15:43 / 15:46≈ on time ≈ on time
15:51≈ on time ≈ on time
15:57≈ on time ≈ on time
16:00≈ on time ≈ on time
16:04 / 16:07≈ on time ≈ on time
16:12 / 16:16≈ on time ≈ on time
16:23 / 16:24≈ on time ≈ on time
16:28 / 16:30≈ on time ≈ on time
16:39on time +1 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 16:44Partial coverage0 min—
Tue 17 NovHeino 16:44Partial coverage0 min—
Mon 16 NovHeino 16:45Partial coverage0 min—
Sun 15 NovHeino 16:440 min—
Sat 14 NovHeino 16:440 min—
Fri 13 NovHeino 16:44Partial coverage0 min+2 min
Thu 12 NovHeino 16:44Partial coverage0 min—
Wed 11 NovHeino 16:44Partial coverage0 min—
Tue 10 NovHeino 16:44Partial coverage0 min+2 min
Mon 9 NovHeino 16:44Partial coverage0 min—
Sun 8 NovHeino 16:450 min—
Sat 7 NovHeino 16:440 min—
Fri 6 NovHeino 16:44No data—
Thu 5 NovHeino 16:49No data—
Wed 4 NovHeino 16:44Partial coverage0 min—
Tue 3 NovHeino 16:44No data—
Mon 2 NovHeino 16:44No data—
Sun 1 NovHeino 16:450 min—
Sat 31 OctHeino 16:440 min—
Fri 30 OctHeino 16:44No data—
Thu 29 OctHeino 16:45Partial coverage0 min—
Wed 28 OctHeino 16:45Partial coverage0 min—
Tue 27 OctHeino 16:44No data—
Mon 26 OctHeino 16:44No data—
Sun 25 OctHeino 16:44No data—
Sat 24 OctHeino 16:440 min—
Fri 23 OctHeino 16:44No data—
Thu 22 OctHeino 16:45No data—
Wed 21 OctHeino 16:47No data—
Tue 20 OctHeino 16:45No data—