Train Arriva 7978 Enschede → Zwolle

Enschede 20:34 → Zwolle 21:39 Daily 1 h 05 min · 11 stops Arriva

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 20:34 from Enschede · Sat 21 Nov

Next departure 20:34 today · Enschede
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 13 full · 6 partial · 4 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 22 full · 8 partial · 21 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

  • Fri 13 Nov Max en route +10 min · last fix heading to — +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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
20:34on time on time
20:38≈ on time ≈ on time
20:42 / 20:46≈ on time ≈ on time
20:51≈ on time ≈ on time
20:57≈ on time ≈ on time
21:00≈ on time ≈ on time
21:04 / 21:07≈ on time ≈ on time
21:12 / 21:16≈ on time ≈ on time
21:23 / 21:24≈ on time ≈ +1 min
21:28 / 21:30≈ on time ≈ +1 min
21:39on 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 20 Nov— 21:390 min—
Thu 19 Nov— 21:43+1 min+1 min
Tue 17 Nov— 21:390 min—
Sun 15 NovHeino 21:44Partial coverage0 min—
Sat 14 NovHeino 21:44Partial coverage+1 min+1 min
Fri 13 Nov— 21:32+10 min+10 min
Thu 12 Nov— 21:42+1 min—
Wed 11 Nov— 21:390 min—
Tue 10 Nov— 21:390 min—
Mon 9 Nov— 21:390 min—
Sun 8 NovHeino 21:44Partial coverage0 min—
Sat 7 NovHeino 21:44Partial coverage+1 min—
Wed 4 Nov— 21:390 min—
Mon 2 Nov— 21:390 min—
Sun 1 NovHeino 21:44Partial coverage0 min—
Sat 31 OctHeino 21:44Partial coverage0 min—
Fri 30 Oct— 21:43No data—
Thu 29 Oct— 21:420 min—
Wed 28 Oct— 21:410 min—
Mon 26 Oct— 21:41No data—
Sun 25 OctHeino 21:44No data—
Sat 24 OctHeino 21:44No data—
Fri 23 Oct— 21:42+1 min+1 min
Thu 22 Oct— 21:50No data—
Wed 21 Oct— 21:43No data—
Tue 20 Oct— 21:440 min—
Mon 19 Oct— 21:450 min—
Sun 18 OctHeino 21:450 min—
Sat 17 OctHeino 21:44No data—
Fri 16 Oct— 21:410 min—