Train Blauwnet K 7934 Enschede – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Heino at 10:45 +1 min

  1. Enschede09:34
  2. Hengelo09:43
  3. Borne09:51
  4. Almelo10:00
  5. Nijverdal10:12
  6. Heino10:28
  7. Zwolle10:39

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

Next departure 09:34 tomorrow · Enschede
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 7 full · 12 partial · 11 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 12 full · 16 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

Worst days

  • Tue 10 Nov Max en route +6 min · last fix heading to Heino +4 min

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 96% · 27
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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