Train NS 6678 Dordrecht – Nijmegen

Dordrecht 21:28 → Nijmegen 23:13 Daily 1 h 45 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November +3 min

Next service: today 21:28 from Dordrecht · Sat 7 Nov

Next departure 21:28 today · Dordrecht
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 15 full · 2 partial · 11 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 19 full · 2 partial · 27 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Mon 12 Oct Max en route +5 min · last fix heading to — +5 min
  • Sat 10 Oct Max en route +5 min · last fix heading to Gilze-Rijen +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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
21:28on time on time
21:31≈ on time ≈ on time
21:39 / 21:40≈ on time ≈ +1 min
21:47≈ on time ≈ +1 min
21:52 / 21:54≈ on time ≈ +1 min
22:02≈ on time ≈ +1 min
22:06≈ on time ≈ +1 min
22:10≈ on time ≈ +2 min
22:13 / 22:14≈ on time ≈ +2 min
22:30 / 22:32≈ +1 min ≈ +2 min
22:35≈ +1 min ≈ +2 min
22:39≈ +1 min ≈ +2 min
22:46≈ +1 min ≈ +2 min
22:49≈ +1 min ≈ +2 min
22:55≈ +1 min ≈ +3 min
23:01≈ +1 min ≈ +3 min
23:05≈ +1 min ≈ +3 min
23:08≈ +1 min ≈ +3 min
23:13+1 min +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
Fri 6 Nov— 23:17+3 min+4 min
Thu 5 Nov— 23:14No data—
Wed 4 Nov— 23:14+1 min—
Mon 2 Nov— 23:140 min—
Sun 1 NovNijmegen Goffert 23:23+3 min+3 min
Sat 31 OctOss West 23:000 min—
Fri 30 Oct— 23:140 min—
Thu 29 Oct— 23:140 min—
Wed 28 Oct— 23:15No data—
Tue 27 Oct— 23:18No data—
Mon 26 Oct— 23:140 min—
Sun 25 OctNijmegen Goffert 23:25No data—
Sat 24 Oct's-Hertogenbosch Oost 23:310 min—
Fri 23 Oct— 23:16+2 min+2 min
Thu 22 Oct— 23:20No data—
Wed 21 Oct— 23:17No data—
Tue 20 Oct— 23:23No data—
Mon 19 Oct— 22:31No data—
Sun 18 OctNijmegen Goffert 23:23Partial coverage0 min—
Sat 17 OctNijmegen Goffert 23:26No data—
Fri 16 Oct— 23:17+1 min+3 min
Thu 15 Oct— 23:29No data—
Wed 14 Oct— 23:16+1 min+3 min
Tue 13 Oct— 23:15No data—
Mon 12 Oct— 23:17+5 min+5 min
Sun 11 OctNijmegen Goffert 23:23Partial coverage0 min—
Sat 10 OctGilze-Rijen 23:18+4 min+5 min
Fri 9 Oct— 23:15+2 min+2 min
Thu 8 Oct— 23:18+2 min+3 min
Wed 7 Oct— 23:18+2 min+3 min