Train NS 6680 Dordrecht – 's-Hertogenbosch

Dordrecht 21:58 → 's-Hertogenbosch 23:00 Daily 1 h 02 min · 10 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

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

Next departure 21:58 today · Dordrecht
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 10 full · 5 partial · 12 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 14 full · 5 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at 's-Hertogenbosch, 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 16 Oct Max en route +7 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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:58on time on time
22:01≈ on time ≈ on time
22:09 / 22:10≈ on time ≈ on time
22:17≈ on time ≈ +1 min
22:22 / 22:24≈ on time ≈ +1 min
22:32≈ on time ≈ +1 min
22:36≈ on time ≈ +1 min
22:40≈ on time ≈ +1 min
22:43 / 22:44≈ on time ≈ +1 min
23:00on time +2 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— 22:59No data—
Wed 4 Nov— 23:04+2 min+2 min
Mon 2 Nov— 22:590 min—
Sun 1 NovTilburg 23:02Partial coverage0 min—
Sat 31 OctTilburg 23:01Partial coverage0 min—
Fri 30 Oct— 23:12No data—
Thu 29 Oct— 23:01+1 min+1 min
Wed 28 Oct— 23:01No data—
Tue 27 Oct— 23:02No data—
Mon 26 Oct— 23:010 min—
Sun 25 OctTilburg 23:02No data—
Sat 24 OctTilburg Reeshof 23:03No data—
Fri 23 Oct— 23:030 min—
Thu 22 Oct— 23:04No data—
Wed 21 Oct— 23:01No data—
Tue 20 Oct— 23:010 min—
Mon 19 Oct— 23:00No data—
Sun 18 OctTilburg 23:03Partial coverage0 min+1 min
Sat 17 OctTilburg 23:02No data—
Fri 16 Oct— 23:14+7 min+7 min
Thu 15 Oct— 23:03No data—
Wed 14 Oct— 23:01No data—
Tue 13 Oct— 23:020 min—
Mon 12 Oct— 23:01+2 min+2 min
Sun 11 OctTilburg 23:01Partial coverage0 min—
Sat 10 OctDordrecht Zuid 23:04Partial coverage+1 min+2 min
Fri 9 Oct— 23:010 min—
Thu 8 Oct— 23:020 min—
Wed 7 Oct— 23:010 min—
Tue 6 Oct— 23:010 min—