Train Blauwnet K 17963 Zwolle → Enschede

Zwolle 18:42 → Enschede 19:29 Mon, Tue, Wed, Thu, Fri 0 h 47 min · 6 stops Blauwnet K

Blauwnet K 17963 Zwolle–Enschede: final delay under 3 min on 9 of its 13 runs with data in the last 30 days (69%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 17:50 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 18:42 from Zwolle · Mon 23 Nov

Next departure 18:42 tomorrow · Zwolle
On-time · 30 days
69%
9/13 runs under 3 min
RT coverage: 9 full · 4 partial · 3 no data
On-time · 90 days
78%
18/23 runs under 3 min
RT coverage: 15 full · 8 partial · 14 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Fri 13 Nov Max en route +20 min · last fix heading to Raalte +20 min
  • Thu 12 Nov Max en route +6 min · last fix heading to — +6 min
  • Wed 11 Nov Max en route +6 min · last fix heading to — +5 min
  • Fri 23 Oct Max en route +4 min · last fix heading to Hengelo +4 min
  • Thu 19 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 18
  • 3–10 min 17% · 4
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 75% W n=4
  • 60% T n=5
  • 60% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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
18:42on time on time
18:52≈ on time ≈ +1 min
19:00 / 19:01≈ on time ≈ +2 min
19:09 / 19:10≈ on time ≈ +3 min
19:21 / 19:22≈ on time ≈ +4 min
19:29on time +5 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
Fri 20 NovAlmelo 19:33Partial coverage0 min—
Thu 19 Nov— 19:29+4 min+4 min
Wed 18 NovZwolle 18:53Partial coverage0 min—
Fri 13 NovRaalte 19:29Partial coverage+20 min+20 min
Thu 12 Nov— 19:38+6 min+6 min
Wed 11 Nov— 19:37+5 min+6 min
Tue 10 Nov— 19:290 min—
Mon 9 Nov— 19:290 min—
Fri 6 NovZwolle 19:32Partial coverage0 min—
Thu 5 Nov— 19:34No data—
Mon 2 Nov— 19:290 min—
Fri 30 OctRaalte 19:37No data—
Thu 29 Oct— 19:320 min—
Wed 28 Oct— 19:320 min—
Tue 27 Oct— 19:370 min—
Mon 26 Oct— 19:37No data—
Fri 23 OctHengelo 19:36Partial coverage+4 min+4 min
Thu 22 OctZwolle 18:59No data—
Tue 20 OctZwolle 19:32Partial coverage0 min—
Mon 19 OctZwolle 18:56Partial coverage0 min—
Fri 16 OctZwolle 18:56No data—
Thu 15 Oct— 19:320 min—
Tue 13 Oct— 19:33No data—
Mon 12 OctZwolle 19:32Partial coverage0 min—
Fri 9 Oct— 19:320 min+2 min
Thu 8 Oct— 19:33+1 min+3 min
Wed 7 Oct— 19:35+3 min+3 min
Tue 6 Oct— 19:31+1 min—
Mon 5 Oct— 19:320 min—
Fri 2 OctZwolle 18:56No data—