Train Arriva 7973 Zwolle – Enschede

Zwolle 21:22 → Enschede 22:27 Daily 1 h 05 min · 11 stops Arriva

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 21:22 from Zwolle · Wed 18 Nov

Next departure 21:22 today · Zwolle
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 10 full · 5 partial · 10 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 16 full · 7 partial · 27 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

  • Mon 2 Nov Max en route +10 min · last fix heading to — +10 min
  • Fri 9 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
21:22on time on time
21:29 / 21:31≈ on time ≈ on time
21:35 / 21:36≈ on time ≈ +1 min
21:43 / 21:49≈ on time ≈ +1 min
21:55≈ on time ≈ +2 min
21:59 / 22:00≈ on time ≈ +2 min
22:03≈ on time ≈ +2 min
22:08≈ on time ≈ +2 min
22:13 / 22:18≈ +1 min ≈ +3 min
22:22≈ +1 min ≈ +3 min
22:27+1 min +3 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
Mon 16 NovRaalte 22:29Partial coverage0 min—
Sun 15 NovEnschede Kennispark 22:38Partial coverage+2 min+2 min
Sat 14 NovEnschede Kennispark 22:34Partial coverage0 min—
Fri 13 Nov— 21:440 min—
Thu 12 Nov— 22:28+1 min—
Wed 11 Nov— 22:290 min—
Tue 10 Nov— 22:29+1 min+1 min
Sun 8 NovEnschede Kennispark 22:34No data—
Sat 7 NovEnschede Kennispark 22:34Partial coverage0 min+1 min
Fri 6 Nov— 22:32+3 min+3 min
Thu 5 Nov— 22:29No data—
Tue 3 Nov— 22:29No data—
Mon 2 Nov— 22:39+10 min+10 min
Sun 1 NovEnschede Kennispark 22:38Partial coverage+2 min+2 min
Sat 31 OctEnschede Kennispark 22:36No data—
Fri 30 Oct— 22:32No data—
Wed 28 Oct— 22:290 min—
Tue 27 Oct— 22:310 min—
Mon 26 Oct— 22:30No data—
Sun 25 OctWierden 22:06No data—
Sat 24 OctWierden 22:06No data—
Fri 23 Oct— 22:31+1 min—
Thu 22 Oct— 22:32No data—
Wed 21 Oct— 22:32No data—
Tue 20 Oct— 22:320 min—
Mon 19 Oct— 22:340 min—
Sun 18 OctEnschede Kennispark 22:38+2 min+2 min
Sat 17 OctEnschede Kennispark 22:37No data—
Mon 12 Oct— 22:300 min—
Sun 11 OctEnschede Kennispark 22:37Partial coverage0 min—