Train Blauwnet K 7944 Enschede – Zwolle

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

✓ Today’s run finished

Today, last fix heading to Heino at 13:14 No data

  1. Enschede12:04
  2. Hengelo12:12
  3. Borne12:21
  4. Almelo12:30
  5. Nijverdal12:41
  6. Heino12:58
  7. Zwolle13:09

Next service: tomorrow 12:04 from Enschede · Sat 7 Nov

Next departure 12:04 tomorrow · Enschede
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 2 full · 12 partial · 15 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 2 full · 15 partial · 71 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

Worst days

  • Sat 31 Oct Max en route +16 min · last fix heading to Heino +14 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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:04on time on time
12:08— —
12:12 / 12:16— —
12:21— —
12:27— —
12:30— —
12:34 / 12:36— —
12:41 / 12:43— —
12:50 / 12:54— —
12:58 / 13:00— —
13: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
Fri 6 NovHeino 13:14No data—
Thu 5 NovHeino 13:14No data—
Wed 4 NovHeino 13:14Partial coverage0 min—
Tue 3 NovHeino 13:14No data—
Mon 2 NovHeino 13:14No data—
Sun 1 NovHeino 13:15Partial coverage0 min—
Sat 31 OctHeino 13:29Partial coverage+14 min+16 min
Fri 30 OctHeino 13:14No data—
Thu 29 OctHeino 13:14Partial coverage0 min—
Wed 28 OctHeino 13:14Partial coverage0 min—
Tue 27 OctHeino 13:14Partial coverage0 min—
Mon 26 OctHeino 13:14No data—
Sun 25 OctHeino 13:14No data—
Sat 24 OctHeino 13:150 min—
Fri 23 OctHeino 13:14No data—
Thu 22 OctHeino 13:14No data—
Wed 21 OctHeino 13:14No data—
Tue 20 OctHeino 13:14Partial coverage0 min—
Mon 19 OctHeino 13:14Partial coverage0 min—
Sun 18 OctHeino 13:140 min+1 min
Sat 17 OctHeino 13:14No data—
Fri 16 OctHeino 13:14No data—
Thu 15 OctHeino 13:14No data—
Tue 13 OctHeino 13:14No data—
Mon 12 OctHeino 13:14No data—
Sun 11 OctHeino 13:14Partial coverage0 min—
Sat 10 OctHeino 13:14Partial coverage0 min—
Fri 9 OctHeino 13:14Partial coverage0 min—
Thu 8 OctHeino 13:14Partial coverage0 min—
Wed 7 OctHeino 13:14Partial coverage0 min—