Train Blauwnet K 7919 Zwolle – Enschede

Zwolle 07:52 → Enschede 08:56 Daily 1 h 04 min · 11 stops Blauwnet K

✓ Today’s run finished

Today, last fix heading to Enschede Kennispark at 09:13 No data

  1. Zwolle07:52
  2. Raalte08:05
  3. Nijverdal08:16
  4. Almelo08:29
  5. Borne08:38
  6. Enschede Kennispark08:51
  7. Enschede08:56

Next service: tomorrow 07:52 from Zwolle · Fri 6 Nov

Next departure 07:52 tomorrow · Zwolle
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 1 full · 16 partial · 13 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 1 full · 17 partial · 71 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Enschede, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 4 Nov Max en route +6 min · last fix heading to Enschede Kennispark +5 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Enschede Kennispark +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
07:52on time on time
07:59 / 08:01— —
08:05 / 08:09— —
08:16 / 08:19— —
08:25— —
08:29 / 08:30— —
08:33— —
08:38— —
08:43 / 08:47— —
08:51— —
08:56— —

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
Thu 5 NovEnschede Kennispark 09:13No data—
Wed 4 NovEnschede Kennispark 09:09Partial coverage+5 min+6 min
Tue 3 NovEnschede Kennispark 09:08No data—
Mon 2 NovEnschede Kennispark 09:04No data—
Sun 1 NovEnschede Kennispark 09:05Partial coverage0 min—
Sat 31 OctEnschede Kennispark 09:05Partial coverage0 min—
Fri 30 OctEnschede Kennispark 09:08No data—
Thu 29 OctEnschede Kennispark 09:06Partial coverage0 min—
Wed 28 OctEnschede Kennispark 09:07Partial coverage0 min—
Tue 27 OctEnschede Kennispark 09:08Partial coverage0 min—
Mon 26 OctEnschede Kennispark 09:06Partial coverage0 min—
Sun 25 OctWierden 08:36No data—
Sat 24 OctWierden 08:36+1 min+1 min
Fri 23 OctEnschede Kennispark 09:06Partial coverage0 min—
Thu 22 OctEnschede Kennispark 09:06No data—
Wed 21 OctEnschede Kennispark 09:09No data—
Tue 20 OctEnschede Kennispark 09:10Partial coverage0 min—
Mon 19 OctEnschede Kennispark 09:10No data—
Sun 18 OctEnschede Kennispark 09:06Partial coverage0 min—
Sat 17 OctEnschede Kennispark 09:05Partial coverage0 min—
Fri 16 OctEnschede Kennispark 09:06No data—
Thu 15 OctEnschede Kennispark 09:06No data—
Wed 14 OctEnschede Kennispark 09:05No data—
Tue 13 OctEnschede Kennispark 09:06No data—
Mon 12 OctEnschede Kennispark 09:07No data—
Sun 11 OctEnschede Kennispark 09:05Partial coverage0 min—
Sat 10 OctEnschede Kennispark 09:05Partial coverage0 min—
Fri 9 OctEnschede Kennispark 09:07Partial coverage+3 min+3 min
Thu 8 OctEnschede Kennispark 09:08Partial coverage0 min—
Wed 7 OctEnschede Kennispark 09:06Partial coverage+1 min+1 min