Train Arriva 7980 Enschede – Zwolle

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 21:04 from Enschede · Fri 6 Nov

Next departure 21:04 today · Enschede
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 12 full · 3 partial · 12 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 13 full · 3 partial · 30 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

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 100% · 16
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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