Train Blauwnet K 7943 Zwolle – Enschede

Zwolle 13:52 → Enschede 14:56 Daily 1 h 04 min · 11 stops Blauwnet K

It has not run yet today

Last recorded run: Thursday 19 November +4 min

Next service: today 13:52 from Zwolle · Fri 20 Nov

Next departure 13:52 today · Zwolle
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 1 full · 20 partial · 8 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 2 full · 28 partial · 57 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

Worst days

  • Thu 19 Nov Max en route +4 min · last fix heading to Enschede Kennispark +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=6
  • 100% W n=5
  • 75% T n=4
  • 100% F n=2
  • 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, 30 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
13:52on time on time
13:59 / 14:01— —
14:05 / 14:09— —
14:16 / 14:19— —
14:25— —
14:29 / 14:30— —
14:33— —
14:38— —
14:43 / 14:47— —
14:51— —
14:56— —

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 19 NovEnschede Kennispark 15:08Partial coverage+4 min+4 min
Wed 18 NovEnschede Kennispark 15:04Partial coverage0 min—
Tue 17 NovEnschede Kennispark 15:04Partial coverage+2 min+2 min
Mon 16 NovEnschede Kennispark 15:05Partial coverage+3 min+3 min
Sun 15 NovEnschede Kennispark 15:07Partial coverage+2 min+2 min
Sat 14 NovEnschede Kennispark 15:04Partial coverage+1 min—
Fri 13 NovEnschede Kennispark 15:04Partial coverage0 min—
Thu 12 NovEnschede Kennispark 15:04Partial coverage0 min—
Wed 11 NovEnschede Kennispark 15:04Partial coverage0 min—
Tue 10 NovEnschede Kennispark 15:04Partial coverage0 min+1 min
Mon 9 NovEnschede Kennispark 15:04Partial coverage0 min—
Sun 8 NovEnschede Kennispark 15:04Partial coverage+1 min—
Sat 7 NovEnschede Kennispark 15:04Partial coverage0 min—
Fri 6 NovEnschede Kennispark 15:04No data—
Thu 5 NovEnschede Kennispark 15:04No data—
Wed 4 NovEnschede Kennispark 15:04Partial coverage+1 min+1 min
Tue 3 NovEnschede Kennispark 15:04Partial coverage0 min—
Mon 2 NovEnschede Kennispark 15:04No data—
Sun 1 NovEnschede Kennispark 15:06Partial coverage0 min—
Sat 31 OctEnschede Kennispark 15:06Partial coverage0 min—
Fri 30 OctEnschede Kennispark 15:06No data—
Thu 29 OctEnschede Kennispark 15:05Partial coverage0 min—
Wed 28 OctEnschede Kennispark 15:05Partial coverage0 min—
Tue 27 OctEnschede Kennispark 15:06Partial coverage0 min—
Mon 26 OctEnschede Kennispark 15:06No data—
Sun 25 OctWierden 14:36No data—
Sat 24 OctWierden 14:360 min—
Fri 23 OctEnschede Kennispark 15:06No data—
Thu 22 OctEnschede Kennispark 15:05No data—
Wed 21 OctEnschede Kennispark 15:06No data—