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

Blauwnet K 7924 Enschede–Zwolle: final delay under 3 min on 21 of its 22 runs with data in the last 30 days (95%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 00:26 (GMT+1).

It does not run today

Last recorded run: Saturday 21 November 0 min

Next service: tomorrow 07:04 from Enschede · Mon 23 Nov

Next departure 07:04 tomorrow · Enschede
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 1 full · 21 partial · 3 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 1 full · 33 partial · 41 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: +1 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 +5 min · last fix heading to Heino +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 33
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 83% T n=6
  • 100% W n=6
  • 100% T n=5
  • 100% F n=6
  • 100% S n=7
  • — S n=0

Stops and timetable

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

Last 90 days, 34 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
Sat 21 NovHeino 08:14Partial coverage0 min—
Fri 20 NovHeino 08:14Partial coverage0 min—
Thu 19 NovHeino 08:14Partial coverage0 min—
Wed 18 NovHeino 08:14Partial coverage+1 min+1 min
Tue 17 NovHeino 08:17Partial coverage+2 min+2 min
Mon 16 NovHeino 08:14Partial coverage0 min—
Sat 14 NovHeino 08:14Partial coverage0 min—
Fri 13 NovHeino 08:14Partial coverage0 min—
Thu 12 NovHeino 08:14Partial coverage0 min—
Wed 11 NovHeino 08:14Partial coverage0 min—
Tue 10 NovHeino 08:18Partial coverage+4 min+5 min
Mon 9 NovHeino 08:14Partial coverage0 min—
Sat 7 NovHeino 08:14Partial coverage0 min—
Fri 6 NovHeino 08:14No data—
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—