Train Arriva 3859 Zwolle – Emmen

Zwolle 18:22 → Emmen 19:15 Daily 0 h 53 min · 9 stops Arriva

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 18:22 from Zwolle · Fri 6 Nov

Next departure 18:22 today · Zwolle
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 5 full · 8 partial · 14 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 7 full · 8 partial · 52 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Emmen, 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 Emmen Zuid +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=1
  • 50% F n=2
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 15 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
18:22on time on time
18:29 / 18:30≈ on time ≈ on time
18:36 / 18:37≈ on time ≈ on time
18:44≈ on time ≈ on time
18:49≈ on time ≈ on time
18:58 / 19:00≈ on time ≈ on time
19:06 / 19:07≈ on time ≈ on time
19:11≈ on time ≈ +1 min
19:15on 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 5 Nov— 19:19No data—
Wed 4 Nov— 19:19No data—
Mon 2 NovDalfsen 19:19Partial coverage0 min—
Sun 1 NovEmmen Zuid 19:27Partial coverage+2 min+2 min
Sat 31 OctEmmen Zuid 19:25Partial coverage0 min—
Fri 30 OctHardenberg 19:03No data—
Thu 29 Oct— 19:190 min—
Wed 28 Oct— 19:200 min—
Tue 27 Oct— 19:220 min—
Mon 26 Oct— 19:21No data—
Sun 25 OctEmmen Zuid 19:25No data—
Sat 24 OctEmmen Zuid 19:25No data—
Fri 23 OctEmmen Zuid 19:25Partial coverage+3 min+3 min
Thu 22 OctMariënberg 19:29No data—
Wed 21 OctOmmen 19:20No data—
Tue 20 OctMariënberg 18:50Partial coverage0 min—
Mon 19 OctOmmen 19:17No data—
Sun 18 OctEmmen Zuid 19:27Partial coverage+2 min+2 min
Sat 17 OctEmmen Zuid 19:25No data—
Fri 16 OctEmmen Zuid 19:25No data—
Thu 15 OctDalfsen 19:18No data—
Wed 14 OctEmmen Zuid 19:25No data—
Tue 13 OctOmmen 19:17No data—
Mon 12 OctMariënberg 19:190 min—
Sun 11 OctEmmen Zuid 19:25Partial coverage0 min—
Sat 10 OctEmmen Zuid 19:27Partial coverage+1 min—
Fri 9 OctZwolle 22:17+1 min+1 min
Wed 7 Oct— 19:170 min—
Mon 5 Oct— 19:190 min—
Sun 4 OctEmmen Zuid 19:25No data—