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:44 0 min

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

Next service: tomorrow 09:34 from Enschede · Mon 9 Nov

Next departure 09:34 tomorrow · Enschede
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 6 full · 8 partial · 15 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 10 full · 8 partial · 70 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=1
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 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, 18 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:42 / 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
Sun 8 NovHeino 10:44Partial coverage0 min—
Sat 7 NovHeino 10:44Partial coverage0 min—
Fri 6 NovHeino 10:44No data—
Thu 5 NovHeino 10:44No data—
Wed 4 NovHeino 10:440 min—
Tue 3 NovHeino 10:44No data—
Mon 2 NovHeino 10:44No data—
Sun 1 NovHeino 10:45Partial coverage0 min—
Sat 31 OctHeino 10:44Partial coverage0 min—
Fri 30 OctHeino 10:46No data—
Thu 29 OctHeino 10:46No data—
Wed 28 OctHeino 10:440 min—
Tue 27 OctHeino 10:440 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:460 min—
Mon 19 OctHeino 10:440 min—
Sun 18 OctHeino 10:44Partial coverage0 min—
Sat 17 OctHeino 10:44Partial coverage0 min—
Fri 16 OctHeino 10:44No data—
Thu 15 OctHeino 10:44No data—
Tue 13 OctHeino 10:44No data—
Mon 12 OctHeino 10:49No data—
Sun 11 OctHeino 10:44Partial coverage0 min—
Sat 10 OctHeino 10:44Partial coverage0 min—
Fri 9 OctHeino 10:440 min—