Train NS 3683 Zwolle – Nijmegen

Zwolle 22:50 → Nijmegen 00:07 Daily 1 h 17 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 22:50 from Zwolle · Sun 8 Nov

Next departure 22:50 today · Zwolle
On-time · 30 days
88%
21/24 runs under 3 min
RT coverage: 18 full · 6 partial · 2 no data
On-time · 90 days
90%
26/29 runs under 3 min
RT coverage: 23 full · 6 partial · 15 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: +4 min

Last 30 days

Arrival delay at Nijmegen, in minutes. One bar per run.

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

Worst days

  • Sun 11 Oct Max en route +10 min · last fix heading to Arnhem Centraal +7 min
  • Sun 18 Oct Max en route +10 min · last fix heading to Arnhem Centraal +6 min
  • Fri 23 Oct Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 26
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=4
  • 100% T n=5
  • 80% F n=5
  • 100% S n=4
  • 33% S n=3

Stops and timetable

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

Last 90 days, 29 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:50on time on time
22:59≈ on time ≈ on time
23:06≈ on time ≈ on time
23:14 / 23:15≈ on time ≈ on time
23:26 / 23:28≈ on time ≈ on time
23:37≈ on time ≈ on time
23:49 / 23:53≈ on time ≈ on time
00:07on time on time

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
Sat 7 NovDeventer 00:08Partial coverage0 min—
Fri 6 Nov— 23:430 min—
Thu 5 Nov— 00:040 min—
Wed 4 Nov— 00:090 min—
Tue 3 Nov— 00:090 min—
Sun 1 NovArnhem Centraal 00:13Partial coverage+2 min+2 min
Sat 31 OctDeventer 00:09Partial coverage0 min—
Fri 30 Oct— 00:520 min—
Thu 29 Oct— 00:080 min—
Wed 28 Oct— 00:080 min—
Tue 27 Oct— 00:070 min—
Mon 26 Oct— 00:080 min—
Fri 23 Oct— 00:18+5 min+6 min
Thu 22 Oct— 00:080 min—
Wed 21 Oct— 00:07No data—
Tue 20 Oct— 00:160 min—
Mon 19 Oct— 23:18No data—
Sun 18 OctArnhem Centraal 00:21Partial coverage+6 min+10 min
Sat 17 OctArnhem Centraal 00:08Partial coverage0 min—
Fri 16 Oct— 00:11+2 min+6 min
Thu 15 Oct— 00:080 min—
Wed 14 Oct— 00:080 min—
Tue 13 Oct— 00:230 min—
Mon 12 Oct— 00:150 min+6 min
Sun 11 OctArnhem Centraal 00:22Partial coverage+7 min+10 min
Sat 10 Oct— 00:090 min—
Fri 9 Oct— 23:280 min—
Thu 8 Oct— 00:060 min—
Wed 7 Oct— 00:080 min—
Tue 6 Oct— 00:080 min—