Train Blauwnet K 7924 Enschede – Zwolle

Enschede 07:04 → Zwolle 08:09 Mon, Tue, Wed, Thu, Fri, Sat 1 h 05 min · 11 stops Blauwnet K

✓ Today’s run finished

Today, last fix heading to Heino at 08:22 No data

  1. Enschede07:04
  2. Hengelo07:12
  3. Borne07:21
  4. Almelo07:30
  5. Nijverdal07:41
  6. Heino07:58
  7. Zwolle08:09

Next service: tomorrow 07:04 from Enschede · Fri 6 Nov

Next departure 07:04 tomorrow · Enschede
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 1 full · 19 partial · 5 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 1 full · 20 partial · 54 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 100% W n=4
  • 100% T n=3
  • 100% F n=4
  • 100% S n=4
  • — S n=0

Stops and timetable

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

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

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