Train Arriva 7972 Enschede – Zwolle

Enschede 19:04 → Zwolle 20:09 Daily 1 h 05 min · 11 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 19:04 from Enschede · Thu 5 Nov

Next departure 19:04 today · Enschede
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 13 full · 1 partial · 9 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 15 full · 1 partial · 39 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Thu 29 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 100% W n=1
  • 50% 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, 16 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:04on time on time
19:08≈ on time ≈ on time
19:12 / 19:16≈ on time ≈ on time
19:21≈ on time ≈ on time
19:27≈ on time ≈ on time
19:30≈ on time ≈ on time
19:34 / 19:36≈ on time ≈ on time
19:41 / 19:43≈ on time ≈ on time
19:50 / 19:54≈ on time ≈ on time
19:58 / 20:00≈ on time ≈ +1 min
20:09on time +1 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
Wed 4 Nov— 20:090 min—
Tue 3 Nov— 20:090 min—
Sun 1 NovHeino 20:140 min—
Sat 31 OctHeino 20:140 min—
Fri 30 Oct— 20:11No data—
Thu 29 Oct— 20:14+3 min+3 min
Tue 27 Oct— 20:110 min—
Mon 26 OctRaalte 20:11No data—
Sun 25 OctHeino 20:14No data—
Sat 24 OctHeino 20:17No data—
Fri 23 OctAlmelo de Riet 20:11Partial coverage0 min—
Thu 22 Oct— 20:11No data—
Wed 21 Oct— 20:12No data—
Tue 20 Oct— 20:140 min—
Mon 19 Oct— 20:110 min—
Sun 18 OctHeino 20:140 min—
Sat 17 OctHeino 20:14No data—
Fri 16 OctRaalte 20:11No data—
Tue 13 Oct— 20:12No data—
Sun 11 OctHeino 20:140 min—
Sat 10 OctHeino 20:14+1 min+1 min
Fri 9 Oct— 20:090 min—
Thu 8 Oct— 20:130 min—
Tue 6 Oct— 20:110 min—
Mon 5 Oct— 20:100 min—
Sun 4 OctHeino 20:14No data—
Sat 3 OctHeino 20:14No data—
Sun 27 SeptHeino 20:14No data—
Sat 26 SeptHeino 20:14No data—
Sun 20 SeptHeino 20:14No data—