Train Blauwnet K 17950 Enschede – Zwolle

Enschede 13:31 → Zwolle 14:18 Mon, Tue, Wed, Thu, Fri 0 h 47 min · 6 stops Blauwnet K

✓ Today’s run finished

Today, last fix heading to Raalte at 14:23 No data

  1. Enschede13:31
  2. Hengelo13:38
  3. Almelo13:49
  4. Nijverdal13:59
  5. Raalte14:08
  6. Zwolle14:18

Next service: Monday 13:31 from Enschede · Mon 9 Nov

Next departure 13:31 Monday · Enschede
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 1 full · 9 partial · 11 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 1 full · 12 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Zwolle, 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • 100% F n=1
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 13 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
13:31on time on time
13:38 / 13:39— —
13:49 / 13:50— —
13:59 / 14:00— —
14:08— —
14:18— —

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 6 NovRaalte 14:23No data—
Thu 5 NovRaalte 14:22No data—
Wed 4 NovRaalte 14:22Partial coverage0 min—
Tue 3 NovRaalte 14:22Partial coverage0 min—
Mon 2 NovRaalte 14:22Partial coverage0 min—
Fri 30 OctRaalte 14:22No data—
Thu 29 OctRaalte 14:22Partial coverage0 min—
Wed 28 OctRaalte 14:22Partial coverage0 min—
Tue 27 OctRaalte 14:22No data—
Mon 26 OctRaalte 14:22No data—
Fri 23 OctRaalte 14:22No data—
Thu 22 OctRaalte 14:22No data—
Wed 21 OctRaalte 14:22No data—
Tue 20 OctRaalte 14:23Partial coverage0 min—
Mon 19 OctRaalte 14:29Partial coverage0 min—
Fri 16 OctRaalte 14:22No data—
Thu 15 OctRaalte 14:220 min—
Tue 13 OctRaalte 14:22No data—
Mon 12 OctRaalte 14:22No data—
Fri 9 OctRaalte 14:23Partial coverage0 min—
Thu 8 OctRaalte 14:22Partial coverage0 min—
Wed 7 OctRaalte 14:22Partial coverage0 min—
Tue 6 OctRaalte 14:23Partial coverage0 min+1 min
Mon 5 OctRaalte 14:23Partial coverage+1 min—
Fri 2 OctRaalte 14:22No data—
Thu 1 OctRaalte 14:22No data—
Wed 30 SeptRaalte 14:22No data—
Tue 29 SeptRaalte 14:22No data—
Mon 28 SeptRaalte 14:22No data—
Fri 25 SeptRaalte 14:22No data—