Train Blauwnet K 7913 Zwolle – Enschede

Zwolle 06:22 → Enschede 07:26 Mon, Tue, Wed, Thu, Fri, Sat 1 h 04 min · 11 stops Blauwnet K

Running now · updated 06:25

Heading to Enschede No data

Estimated arrival at Enschede 07:26 · 83 km/h

  1. Zwolle06:22
  2. Raalte06:35
  3. Nijverdal06:43
  4. Almelo06:59
  5. Borne07:08
  6. Hengelo07:13
  7. Enschede07:26
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 3 full · 18 partial · 4 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 3 full · 20 partial · 52 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 Enschede, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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 10Today
06:22on time on time
06:29 / 06:31— —
06:35 / 06:36— —
06:43 / 06:47— —
06:52 / 06:55— —
06:59 / 07:00— —
07:03— —
07:08— —
07:13 / 07:17— —
07:21— —
07:26— —

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
Fri 6 NovHeino 06:24No data—
Thu 5 NovEnschede Kennispark 07:34No data—
Wed 4 NovEnschede Kennispark 07:37Partial coverage+3 min+3 min
Tue 3 NovEnschede Kennispark 07:34Partial coverage0 min—
Mon 2 NovEnschede Kennispark 07:34Partial coverage0 min—
Sat 31 OctEnschede Kennispark 07:360 min—
Fri 30 OctEnschede Kennispark 07:36Partial coverage+1 min—
Thu 29 OctEnschede Kennispark 07:37Partial coverage+3 min+3 min
Wed 28 OctEnschede Kennispark 07:36Partial coverage0 min—
Tue 27 OctEnschede Kennispark 07:36Partial coverage0 min—
Mon 26 OctEnschede Kennispark 07:37Partial coverage+2 min+2 min
Fri 23 OctEnschede Kennispark 07:37Partial coverage+2 min+2 min
Thu 22 OctEnschede Kennispark 07:36No data—
Wed 21 OctEnschede Kennispark 07:37Partial coverage0 min—
Tue 20 OctEnschede Kennispark 07:37Partial coverage0 min—
Mon 19 OctEnschede Kennispark 07:37Partial coverage0 min—
Sat 17 OctEnschede Kennispark 07:360 min—
Fri 16 OctEnschede Kennispark 07:36Partial coverage0 min—
Thu 15 OctEnschede Kennispark 07:36Partial coverage0 min—
Wed 14 OctBorne 07:22Partial coverageNo data—
Tue 13 OctEnschede Kennispark 07:36Partial coverage0 min—
Mon 12 OctEnschede Kennispark 07:35Partial coverage0 min—
Sat 10 OctEnschede Kennispark 07:370 min—
Fri 9 OctEnschede Kennispark 07:36Partial coverage+1 min—
Thu 8 OctEnschede Kennispark 07:36Partial coverage+1 min—
Wed 7 OctEnschede Kennispark 07:37Partial coverage+1 min+2 min
Tue 6 OctEnschede Kennispark 07:36Partial coverage+2 min+2 min
Mon 5 OctEnschede Kennispark 07:37No data—
Sat 3 OctEnschede Kennispark 07:37No data—
Fri 2 OctEnschede Kennispark 07:36No data—