Train NS 6626 Breda – Nijmegen

Breda 08:53 → Nijmegen 10:13 Daily 1 h 20 min · 15 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 8 November +1 min

Next service: today 08:53 from Breda · Mon 9 Nov

Next departure 08:53 today · Breda
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 16 full · 1 partial · 12 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 21 full · 1 partial · 66 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: +1 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 9 Oct Max en route +13 min · last fix heading to Arnhem Zuid +13 min
  • Sat 7 Nov Max en route +4 min · last fix heading to Arnhem Zuid +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 20
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
08:53on time on time
09:01≈ on time ≈ on time
09:05≈ on time ≈ on time
09:09≈ on time ≈ on time
09:12 / 09:13≈ on time ≈ on time
09:29 / 09:30≈ on time ≈ +1 min
09:33≈ on time ≈ +1 min
09:38≈ on time ≈ +1 min
09:46≈ on time ≈ +1 min
09:50≈ on time ≈ +1 min
09:56≈ on time ≈ +1 min
10:01≈ on time ≈ +1 min
10:06≈ on time ≈ +1 min
10:09≈ on time ≈ +1 min
10:13on 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
Sun 8 NovNijmegen Goffert 10:24Partial coverage+1 min+2 min
Sat 7 NovArnhem Zuid 10:44+4 min+4 min
Fri 6 NovArnhem Zuid 10:44No data—
Thu 5 NovArnhem Zuid 10:44No data—
Wed 4 NovArnhem Zuid 10:440 min—
Tue 3 NovArnhem Zuid 10:44No data—
Mon 2 NovArnhem Zuid 10:480 min—
Sun 1 NovNijmegen Goffert 10:24No data—
Sat 31 OctNijmegen Goffert 10:24+1 min+1 min
Fri 30 OctNijmegen Goffert 10:230 min—
Thu 29 OctNijmegen Goffert 10:230 min—
Wed 28 OctNijmegen Goffert 10:230 min—
Tue 27 OctNijmegen Goffert 10:230 min—
Mon 26 OctNijmegen Goffert 10:230 min—
Sun 25 OctNijmegen Goffert 10:24No data—
Sat 24 OctArnhem Zuid 10:460 min—
Fri 23 OctArnhem Zuid 10:460 min—
Thu 22 OctArnhem Zuid 10:540 min—
Wed 21 OctArnhem Zuid 10:45No data—
Tue 20 OctArnhem Zuid 10:45No data—
Mon 19 OctArnhem Zuid 10:500 min—
Sun 18 OctNijmegen Goffert 10:230 min+1 min
Sat 17 OctArnhem Zuid 10:440 min—
Fri 16 OctArnhem Zuid 10:44No data—
Thu 15 Oct's-Hertogenbosch 10:58No data—
Wed 14 OctArnhem Zuid 10:44No data—
Tue 13 OctArnhem Zuid 10:44No data—
Mon 12 OctArnhem Zuid 10:45No data—
Sun 11 OctNijmegen Goffert 10:25+2 min+3 min
Sat 10 OctArnhem Zuid 10:440 min—