Train Arriva 17970 Enschede – Zwolle

Enschede 18:31 → Zwolle 19:18 Mon, Tue, Wed, Thu, Fri 0 h 47 min · 6 stops Arriva

It has not run yet today

Last recorded run: Tuesday 3 November No data

Next service: today 18:31 from Enschede · Thu 5 Nov

Next departure 18:31 today · Enschede
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 6 full · 5 partial · 7 no data
On-time · 90 days
92%
11/12 runs under 3 min
RT coverage: 7 full · 5 partial · 26 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 8 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 11
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 12 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:31on time on time
18:38 / 18:39≈ on time ≈ +1 min
18:49 / 18:50≈ on time ≈ +1 min
18:59 / 19:00≈ on time ≈ +2 min
19:08≈ on time ≈ +2 min
19:18on time +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
Tue 3 Nov— 19:19No data—
Fri 30 OctAlmelo 19:21No data—
Thu 29 Oct— 19:210 min—
Wed 28 Oct— 19:220 min—
Tue 27 Oct— 19:21No data—
Mon 26 Oct— 19:240 min—
Fri 23 OctRaalte 19:23Partial coverage+1 min+2 min
Thu 22 OctHengelo 18:53No data—
Wed 21 OctHengelo 19:21No data—
Tue 20 OctHengelo 18:50Partial coverage0 min—
Mon 19 OctHengelo 18:53Partial coverage0 min—
Fri 16 OctRaalte 19:22No data—
Thu 15 Oct— 19:230 min—
Tue 13 OctHengelo 19:22No data—
Mon 12 OctHengelo 19:21Partial coverage0 min—
Fri 9 OctEnschede 19:21Partial coverage0 min—
Thu 8 Oct— 19:25+5 min+5 min
Wed 7 Oct— 19:210 min—
Mon 5 Oct— 19:23+1 min+3 min
Fri 2 OctHengelo 18:53No data—
Fri 25 SeptEnschede 18:45No data—
Fri 18 SeptHengelo 18:53No data—
Fri 11 SeptAlmelo 19:04No data—
Fri 4 SeptAlmelo 19:04No data—
Fri 28 AugRaalte 19:22No data—
Thu 27 AugHengelo 18:53No data—
Wed 26 AugRaalte 19:22No data—
Tue 25 AugAlmelo 19:04No data—
Fri 21 AugRaalte 19:22No data—
Thu 20 AugRaalte 19:22No data—