Train Blauwnet K 7929 Zwolle – Enschede

Zwolle 10:22 → Enschede 11:26 Daily 1 h 04 min · 11 stops Blauwnet K

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 10:22 from Zwolle · Fri 6 Nov

Next departure 10:22 today · Zwolle
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 6 full · 8 partial · 14 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 6 full · 9 partial · 72 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=2
  • 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, 15 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:22on time on time
10:29 / 10:31≈ on time ≈ on time
10:35 / 10:36≈ on time ≈ on time
10:43 / 10:47≈ on time ≈ on time
10:52 / 10:55≈ on time ≈ on time
10:59 / 11:00≈ on time ≈ on time
11:03≈ on time ≈ on time
11:08≈ on time ≈ on time
11:13 / 11:17≈ on time ≈ on time
11:21≈ on time ≈ on time
11:26on time on time

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 11:37No data—
Wed 4 NovEnschede Kennispark 11:34Partial coverage+1 min—
Tue 3 NovEnschede Kennispark 11:35No data—
Mon 2 NovEnschede Kennispark 11:34Partial coverage0 min—
Sun 1 NovEnschede Kennispark 11:370 min—
Sat 31 OctEnschede Kennispark 11:370 min—
Fri 30 OctEnschede Kennispark 11:36No data—
Thu 29 OctEnschede Kennispark 11:36No data—
Wed 28 OctEnschede Kennispark 11:36Partial coverage0 min—
Tue 27 OctEnschede Kennispark 11:36Partial coverage0 min—
Mon 26 OctEnschede Kennispark 11:35No data—
Sun 25 OctWierden 11:07No data—
Sat 24 OctWierden 11:060 min—
Fri 23 OctEnschede Kennispark 11:37No data—
Thu 22 OctEnschede Kennispark 11:41No data—
Wed 21 OctEnschede Kennispark 11:36No data—
Tue 20 OctEnschede Kennispark 11:36Partial coverage0 min—
Mon 19 OctEnschede Kennispark 11:37Partial coverage0 min—
Sun 18 OctEnschede Kennispark 11:370 min—
Sat 17 OctEnschede Kennispark 11:37No data—
Fri 16 OctEnschede Kennispark 11:36No data—
Thu 15 OctEnschede Kennispark 11:35No data—
Tue 13 OctEnschede Kennispark 11:36No data—
Mon 12 OctEnschede Kennispark 11:35No data—
Sun 11 OctEnschede Kennispark 11:360 min—
Sat 10 OctEnschede Kennispark 11:360 min—
Fri 9 OctEnschede Kennispark 11:37Partial coverage+1 min+1 min
Thu 8 OctEnschede Kennispark 11:36Partial coverage0 min—
Wed 7 OctAlmelo de Riet 12:02No data—
Tue 6 OctEnschede Kennispark 11:36Partial coverage+1 min—