Train Arriva 8086 Emmen – Zwolle

Emmen 21:41 → Zwolle 22:38 Daily 0 h 57 min · 11 stops Arriva

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 21:41 from Emmen · Fri 6 Nov

Next departure 21:41 today · Emmen
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 12 full · 0 partial · 13 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 13 full · 0 partial · 30 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • — W n=0
  • 100% T n=1
  • 50% F n=2
  • 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, 13 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:41on time on time
21:44 / 21:46≈ on time ≈ on time
21:49 / 21:50≈ on time ≈ on time
21:55≈ on time ≈ +1 min
21:58 / 22:00≈ on time ≈ +1 min
22:06≈ on time ≈ +1 min
22:10≈ on time ≈ +1 min
22:16≈ on time ≈ +2 min
22:22 / 22:23≈ on time ≈ +2 min
22:30≈ on time ≈ +2 min
22:38on time +2 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:43No data—
Tue 3 Nov— 22:45No data—
Mon 2 Nov— 22:42+2 min+2 min
Sun 1 NovDalfsen 22:440 min—
Sat 31 OctDalfsen 22:44No data—
Fri 30 Oct— 22:42No data—
Thu 29 Oct— 22:420 min—
Wed 28 Oct— 22:42No data—
Tue 27 Oct— 22:450 min—
Mon 26 Oct— 22:42No data—
Sun 25 OctDalfsen 22:44No data—
Sat 24 OctDalfsen 22:45No data—
Fri 23 Oct— 22:45+3 min+3 min
Thu 22 Oct— 22:44No data—
Wed 21 Oct— 22:42No data—
Tue 20 Oct— 22:430 min—
Mon 19 Oct— 22:420 min—
Sun 18 OctDalfsen 22:46+1 min+1 min
Sat 17 OctDalfsen 22:45No data—
Wed 14 Oct— 22:40No data—
Tue 13 Oct— 22:41No data—
Mon 12 Oct— 22:420 min—
Sun 11 OctDalfsen 22:45+1 min+1 min
Sat 10 OctCoevorden 22:43+2 min+2 min
Fri 9 Oct— 22:42+2 min+2 min
Tue 6 Oct— 22:410 min—
Sun 4 OctDalfsen 22:44No data—
Sat 3 OctDalfsen 22:45No data—
Sun 27 SeptDalfsen 22:44No data—
Sat 26 SeptDalfsen 22:44No data—