Train Arriva 7975 Zwolle – Enschede

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

It has not run yet today

Last recorded run: Wednesday 4 November +4 min

Next service: today 21:52 from Zwolle · Thu 5 Nov

Next departure 21:52 today · Zwolle
On-time · 30 days
79%
11/14 runs under 3 min
RT coverage: 11 full · 3 partial · 9 no data
On-time · 90 days
80%
12/15 runs under 3 min
RT coverage: 12 full · 3 partial · 28 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Thu 29 Oct Max en route +32 min · last fix heading to — +32 min
  • Wed 4 Nov Max en route +4 min · last fix heading to — +4 min
  • Fri 16 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 12
  • 3–10 min 13% · 2
  • 10–30 min 0% · 0
  • 30+ min 7% · 1

On-time by weekday

  • 100% M n=5
  • — T n=0
  • 0% W n=1
  • 50% T n=2
  • 67% F n=3
  • 100% S n=1
  • 100% S n=3

Stops and timetable

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

Last 90 days, 15 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:52on time on time
21:59 / 22:01≈ on time ≈ on time
22:05 / 22:09≈ on time ≈ +1 min
22:16 / 22:19≈ on time ≈ +1 min
22:25≈ on time ≈ +2 min
22:29 / 22:30≈ on time ≈ +2 min
22:33≈ +1 min ≈ +3 min
22:38≈ +1 min ≈ +3 min
22:43 / 22:48≈ +1 min ≈ +3 min
22:52≈ +1 min ≈ +4 min
22:57+1 min +4 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— 23:04+4 min+4 min
Mon 2 Nov— 23:03+3 min+3 min
Sun 1 NovEnschede Kennispark 23:07Partial coverage0 min—
Sat 31 OctEnschede Kennispark 23:06No data—
Fri 30 Oct— 22:59No data—
Thu 29 Oct— 23:32+32 min+32 min
Wed 28 Oct— 23:01No data—
Mon 26 Oct— 23:030 min—
Sun 25 OctWierden 22:38No data—
Sat 24 OctWierden 22:36No data—
Fri 23 Oct— 23:000 min—
Thu 22 Oct— 23:01No data—
Tue 20 Oct— 23:00No data—
Mon 19 Oct— 23:000 min—
Sun 18 OctEnschede Kennispark 23:060 min—
Sat 17 OctEnschede Kennispark 23:07No data—
Fri 16 Oct— 23:03+3 min+3 min
Tue 13 Oct— 22:58No data—
Mon 12 Oct— 23:00+1 min—
Sun 11 OctEnschede Kennispark 23:07Partial coverage+1 min—
Sat 10 OctHeino 23:00Partial coverage+1 min—
Fri 9 Oct— 23:01+1 min+1 min
Thu 8 Oct— 23:000 min—
Tue 6 Oct— 22:59No data—
Mon 5 Oct— 23:01+1 min+1 min
Sun 4 OctEnschede Kennispark 23:06No data—
Sat 3 OctEnschede Kennispark 23:06No data—
Sun 27 SeptEnschede Kennispark 23:06No data—
Sat 26 SeptEnschede Kennispark 23:06No data—
Sun 20 SeptEnschede Kennispark 23:07No data—