Train NS 6652 Zwijndrecht – Nijmegen

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

Running now · updated 14:57

Heading to Nijmegen 0 min

Estimated arrival at Nijmegen 16:43

  1. Zwijndrecht14:52
  2. Lage Zwaluwe15:09
  3. Gilze-Rijen15:31
  4. 's-Hertogenbosch15:59
  5. Oss West16:16
  6. Wijchen16:31
  7. Nijmegen16:43

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 22 runs arrived on time.

On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 21 full · 1 partial · 8 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 26 full · 1 partial · 62 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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 10Today
14:52on time on time
14:56 / 14:58≈ on time ≈ on time
15:01≈ on time ≈ on time
15:09 / 15:10≈ on time ≈ on time
15:17≈ on time ≈ on time
15:22 / 15:23≈ on time ≈ on time
15:31≈ on time ≈ on time
15:35≈ on time ≈ on time
15:39≈ on time ≈ on time
15:42 / 15:43≈ on time ≈ on time
15:59 / 16:00≈ on time ≈ +1 min
16:03≈ on time ≈ +1 min
16:08≈ on time ≈ +1 min
16:16≈ on time ≈ +1 min
16:20≈ on time ≈ +1 min
16:26≈ on time ≈ +1 min
16:31≈ on time ≈ +1 min
16:35≈ on time ≈ +1 min
16:38≈ on time ≈ +1 min
16:43on 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 NovDordrecht 14:54Partial coverage0 min—
Sat 7 NovArnhem Zuid 17:14+1 min+1 min
Fri 6 NovArnhem Zuid 17:140 min—
Thu 5 NovArnhem Zuid 17:130 min—
Wed 4 NovArnhem Zuid 17:130 min—
Tue 3 NovArnhem Zuid 17:13No data—
Mon 2 NovArnhem Zuid 17:13No data—
Sun 1 NovNijmegen Goffert 16:530 min—
Sat 31 OctNijmegen Goffert 16:530 min—
Fri 30 Oct's-Hertogenbosch Oost 17:130 min—
Thu 29 OctNijmegen Goffert 16:530 min—
Wed 28 OctNijmegen Goffert 16:540 min—
Tue 27 OctNijmegen Goffert 16:530 min—
Mon 26 OctNijmegen Goffert 16:540 min—
Sun 25 OctNijmegen Goffert 16:54No data—
Sat 24 OctArnhem Zuid 17:17+3 min+3 min
Fri 23 OctArnhem Zuid 17:240 min—
Thu 22 OctArnhem Zuid 17:14No data—
Wed 21 OctArnhem Zuid 17:140 min—
Tue 20 OctArnhem Zuid 17:140 min—
Mon 19 OctArnhem Zuid 17:140 min—
Sun 18 OctNijmegen Goffert 16:55+1 min+3 min
Sat 17 OctArnhem Zuid 17:140 min—
Fri 16 OctArnhem Zuid 17:14No data—
Thu 15 OctArnhem Zuid 17:14No data—
Wed 14 OctArnhem Zuid 17:17No data—
Tue 13 OctArnhem Zuid 17:14No data—
Mon 12 OctArnhem Zuid 17:130 min—
Sun 11 OctNijmegen Goffert 16:53+1 min—
Sat 10 OctArnhem Zuid 17:140 min—