Train NS 6668 Dordrecht – Nijmegen

Dordrecht 18:58 → Nijmegen 20:43 Daily 1 h 45 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 18:58 from Dordrecht · Fri 6 Nov

Next departure 18:58 today · Dordrecht
On-time · 30 days
72%
13/18 runs under 3 min
RT coverage: 18 full · 0 partial · 11 no data
On-time · 90 days
76%
16/21 runs under 3 min
RT coverage: 21 full · 0 partial · 40 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: +8 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

  • Fri 23 Oct Max en route +12 min · last fix heading to Breda +11 min
  • Fri 9 Oct Max en route +11 min · last fix heading to — +10 min
  • Wed 4 Nov Max en route +7 min · last fix heading to — +7 min
  • Thu 29 Oct Max en route +3 min · last fix heading to — +3 min
  • Fri 16 Oct Max en route +3 min · last fix heading to Tilburg +3 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 76% · 16
  • 3–10 min 19% · 4
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=3
  • 75% W n=4
  • 50% T n=2
  • 25% F n=4
  • 100% 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
18:58on time on time
19:01≈ on time ≈ on time
19:09 / 19:10≈ on time ≈ +1 min
19:17≈ on time ≈ +1 min
19:22 / 19:24≈ on time ≈ +2 min
19:32≈ on time ≈ +2 min
19:36≈ on time ≈ +3 min
19:40≈ on time ≈ +3 min
19:43 / 19:44≈ on time ≈ +3 min
20:00 / 20:02≈ on time ≈ +4 min
20:05≈ on time ≈ +5 min
20:09≈ on time ≈ +5 min
20:16≈ on time ≈ +5 min
20:19 / 20:20≈ on time ≈ +6 min
20:26≈ on time ≈ +6 min
20:32≈ on time ≈ +7 min
20:36≈ on time ≈ +7 min
20:39≈ on time ≈ +7 min
20:43on time +7 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 5 Nov— 20:48No data—
Wed 4 Nov— 20:59+7 min+7 min
Tue 3 Nov— 20:450 min—
Mon 2 Nov— 19:24No data—
Sun 1 NovNijmegen Goffert 20:53+1 min—
Sat 31 OctNijmegen Goffert 20:520 min—
Fri 30 Oct— 20:440 min—
Thu 29 Oct— 20:46+3 min+3 min
Wed 28 Oct— 20:450 min—
Tue 27 Oct— 21:480 min—
Mon 26 OctTilburg 20:51No data—
Sun 25 OctNijmegen Goffert 20:53No data—
Sat 24 OctNijmegen Goffert 20:58No data—
Fri 23 OctBreda 20:58+11 min+12 min
Thu 22 Oct— 21:11No data—
Wed 21 Oct— 20:470 min—
Tue 20 Oct— 20:51No data—
Mon 19 Oct— 20:010 min—
Sun 18 OctNijmegen Goffert 20:530 min—
Sat 17 OctNijmegen Goffert 20:530 min—
Fri 16 OctTilburg 20:47+3 min+3 min
Thu 15 Oct— 20:44No data—
Wed 14 OctTilburg 20:44No data—
Tue 13 Oct— 20:45No data—
Mon 12 Oct— 20:47No data—
Sun 11 OctNijmegen Goffert 20:53+1 min—
Sat 10 OctNijmegen Goffert 20:53+1 min—
Fri 9 Oct— 20:56+10 min+11 min
Thu 8 Oct— 02:250 min—
Wed 7 Oct— 20:440 min—