Train Arriva 17974 Enschede – Zwolle

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

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: tomorrow 19:31 from Enschede · Mon 9 Nov

Next departure 19:31 tomorrow · Enschede
On-time · 30 days
83%
5/6 runs under 3 min
RT coverage: 6 full · 0 partial · 5 no data
On-time · 90 days
91%
10/11 runs under 3 min
RT coverage: 11 full · 0 partial · 11 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: +4 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

  • Fri 23 Oct Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 11 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:31on time on time
19:38 / 19:39≈ on time ≈ on time
19:49 / 19:50≈ on time ≈ on time
19:59 / 20:00≈ on time ≈ +1 min
20:08≈ on time ≈ +1 min
20:18on 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
Fri 6 Nov— 20:22+1 min+1 min
Mon 2 Nov— 20:19No data—
Thu 29 Oct— 20:22+1 min—
Wed 28 Oct— 20:240 min—
Mon 26 Oct— 20:21No data—
Fri 23 Oct— 20:28+8 min+8 min
Wed 21 Oct— 20:21No data—
Tue 20 Oct— 20:220 min—
Fri 16 OctAlmelo 20:22No data—
Tue 13 Oct— 20:22No data—
Mon 12 Oct— 20:220 min—
Fri 9 Oct— 20:22+1 min+1 min
Thu 8 Oct— 20:210 min—
Wed 7 Oct— 20:20+1 min+1 min
Tue 6 Oct— 20:210 min—
Mon 5 Oct— 20:220 min—
Fri 21 AugRaalte 20:22No data—
Mon 17 AugHengelo 19:53No data—
Fri 14 AugRaalte 20:22No data—
Thu 13 AugRaalte 20:21No data—
Wed 12 AugRaalte 20:22No data—
Tue 11 AugRaalte 20:22No data—