Train NS 6675 Nijmegen – Dordrecht

Nijmegen 20:20 → Dordrecht 22:02 Daily 1 h 42 min · 19 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +4 min

Next service: today 20:20 from Nijmegen · Thu 5 Nov

Next departure 20:20 today · Nijmegen
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 17 full · 6 partial · 6 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 19 full · 6 partial · 28 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: +2 min

Last 30 days

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

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

Worst days

  • Wed 4 Nov Max en route +5 min · last fix heading to — +4 min
  • Sun 18 Oct Max en route +3 min · last fix heading to Dordrecht Zuid +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 25 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
20:20on time on time
20:23≈ on time ≈ on time
20:26≈ on time ≈ on time
20:31≈ on time ≈ on time
20:36≈ on time ≈ on time
20:42 / 20:43≈ on time ≈ on time
20:46≈ on time ≈ on time
20:53≈ on time ≈ on time
20:57≈ on time ≈ on time
21:00 / 21:02≈ on time ≈ +1 min
21:16 / 21:18≈ on time ≈ +1 min
21:21≈ on time ≈ +1 min
21:25≈ on time ≈ +1 min
21:29≈ on time ≈ +1 min
21:36 / 21:39≈ on time ≈ +1 min
21:43≈ on time ≈ +1 min
21:50≈ on time ≈ +1 min
21:58≈ on time ≈ +1 min
22:02on 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
Wed 4 Nov— 22:09+4 min+5 min
Tue 3 Nov— 22:240 min—
Mon 2 Nov— 22:030 min—
Sun 1 NovDordrecht Zuid 22:12Partial coverage0 min—
Sat 31 OctDordrecht Zuid 22:120 min—
Fri 30 Oct— 22:030 min—
Thu 29 Oct— 22:03+1 min+1 min
Wed 28 Oct— 22:03No data—
Tue 27 Oct— 22:040 min—
Mon 26 Oct— 22:040 min—
Sun 25 OctDordrecht Zuid 22:12No data—
Sat 24 OctDordrecht Zuid 22:17Partial coverage0 min—
Fri 23 Oct— 22:06+1 min+2 min
Thu 22 Oct— 22:04No data—
Wed 21 Oct— 22:030 min—
Tue 20 Oct— 22:030 min—
Mon 19 Oct— 20:46No data—
Sun 18 OctDordrecht Zuid 22:15Partial coverage+3 min+3 min
Sat 17 OctDordrecht Zuid 22:12Partial coverage0 min—
Fri 16 Oct— 21:090 min—
Thu 15 Oct— 22:03No data—
Wed 14 Oct— 22:03No data—
Tue 13 Oct— 22:040 min—
Mon 12 Oct— 22:030 min—
Sun 11 OctDordrecht Zuid 22:12Partial coverage0 min—
Sat 10 OctDordrecht Zuid 22:12Partial coverage+1 min—
Fri 9 Oct— 22:030 min—
Thu 8 Oct— 22:040 min—
Wed 7 Oct— 22:06+2 min+2 min
Tue 6 Oct— 22:040 min—