Train Arriva 7990 Enschede – Zwolle

Enschede 23:34 → Zwolle 00:39 Daily 1 h 05 min · 11 stops Arriva

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 23:34 from Enschede · Fri 20 Nov

Next departure 23:34 today · Enschede
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 18 full · 1 partial · 6 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 26 full · 2 partial · 20 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: +2 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

  • Tue 17 Nov Max en route +9 min · last fix heading to — +9 min
  • Fri 13 Nov Max en route +6 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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