Train Arriva 7983 Zwolle – Enschede

Zwolle 23:52 → Enschede 00:53 Daily 1 h 01 min · 11 stops Arriva

✓ Today’s run finished

Today, last fix heading to — at 01:03 No data

  1. Zwolle23:52
  2. Raalte00:05
  3. Nijverdal00:16
  4. Almelo00:29
  5. Borne00:38
  6. Hengelo00:43
  7. Enschede00:53

Next service: tomorrow 23:52 from Zwolle · Sat 7 Nov

Next departure 23:52 tomorrow · Zwolle
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 11 full · 3 partial · 7 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 13 full · 3 partial · 17 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 Enschede, 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=5
  • 100% T n=3
  • 100% W n=2
  • 100% T n=1
  • 100% F n=2
  • — S n=0
  • 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
23:52on time on time
23:59 / 00:01≈ on time ≈ on time
00:05 / 00:09≈ on time ≈ on time
00:16 / 00:19≈ on time ≈ on time
00:25≈ on time ≈ +1 min
00:29 / 00:30≈ on time ≈ +1 min
00:33≈ on time ≈ +1 min
00:38≈ on time ≈ +1 min
00:43 / 00:44≈ on time ≈ +1 min
00:49≈ on time ≈ +1 min
00:53on 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— 01:03No data—
Tue 3 Nov— 00:590 min—
Mon 2 Nov— 00:54+1 min—
Sun 1 NovEnschede Kennispark 01:03Partial coverage0 min—
Fri 30 Oct— 00:58No data—
Wed 28 Oct— 00:560 min—
Tue 27 Oct— 01:020 min—
Mon 26 Oct— 00:590 min—
Sun 25 OctWierden 00:39No data—
Sat 24 Oct— 00:32No data—
Fri 23 Oct— 01:01+1 min+1 min
Thu 22 Oct— 01:00No data—
Wed 21 Oct— 01:00No data—
Tue 20 Oct— 00:170 min—
Mon 19 Oct— 00:570 min—
Sun 18 OctEnschede Kennispark 01:05Partial coverage0 min—
Sat 17 OctEnschede Kennispark 01:05No data—
Mon 12 Oct— 00:570 min—
Sun 11 OctEnschede Kennispark 01:03Partial coverage0 min—
Fri 9 Oct— 01:01+1 min+1 min
Thu 8 Oct— 01:03+1 min+1 min
Wed 7 Oct— 00:57+1 min—
Mon 5 OctRaalte 00:570 min—
Sun 4 OctEnschede Kennispark 01:04No data—
Sat 3 OctAlmelo de Riet 00:47No data—
Sun 27 SeptEnschede Kennispark 01:04No data—
Sun 20 SeptEnschede Kennispark 01:04No data—
Sun 13 SeptEnschede Kennispark 01:03No data—
Sun 30 AugEnschede Kennispark 01:03No data—
Sun 23 AugEnschede Kennispark 01:04No data—