Train Arriva 3875 Zwolle – Emmen

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 22:22 from Zwolle · Thu 5 Nov

Next departure 22:22 today · Zwolle
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 11 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 16 full · 0 partial · 29 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 Emmen, 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
  • — T n=0
  • 100% W n=3
  • 100% T n=2
  • 100% F n=3
  • — S n=0
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
22:22on time on time
22:29 / 22:30≈ on time ≈ on time
22:36 / 22:37≈ on time ≈ on time
22:44≈ on time ≈ +1 min
22:49≈ on time ≈ +1 min
22:58 / 23:00≈ on time ≈ +1 min
23:06 / 23:07≈ on time ≈ +1 min
23:11≈ on time ≈ +1 min
23: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
Wed 4 Nov— 23:190 min—
Mon 2 Nov— 23:140 min—
Sun 1 NovEmmen Zuid 23:24+2 min+2 min
Sat 31 OctEmmen Zuid 23:25No data—
Fri 30 Oct— 23:20No data—
Thu 29 Oct— 23:170 min—
Wed 28 Oct— 23:18No data—
Tue 27 Oct— 23:20No data—
Mon 26 Oct— 23:170 min—
Sun 25 OctEmmen Zuid 23:25No data—
Sat 24 OctOmmen 23:18No data—
Fri 23 Oct— 23:19+2 min+2 min
Thu 22 Oct— 23:20No data—
Tue 20 Oct— 23:35No data—
Mon 19 Oct— 23:180 min—
Sun 18 OctEmmen Zuid 23:250 min+1 min
Sat 17 OctEmmen Zuid 23:27No data—
Fri 16 Oct— 23:180 min—
Thu 15 Oct— 23:19No data—
Wed 14 Oct— 23:160 min—
Tue 13 Oct— 23:17No data—
Mon 12 Oct— 23:180 min—
Sun 11 OctEmmen Zuid 23:25+1 min+1 min
Fri 9 Oct— 23:19+1 min+1 min
Thu 8 Oct— 23:180 min—
Wed 7 Oct— 23:160 min—
Mon 5 Oct— 23:180 min—
Sun 4 OctEmmen Zuid 23:25No data—
Sat 3 OctEmmen Zuid 23:26No data—
Sun 27 SeptEmmen Zuid 23:25No data—