Train Blauwnet K 7951 Zwolle – Enschede

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

✓ Today’s run finished

Today, last fix heading to Enschede Kennispark at 17:04 No data

  1. Zwolle15:52
  2. Raalte16:05
  3. Nijverdal16:16
  4. Almelo16:29
  5. Borne16:38
  6. Enschede Kennispark16:51
  7. Enschede16:56

Next service: tomorrow 15:52 from Zwolle · Fri 6 Nov

Next departure 15:52 tomorrow · Zwolle
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 2 full · 12 partial · 15 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 2 full · 14 partial · 72 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

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

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

On-time by weekday

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

Stops and timetable

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

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