Train Arriva 8082 Emmen – Zwolle

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

It has not run yet today

Last recorded run: Monday 2 November 0 min

Next service: today 20:41 from Emmen · Thu 5 Nov

Next departure 20:41 today · Emmen
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 13 full · 0 partial · 10 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 14 full · 0 partial · 28 no data
Typical delay
+1min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 14
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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