Train Blauwnet K 7933 Zwolle – Enschede

Zwolle 11:22 → Enschede 12:27 Daily 1 h 05 min · 11 stops Blauwnet K

✓ Today’s run finished

Today, last fix heading to Enschede Kennispark at 12:39 +2 min

  1. Zwolle11:22
  2. Raalte11:35
  3. Nijverdal11:43
  4. Almelo11:59
  5. Borne12:08
  6. Enschede Kennispark12:22
  7. Enschede12:27

Next service: tomorrow 11:22 from Zwolle · Mon 9 Nov

Next departure 11:22 tomorrow · Zwolle
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 7 full · 7 partial · 15 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 12 full · 7 partial · 69 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: +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

  • Wed 7 Oct Max en route +4 min · last fix heading to Enschede Kennispark +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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