Train Blauwnet K 7946 Enschede – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Heino at 13:47 +2 min

  1. Enschede12:34
  2. Hengelo12:43
  3. Borne12:51
  4. Almelo13:00
  5. Nijverdal13:12
  6. Heino13:28
  7. Zwolle13:39

Next service: tomorrow 12:34 from Enschede · Wed 18 Nov

Next departure 12:34 tomorrow · Enschede
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 6 full · 13 partial · 11 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 9 full · 18 partial · 62 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: +2 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

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

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

On-time by weekday

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

Stops and timetable

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

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