Train Arriva 7961 Zwolle – Enschede

Zwolle 18:22 → Enschede 19:26 Daily 1 h 04 min · 11 stops Arriva

It has not run yet today

Last recorded run: Tuesday 3 November No data

Next service: today 18:22 from Zwolle · Thu 5 Nov

Next departure 18:22 today · Zwolle
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 10 full · 6 partial · 10 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 12 full · 6 partial · 49 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

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 100% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=2
  • 100% T n=2
  • 100% F n=2
  • 100% S n=2
  • 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
18:22on time on time
18:29 / 18:31≈ on time ≈ on time
18:35 / 18:36≈ on time ≈ on time
18:43 / 18:47≈ on time ≈ +1 min
18:52 / 18:55≈ on time ≈ +1 min
18:59 / 19:00≈ on time ≈ +1 min
19:03≈ on time ≈ +1 min
19:08≈ on time ≈ +1 min
19:13 / 19:17≈ on time ≈ +2 min
19:21≈ on time ≈ +2 min
19:26on time +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 3 Nov— 19:24No data—
Mon 2 NovRaalte 19:28Partial coverage0 min—
Sun 1 NovEnschede Kennispark 19:37+2 min+2 min
Sat 31 OctEnschede Kennispark 19:38+2 min+2 min
Fri 30 OctNijverdal 19:30No data—
Wed 28 Oct— 19:290 min—
Tue 27 Oct— 19:340 min—
Mon 26 Oct— 19:32No data—
Sun 25 OctWierden 19:09No data—
Sat 24 OctWierden 19:07No data—
Fri 23 OctEnschede Kennispark 19:35Partial coverage+3 min+3 min
Thu 22 OctRaalte 18:50No data—
Wed 21 OctRaalte 18:50No data—
Tue 20 OctRaalte 18:50Partial coverage0 min—
Mon 19 OctRaalte 19:29Partial coverage0 min—
Sun 18 OctEnschede Kennispark 19:39+2 min+2 min
Sat 17 OctEnschede Kennispark 19:37No data—
Fri 16 OctEnschede Kennispark 19:35No data—
Thu 15 OctZwolle 19:290 min—
Tue 13 OctRaalte 19:31No data—
Mon 12 OctRaalte 19:29Partial coverage0 min—
Sun 11 OctEnschede Kennispark 19:38+2 min+2 min
Sat 10 OctEnschede Kennispark 19:370 min—
Fri 9 OctRaalte 19:28Partial coverage0 min—
Thu 8 Oct— 19:270 min—
Wed 7 Oct— 19:260 min—
Tue 6 Oct— 19:27+1 min—
Mon 5 Oct— 19:280 min—
Sun 4 OctEnschede Kennispark 19:37No data—
Sat 3 OctEnschede Kennispark 19:36No data—