Train NS 3687 Zwolle – Arnhem Centraal

Zwolle 23:50 → Arnhem Centraal 00:49 Daily 0 h 59 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 23:50 from Zwolle · Fri 20 Nov

Next departure 23:50 today · Zwolle
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 14 full · 3 partial · 0 no data
On-time · 90 days
78%
25/32 runs under 3 min
RT coverage: 25 full · 7 partial · 6 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Arnhem Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 14 Nov Max en route +39 min · last fix heading to — +9 min
  • Mon 5 Oct Max en route +9 min · last fix heading to Olst +9 min
  • Sun 18 Oct Max en route +7 min · last fix heading to Dieren +7 min
  • Sun 11 Oct Max en route +7 min · last fix heading to Dieren +7 min
  • Sun 8 Nov Max en route +6 min · last fix heading to Dieren +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 25
  • 3–10 min 22% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 100% T n=3
  • 100% W n=5
  • 100% T n=4
  • 100% F n=4
  • 60% S n=5
  • 40% S n=5

Stops and timetable

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

Last 90 days, 32 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:50on time +1 min
23:59≈ on time ≈ +1 min
00:06≈ on time ≈ +1 min
00:14 / 00:15≈ on time ≈ +1 min
00:26 / 00:28≈ on time ≈ +2 min
00:37≈ on time ≈ +3 min
00:49on time +3 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 19 Nov— 00:590 min—
Wed 18 Nov— 00:490 min+28 min
Mon 16 Nov— 00:490 min—
Sun 15 NovDieren 00:52Partial coverage0 min+1 min
Sat 14 Nov— 01:07+9 min+39 min
Thu 12 Nov— 00:540 min—
Wed 11 Nov— 00:49+1 min—
Mon 9 Nov— 00:58+4 min+4 min
Sun 8 NovDieren 00:59Partial coverage+5 min+6 min
Sat 7 Nov— 00:490 min—
Fri 6 Nov— 00:54+3 min+4 min
Wed 4 Nov— 00:54+2 min+2 min
Tue 3 Nov— 00:490 min—
Mon 2 Nov— 00:54+2 min+2 min
Sun 1 NovDieren 00:49Partial coverage0 min+1 min
Sat 31 Oct— 00:500 min—
Fri 30 Oct— 01:080 min—
Mon 19 Oct— 00:53+2 min+3 min
Sun 18 OctDieren 01:00Partial coverage+7 min+7 min
Sat 17 OctDieren 01:03Partial coverage0 min—
Fri 16 Oct— 00:500 min—
Thu 15 Oct— 01:010 min—
Wed 14 Oct— 00:510 min—
Tue 13 Oct— 01:160 min—
Mon 12 Oct— 01:130 min—
Sun 11 OctDieren 01:04Partial coverage+7 min+7 min
Sat 10 Oct— 00:53+3 min+3 min
Fri 9 Oct— 00:53+2 min+2 min
Thu 8 Oct— 00:53+1 min+1 min
Wed 7 Oct— 00:50+1 min+1 min