Train Blauwnet K 7974 Enschede – Zwolle

Enschede 19:34 → Zwolle 20:39 Daily 1 h 05 min · 11 stops Blauwnet K

It has not run yet today

Last recorded run: Sunday 15 November +1 min

Next service: today 19:34 from Enschede · Wed 18 Nov

Next departure 19:34 today · Enschede
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 15 full · 2 partial · 5 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 24 full · 2 partial · 23 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 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 26 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
19:34on time on time
19:38≈ on time ≈ on time
19:42 / 19:46≈ on time ≈ on time
19:51≈ on time ≈ on time
19:57≈ on time ≈ on time
20:00≈ on time ≈ on time
20:04 / 20:07≈ on time ≈ on time
20:12 / 20:16≈ on time ≈ +1 min
20:23 / 20:24≈ on time ≈ +1 min
20:28 / 20:30≈ on time ≈ +1 min
20:39on 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 15 NovHeino 20:44Partial coverage+1 min+1 min
Sat 14 NovHeino 20:440 min—
Fri 13 Nov— 20:44+3 min+3 min
Thu 12 Nov— 20:430 min—
Wed 11 Nov— 20:390 min—
Tue 10 Nov— 20:420 min+4 min
Mon 9 Nov— 20:390 min—
Sun 8 NovHeino 20:44+1 min+1 min
Sat 7 NovHeino 20:440 min+1 min
Fri 6 Nov— 20:390 min—
Thu 5 Nov— 20:39No data—
Mon 2 Nov— 20:390 min—
Sun 1 NovHeino 20:44Partial coverage0 min—
Sat 31 OctHeino 20:440 min—
Fri 30 Oct— 20:42No data—
Thu 29 Oct— 20:410 min—
Wed 28 Oct— 20:410 min—
Tue 27 Oct— 20:420 min—
Mon 26 OctAlmelo 20:39No data—
Sun 25 OctHeino 20:44No data—
Sat 24 OctHeino 20:46No data—
Tue 20 Oct— 20:410 min—
Sun 18 OctHeino 20:440 min—
Sat 17 OctHeino 20:44No data—
Thu 15 Oct— 20:40No data—
Tue 13 Oct— 20:41No data—
Mon 12 Oct— 20:410 min—
Sun 11 OctHeino 20:46+1 min+1 min
Sat 10 OctHeino 20:440 min—
Fri 9 Oct— 20:410 min—