Train Arriva 7967 Zwolle – Enschede

Zwolle 19:52 → Enschede 20:57 Daily 1 h 05 min · 11 stops Arriva

It has not run yet today

Last recorded run: Tuesday 17 November +2 min

Next service: today 19:52 from Zwolle · Wed 18 Nov

Next departure 19:52 today · Zwolle
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 12 full · 6 partial · 7 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 17 full · 10 partial · 26 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sat 7 Nov Max en route +7 min · last fix heading to Enschede Kennispark +7 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 min

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 93% · 25
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
19:52on time on time
19:59 / 20:01≈ on time ≈ on time
20:05 / 20:09≈ on time ≈ on time
20:16 / 20:19≈ on time ≈ +1 min
20:25≈ on time ≈ +1 min
20:29 / 20:30≈ on time ≈ +1 min
20:33≈ +1 min ≈ +1 min
20:38≈ +1 min ≈ +1 min
20:43 / 20:48≈ +1 min ≈ +2 min
20:52≈ +1 min ≈ +2 min
20:57+1 min +2 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 Nov— 20:59+2 min+2 min
Mon 16 Nov— 20:59+2 min+2 min
Sun 15 NovEnschede Kennispark 21:07Partial coverage+1 min—
Sat 14 NovEnschede Kennispark 21:07Partial coverage+1 min—
Fri 13 Nov— 20:58+1 min—
Wed 11 Nov— 20:59+1 min—
Mon 9 Nov— 20:59+1 min—
Sun 8 NovEnschede Kennispark 21:07Partial coverage+1 min—
Sat 7 NovEnschede Kennispark 21:12Partial coverage+7 min+7 min
Fri 6 Nov— 20:590 min+1 min
Wed 4 Nov— 20:59+2 min+2 min
Mon 2 Nov— 20:59No data—
Sun 1 NovEnschede Kennispark 21:09Partial coverage+2 min+2 min
Sat 31 OctEnschede Kennispark 21:06Partial coverage0 min—
Fri 30 Oct— 21:00No data—
Thu 29 Oct— 21:00+1 min—
Wed 28 Oct— 20:590 min—
Tue 27 Oct— 20:580 min—
Mon 26 Oct— 21:00No data—
Sun 25 OctWierden 20:36No data—
Sat 24 OctWierden 20:40No data—
Fri 23 Oct— 21:06+5 min+5 min
Thu 22 Oct— 21:01No data—
Wed 21 Oct— 21:00No data—
Tue 20 Oct— 21:020 min—
Mon 19 Oct— 21:00No data—
Sun 18 OctEnschede Kennispark 21:08Partial coverage+2 min+2 min
Sat 17 OctEnschede Kennispark 21:07No data—
Fri 16 OctZwolle 20:59Partial coverage0 min—
Thu 15 Oct— 20:590 min—