Train Blauwnet K 7936 Enschede – Zwolle

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

✓ Today’s run finished

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

  1. Enschede10:04
  2. Hengelo10:12
  3. Borne10:21
  4. Almelo10:30
  5. Nijverdal10:41
  6. Heino10:58
  7. Zwolle11:09

Next service: tomorrow 10:04 from Enschede · Thu 19 Nov

Next departure 10:04 tomorrow · Enschede
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 1 full · 17 partial · 11 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 1 full · 25 partial · 61 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

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=2
  • 100% T n=5
  • 100% W n=5
  • 100% T n=2
  • 100% F n=2
  • 100% S n=6
  • 100% S n=4

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
10:04on time on time
10:08— —
10:12 / 10:16— —
10:21— —
10:27— —
10:30— —
10:34 / 10:36— —
10:41 / 10:43— —
10:50 / 10:54— —
10:58 / 11:00— —
11:09— —

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