Train Blauwnet K 7931 Zwolle – Enschede

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

✓ Today’s run finished

Today, last fix heading to Enschede Kennispark at 12:04 +1 min

  1. Zwolle10:52
  2. Raalte11:05
  3. Nijverdal11:16
  4. Almelo11:29
  5. Borne11:38
  6. Enschede Kennispark11:51
  7. Enschede11:56

Next service: tomorrow 10:52 from Zwolle · Sat 21 Nov

Next departure 10:52 tomorrow · Zwolle
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 1 full · 19 partial · 10 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 1 full · 27 partial · 60 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

  • Fri 9 Oct Max en route +5 min · last fix heading to Enschede Kennispark +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 27
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=5
  • 100% W n=5
  • 100% T n=3
  • 67% F n=3
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 28 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
10:52on time on time
10:59 / 11:01— —
11:05 / 11:09— —
11:16 / 11:19— —
11:25— —
11:29 / 11:30— —
11:33— —
11:38— —
11:43 / 11:47— —
11:51— —
11: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
Fri 20 NovEnschede Kennispark 12:04Partial coverage+1 min—
Thu 19 NovEnschede Kennispark 12:07Partial coverage+2 min+2 min
Wed 18 NovEnschede Kennispark 12:07Partial coverage+2 min+2 min
Tue 17 NovEnschede Kennispark 12:04Partial coverage+1 min—
Mon 16 NovEnschede Kennispark 12:08Partial coverage+2 min+2 min
Sun 15 NovEnschede Kennispark 12:04Partial coverage0 min—
Sat 14 NovEnschede Kennispark 12:04Partial coverage0 min—
Fri 13 NovEnschede Kennispark 12:04Partial coverage0 min—
Thu 12 NovEnschede Kennispark 12:04Partial coverage0 min—
Wed 11 NovEnschede Kennispark 12:04Partial coverage+1 min—
Tue 10 NovEnschede Kennispark 12:04Partial coverage+1 min—
Mon 9 NovEnschede Kennispark 12:08Partial coverage+2 min+3 min
Sun 8 NovEnschede Kennispark 12:04Partial coverage0 min—
Sat 7 NovEnschede Kennispark 12:04Partial coverage0 min—
Fri 6 NovEnschede Kennispark 12:04No data—
Thu 5 NovEnschede Kennispark 12:04No data—
Wed 4 NovEnschede Kennispark 12:04Partial coverage+1 min—
Tue 3 NovEnschede Kennispark 12:04No data—
Mon 2 NovEnschede Kennispark 12:04No data—
Sun 1 NovEnschede Kennispark 12:06Partial coverage0 min—
Sat 31 OctEnschede Kennispark 12:05Partial coverage0 min—
Fri 30 OctEnschede Kennispark 12:06No data—
Thu 29 OctEnschede Kennispark 12:06No data—
Wed 28 OctEnschede Kennispark 12:05Partial coverage0 min—
Tue 27 OctEnschede Kennispark 12:07Partial coverage0 min—
Mon 26 OctEnschede Kennispark 12:06No data—
Sun 25 OctWierden 11:36No data—
Sat 24 OctWierden 11:37+3 min+3 min
Fri 23 OctEnschede Kennispark 12:06No data—
Thu 22 OctEnschede Kennispark 12:06No data—