Train NS 6650 Zwijndrecht – Nijmegen

Zwijndrecht 14:22 → Nijmegen 16:13 Daily 1 h 51 min · 20 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Nijmegen Goffert at 16:24 0 min

  1. Zwijndrecht14:22
  2. Lage Zwaluwe14:39
  3. Gilze-Rijen15:01
  4. 's-Hertogenbosch15:29
  5. Oss West15:46
  6. Nijmegen Goffert16:09
  7. Nijmegen16:13

Next service: tomorrow 14:22 from Zwijndrecht · Mon 9 Nov

Next departure 14:22 tomorrow · Zwijndrecht
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 14 full · 1 partial · 15 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 19 full · 1 partial · 69 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: +1 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
14:22on time on time
14:26 / 14:28≈ on time ≈ on time
14:31≈ on time ≈ on time
14:39 / 14:40≈ on time ≈ on time
14:47≈ on time ≈ on time
14:52 / 14:53≈ on time ≈ on time
15:01≈ on time ≈ on time
15:05≈ on time ≈ on time
15:09≈ on time ≈ on time
15:12 / 15:13≈ on time ≈ on time
15:29 / 15:30≈ on time ≈ +1 min
15:33≈ on time ≈ +1 min
15:38≈ on time ≈ +1 min
15:46≈ on time ≈ +1 min
15:50≈ on time ≈ +1 min
15:56≈ on time ≈ +1 min
16:01≈ on time ≈ +1 min
16:06≈ on time ≈ +1 min
16:09≈ on time ≈ +1 min
16:13on 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
Sun 8 NovNijmegen Goffert 16:24Partial coverage0 min—
Sat 7 NovArnhem Zuid 16:44+1 min+1 min
Fri 6 NovArnhem Zuid 16:44No data—
Thu 5 NovArnhem Zuid 16:44No data—
Wed 4 NovArnhem Zuid 16:440 min—
Tue 3 NovArnhem Zuid 16:440 min—
Mon 2 NovArnhem Zuid 16:43No data—
Sun 1 NovNijmegen Goffert 16:230 min—
Sat 31 OctNijmegen Goffert 16:240 min—
Fri 30 OctNijmegen Goffert 16:230 min—
Thu 29 OctNijmegen Goffert 16:23No data—
Wed 28 OctNijmegen Goffert 16:230 min—
Tue 27 OctNijmegen Goffert 16:32No data—
Mon 26 OctNijmegen Goffert 16:24No data—
Sun 25 OctNijmegen Goffert 16:27No data—
Sat 24 OctArnhem Zuid 16:450 min—
Fri 23 OctArnhem Zuid 16:46No data—
Thu 22 OctArnhem Zuid 16:46No data—
Wed 21 OctArnhem Zuid 16:46No data—
Tue 20 OctArnhem Zuid 16:460 min—
Mon 19 OctArnhem Zuid 16:450 min—
Sun 18 OctNijmegen Goffert 16:230 min—
Sat 17 OctArnhem Zuid 16:45No data—
Fri 16 OctArnhem Zuid 16:49No data—
Thu 15 OctArnhem Zuid 16:44No data—
Wed 14 OctArnhem Zuid 16:44No data—
Tue 13 OctArnhem Zuid 16:45No data—
Mon 12 OctArnhem Zuid 16:45+2 min+2 min
Sun 11 OctNijmegen Goffert 16:25+1 min+2 min
Sat 10 OctArnhem Zuid 16:430 min—