Train Blauwnet K 7925 Zwolle – Enschede

Zwolle 09:22 → Enschede 10: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 09:22 from Zwolle · Fri 6 Nov

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

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=1
  • 100% T n=4
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 100% S n=4
  • 100% S n=2

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
09:22on time on time
09:29 / 09:31≈ on time ≈ on time
09:35 / 09:36≈ on time ≈ on time
09:43 / 09:47≈ on time ≈ on time
09:52 / 09:55≈ on time ≈ +1 min
09:59 / 10:00≈ on time ≈ +1 min
10:03≈ on time ≈ +1 min
10:08≈ on time ≈ +1 min
10:13 / 10:17≈ on time ≈ +1 min
10:21≈ on time ≈ +1 min
10:26on 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
Thu 5 NovEnschede Kennispark 10:37No data—
Wed 4 NovEnschede Kennispark 10:34Partial coverage0 min—
Tue 3 NovEnschede Kennispark 10:34Partial coverage0 min—
Mon 2 NovEnschede Kennispark 10:37No data—
Sun 1 NovEnschede Kennispark 10:370 min—
Sat 31 OctEnschede Kennispark 10:360 min—
Fri 30 OctEnschede Kennispark 10:40No data—
Thu 29 OctEnschede Kennispark 10:36No data—
Wed 28 OctEnschede Kennispark 10:36Partial coverage0 min—
Tue 27 OctEnschede Kennispark 10:35Partial coverage0 min—
Mon 26 OctEnschede Kennispark 10:36No data—
Sun 25 OctWierden 10:06No data—
Sat 24 OctWierden 10:07+1 min+1 min
Fri 23 OctEnschede Kennispark 10:35No data—
Thu 22 OctEnschede Kennispark 10:37No data—
Wed 21 OctEnschede Kennispark 10:35No data—
Tue 20 OctEnschede Kennispark 10:35Partial coverage0 min—
Mon 19 OctEnschede Kennispark 10:36Partial coverage0 min—
Sun 18 OctEnschede Kennispark 10:37+1 min—
Sat 17 OctEnschede Kennispark 10:360 min—
Fri 16 OctEnschede Kennispark 10:36No data—
Thu 15 OctEnschede Kennispark 10:36No data—
Wed 14 OctZwolle 09:36No data—
Tue 13 OctEnschede Kennispark 10:37No data—
Mon 12 OctEnschede Kennispark 10:55No data—
Sun 11 OctEnschede Kennispark 10:36No data—
Sat 10 OctEnschede Kennispark 10:370 min+1 min
Fri 9 OctEnschede Kennispark 10:37Partial coverage+2 min+2 min
Thu 8 OctEnschede Kennispark 10:36Partial coverage0 min—
Wed 7 OctEnschede Kennispark 12:01+1 min+1 min