Train Blauwnet K 7927 Zwolle – Enschede

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

✓ Today’s run finished

Today, last fix heading to Enschede Kennispark at 11:05 0 min

  1. Zwolle09:52
  2. Raalte10:05
  3. Nijverdal10:16
  4. Almelo10:29
  5. Borne10:38
  6. Enschede Kennispark10:51
  7. Enschede10:56

Next service: tomorrow 09:52 from Zwolle · Mon 16 Nov

Next departure 09:52 tomorrow · Zwolle
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 12 full · 7 partial · 11 no data
On-time · 90 days
96%
24/25 runs under 3 min
RT coverage: 16 full · 9 partial · 63 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Tue 10 Nov Max en route +3 min · last fix heading to Enschede Kennispark +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=2
  • 75% T n=4
  • 100% W n=4
  • 100% T n=3
  • 100% F n=2
  • 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, 25 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
09:52on time on time
09:59 / 10:01≈ on time ≈ on time
10:05 / 10:09≈ on time ≈ on time
10:16 / 10:19≈ on time ≈ on time
10:25≈ on time ≈ on time
10:29 / 10:30≈ on time ≈ on time
10:33≈ on time ≈ on time
10:38≈ on time ≈ +1 min
10:43 / 10:47≈ on time ≈ +1 min
10:51≈ on time ≈ +1 min
10:56on time +1 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
Sun 15 NovEnschede Kennispark 11:05Partial coverage0 min—
Sat 14 NovEnschede Kennispark 11:04Partial coverage+1 min+1 min
Fri 13 NovEnschede Kennispark 11:04+1 min—
Thu 12 NovEnschede Kennispark 11:040 min—
Wed 11 NovEnschede Kennispark 11:04+1 min—
Tue 10 NovEnschede Kennispark 11:09+3 min+3 min
Mon 9 NovEnschede Kennispark 11:040 min+1 min
Sun 8 NovEnschede Kennispark 11:04Partial coverage0 min—
Sat 7 NovEnschede Kennispark 11:04Partial coverage0 min—
Fri 6 NovEnschede Kennispark 11:04No data—
Thu 5 NovEnschede Kennispark 11:04No data—
Wed 4 NovEnschede Kennispark 11:040 min—
Tue 3 NovEnschede Kennispark 11:04No data—
Mon 2 NovEnschede Kennispark 11:04No data—
Sun 1 NovEnschede Kennispark 11:05Partial coverage0 min—
Sat 31 OctEnschede Kennispark 11:05No data—
Fri 30 OctEnschede Kennispark 11:08No data—
Thu 29 OctEnschede Kennispark 11:060 min—
Wed 28 OctEnschede Kennispark 11:060 min—
Tue 27 OctEnschede Kennispark 11:060 min—
Mon 26 OctEnschede Kennispark 11:06No data—
Sun 25 OctWierden 10:36No data—
Sat 24 OctWierden 10:360 min—
Fri 23 OctEnschede Kennispark 11:06No data—
Thu 22 OctEnschede Kennispark 11:09No data—
Wed 21 OctEnschede Kennispark 11:07No data—
Tue 20 OctEnschede Kennispark 11:060 min—
Mon 19 OctRaalte 10:590 min—
Sun 18 OctEnschede Kennispark 11:05Partial coverage0 min—
Sat 17 OctEnschede Kennispark 11:05Partial coverage0 min—