Train NS 6681 Nijmegen – Breda

Nijmegen 21:50 → Breda 23:06 Daily 1 h 16 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 21:50 from Nijmegen · Sun 8 Nov

Next departure 21:50 today · Nijmegen
On-time · 30 days
86%
18/21 runs under 3 min
RT coverage: 17 full · 4 partial · 7 no data
On-time · 90 days
81%
21/26 runs under 3 min
RT coverage: 22 full · 4 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

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

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

Worst days

  • Tue 6 Oct Max en route +25 min · last fix heading to — +22 min
  • Fri 16 Oct Max en route +21 min · last fix heading to — +21 min
  • Fri 23 Oct Max en route +13 min · last fix heading to — +13 min
  • Thu 29 Oct Max en route +3 min · last fix heading to — +3 min
  • Fri 9 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 21
  • 3–10 min 8% · 2
  • 10–30 min 12% · 3
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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:50on time +3 min
21:53≈ on time ≈ +6 min
21:56≈ on time ≈ +7 min
22:01≈ on time ≈ +7 min
22:06≈ on time ≈ +7 min
22:12 / 22:13≈ on time ≈ +8 min
22:16≈ on time ≈ +8 min
22:23≈ on time ≈ +9 min
22:27≈ on time ≈ +9 min
22:30 / 22:32≈ on time ≈ +9 min
22:46 / 22:48≈ on time ≈ +11 min
22:51≈ on time ≈ +11 min
22:55≈ on time ≈ +11 min
22:59≈ on time ≈ +12 min
23:06on time +12 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
Sat 7 NovGilze-Rijen 23:13Partial coverage0 min—
Fri 6 Nov— 23:08+1 min—
Thu 5 Nov— 23:14No data—
Wed 4 Nov— 23:070 min—
Mon 2 Nov— 23:070 min—
Sun 1 Nov's-Hertogenbosch Oost 22:43+1 min+2 min
Sat 31 OctGilze-Rijen 23:13Partial coverage0 min—
Fri 30 Oct— 23:08No data—
Thu 29 Oct— 23:14+3 min+3 min
Wed 28 Oct— 23:07No data—
Tue 27 Oct— 23:100 min—
Mon 26 Oct— 23:07No data—
Sun 25 Oct's-Hertogenbosch Oost 23:02No data—
Sat 24 Oct's-Hertogenbosch 23:24Partial coverage0 min—
Fri 23 Oct— 23:32+13 min+13 min
Thu 22 Oct— 23:080 min—
Wed 21 Oct— 23:09No data—
Tue 20 Oct— 23:070 min—
Mon 19 Oct— 22:160 min—
Sun 18 Oct's-Hertogenbosch Oost 22:43+1 min+1 min
Sat 17 OctGilze-Rijen 23:13No data—
Fri 16 Oct— 23:48+21 min+21 min
Thu 15 Oct— 23:100 min—
Wed 14 Oct— 23:070 min—
Tue 13 Oct— 23:080 min—
Mon 12 Oct— 23:070 min—
Sun 11 Oct's-Hertogenbosch Oost 22:420 min—
Sat 10 OctWijchen 23:08Partial coverage+2 min+2 min
Fri 9 Oct— 23:11+3 min+3 min
Thu 8 Oct— 23:080 min—