Train Blauwnet K 7928 Enschede – Zwolle

Enschede 08:04 → Zwolle 09:09 Daily 1 h 05 min · 11 stops Blauwnet K

✓ Today’s run finished

Today, last fix heading to Heino at 09:14 0 min

  1. Enschede08:04
  2. Hengelo08:12
  3. Borne08:21
  4. Almelo08:30
  5. Nijverdal08:41
  6. Heino08:58
  7. Zwolle09:09

Next service: tomorrow 08:04 from Enschede · Thu 12 Nov

Next departure 08:04 tomorrow · Enschede
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 7 full · 8 partial · 15 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 8 full · 12 partial · 69 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
08:04on time on time
08:08≈ on time ≈ on time
08:12 / 08:16≈ on time ≈ on time
08:21≈ on time ≈ on time
08:27≈ on time ≈ on time
08:30≈ on time ≈ on time
08:34 / 08:36≈ on time ≈ on time
08:41 / 08:43≈ on time ≈ on time
08:50 / 08:54≈ on time ≈ on time
08:58 / 09:00≈ on time ≈ on time
09:09on time on time

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
Wed 11 NovHeino 09:14Partial coverage0 min—
Tue 10 NovHeino 09:14Partial coverage+1 min+1 min
Mon 9 NovHeino 09:14Partial coverage0 min—
Sun 8 NovHeino 09:140 min—
Sat 7 NovHeino 09:140 min—
Fri 6 NovHeino 09:14No data—
Thu 5 NovHeino 09:14No data—
Wed 4 NovHeino 09:14Partial coverage0 min—
Tue 3 NovHeino 09:14No data—
Mon 2 NovHeino 09:14No data—
Sun 1 NovHeino 09:150 min+1 min
Sat 31 OctHeino 09:140 min—
Fri 30 OctHeino 09:14No data—
Thu 29 OctHeino 09:14Partial coverage0 min—
Wed 28 OctHeino 09:14Partial coverage0 min—
Tue 27 OctHeino 09:14No data—
Mon 26 OctHeino 09:14No data—
Sun 25 OctHeino 09:14No data—
Sat 24 OctHeino 09:140 min—
Fri 23 OctHeino 09:15No data—
Thu 22 OctHeino 09:19Partial coverageNo data—
Wed 21 OctHeino 09:14No data—
Tue 20 OctHeino 09:17Partial coverage0 min—
Mon 19 OctHeino 09:14Partial coverage0 min—
Sun 18 OctHeino 09:140 min—
Sat 17 OctHeino 09:140 min—
Fri 16 OctHeino 09:14No data—
Thu 15 OctHeino 09:33No data—
Wed 14 OctHeino 09:14No data—
Tue 13 OctHeino 09:14No data—