Train Blauwnet K 7922 Enschede – Zwolle

Enschede 06:34 → Zwolle 07:39 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 07:44 0 min

  1. Enschede06:34
  2. Hengelo06:42
  3. Borne06:51
  4. Almelo07:00
  5. Nijverdal07:12
  6. Heino07:28
  7. Zwolle07:39

Next service: Monday 06:34 from Enschede · Mon 9 Nov

Next departure 06:34 Monday · Enschede
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 19 full · 4 partial · 3 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 22 full · 4 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Fri 23 Oct Max en route +5 min · last fix heading to Heino +5 min
  • Fri 30 Oct Max en route +5 min · last fix heading to Heino +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 24
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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