Train Blauwnet K 17938 Enschede – Zwolle

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 10:31 from Enschede · Mon 9 Nov

Next departure 10:31 today · Enschede
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 0 full · 5 partial · 15 no data
On-time · 90 days
88%
7/8 runs under 3 min
RT coverage: 0 full · 8 partial · 54 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: 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

Worst days

  • Fri 9 Oct Max en route +8 min · last fix heading to Raalte +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 7
  • 3–10 min 13% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=3
  • 100% W n=3
  • — T n=0
  • 0% 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, 8 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:31on time on time
10:38 / 10:39— —
10:49 / 10:50— —
10:59 / 11:00— —
11:08— —
11: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 11:22No data—
Thu 5 NovRaalte 11:24No data—
Wed 4 NovRaalte 11:22Partial coverage0 min—
Tue 3 NovRaalte 11:24No data—
Mon 2 NovRaalte 11:22No data—
Fri 30 OctRaalte 11:24No data—
Thu 29 OctRaalte 11:22No data—
Wed 28 OctRaalte 11:22Partial coverage0 min—
Tue 27 OctRaalte 11:22Partial coverage0 min—
Mon 26 OctRaalte 11:22No data—
Fri 23 OctRaalte 11:23No data—
Thu 22 OctRaalte 11:27No data—
Wed 21 OctRaalte 11:29No data—
Tue 20 OctRaalte 11:22Partial coverage0 min—
Mon 19 OctRaalte 11:22Partial coverage0 min—
Fri 16 OctRaalte 11:22No data—
Thu 15 OctRaalte 11:23No data—
Wed 14 OctRaalte 11:22No data—
Tue 13 OctRaalte 11:23No data—
Mon 12 OctAlmelo 12:08No data—
Fri 9 OctRaalte 11:30Partial coverage+8 min+8 min
Thu 8 OctRaalte 11:22Partial coverageNo data—
Wed 7 OctAlmelo 12:01Partial coverage0 min—
Tue 6 OctRaalte 11:22Partial coverage0 min—
Mon 5 OctRaalte 11:22No data—
Fri 2 OctRaalte 11:22No data—
Thu 1 OctRaalte 11:22No data—
Wed 30 SeptRaalte 11:23No data—
Tue 29 SeptRaalte 11:22No data—
Mon 28 SeptRaalte 11:22No data—