Train NS 6622 Breda – Nijmegen

Breda 07:55 → Nijmegen 09:13 Daily 1 h 18 min · 15 stops NS (Nederlandse Spoorwegen)

Running now · updated 08:22

Heading to Nijmegen 0 min

Estimated arrival at Nijmegen 09:13 · 130 km/h

  1. Breda07:55
  2. Tilburg Reeshof08:06
  3. 's-Hertogenbosch08:30
  4. Rosmalen08:39
  5. Oss08:49
  6. Nijmegen Dukenburg09:05
  7. Nijmegen09:13

Today it is running no worse than usual: typical arrival delay is 0 min; 87% of the last 23 runs arrived on time.

On-time · 30 days
87%
20/23 runs under 3 min
RT coverage: 22 full · 1 partial · 7 no data
On-time · 90 days
90%
28/31 runs under 3 min
RT coverage: 30 full · 1 partial · 58 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Tue 10 Nov Max en route +10 min · last fix heading to Arnhem Zuid +8 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Arnhem Zuid +4 min
  • Sat 17 Oct Max en route +4 min · last fix heading to Arnhem Zuid +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 28
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 75% T n=4
  • 75% W n=4
  • 100% T n=4
  • 100% F n=4
  • 83% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 31 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 10Today
07:55on time on time
08:02≈ on time ≈ on time
08:06≈ on time ≈ on time
08:10≈ on time ≈ +1 min
08:13 / 08:14≈ on time ≈ +1 min
08:30 / 08:32≈ on time ≈ +1 min
08:35≈ on time ≈ +1 min
08:39≈ on time ≈ +2 min
08:46≈ on time ≈ +2 min
08:49≈ on time ≈ +2 min
08:55≈ on time ≈ +2 min
09:01≈ on time ≈ +2 min
09:05≈ on time ≈ +2 min
09:08≈ on time ≈ +3 min
09:13on time +3 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 15 NovTilburg 08:19Partial coverage0 min—
Sat 14 NovArnhem Zuid 09:44+2 min+2 min
Fri 13 NovArnhem Zuid 09:440 min—
Thu 12 NovArnhem Zuid 09:500 min+3 min
Wed 11 NovArnhem Zuid 09:44+2 min+2 min
Tue 10 NovArnhem Zuid 09:52+8 min+10 min
Mon 9 NovArnhem Zuid 09:440 min—
Sun 8 NovNijmegen Goffert 09:24+2 min+3 min
Sat 7 NovArnhem Zuid 09:440 min+3 min
Fri 6 NovArnhem Zuid 09:47No data—
Thu 5 NovArnhem Zuid 09:49No data—
Wed 4 NovArnhem Zuid 09:44+4 min+4 min
Tue 3 NovArnhem Zuid 09:44No data—
Mon 2 NovArnhem Zuid 09:44No data—
Sun 1 NovNijmegen Goffert 09:26+3 min+3 min
Sat 31 OctNijmegen Goffert 09:230 min—
Fri 30 OctNijmegen Goffert 09:230 min—
Thu 29 OctNijmegen Goffert 09:230 min—
Wed 28 OctNijmegen Goffert 09:25No data—
Tue 27 OctWijchen 09:440 min—
Mon 26 OctNijmegen Goffert 09:240 min—
Sun 25 OctNijmegen Goffert 09:25No data—
Sat 24 OctArnhem Zuid 09:48+2 min+3 min
Fri 23 OctArnhem Zuid 09:460 min—
Thu 22 OctArnhem Zuid 09:460 min—
Wed 21 OctArnhem Zuid 09:48No data—
Tue 20 OctArnhem Zuid 09:460 min—
Mon 19 OctArnhem Zuid 09:430 min—
Sun 18 OctNijmegen Goffert 09:23+3 min+3 min
Sat 17 OctArnhem Zuid 09:47+4 min+4 min