Train NS 1854 Amersfoort Schothorst – Breda

Amersfoort Schothorst 16:04 → Breda 17:46 Daily 1 h 42 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 16:04 from Amersfoort Schothorst · Thu 5 Nov

Next departure 16:04 today · Amersfoort Schothorst
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 12 full · 6 partial · 11 no data
On-time · 90 days
85%
17/20 runs under 3 min
RT coverage: 13 full · 7 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Wed 7 Oct Max en route +10 min · last fix heading to Amersfoort Centraal +10 min
  • Sat 24 Oct Max en route +9 min · last fix heading to Rotterdam Centraal +9 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Rotterdam Centraal +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 17
  • 3–10 min 10% · 2
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
16:04on time on time
16:08 / 16:11≈ on time ≈ on time
16:22 / 16:23≈ on time ≈ +1 min
16:38≈ on time ≈ +1 min
16:43 / 16:44≈ on time ≈ +1 min
16:50 / 16:52≈ on time ≈ +2 min
17:18 / 17:23≈ on time ≈ +3 min
17:46on time +4 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 NovRotterdam Centraal 17:49Partial coverage0 min—
Tue 3 NovRotterdam Centraal 17:47No data—
Mon 2 NovRotterdam Centraal 17:47No data—
Sun 1 NovRotterdam Centraal 17:370 min—
Sat 31 OctRotterdam Centraal 17:470 min—
Fri 30 OctRotterdam Centraal 17:38No data—
Thu 29 OctRotterdam Centraal 18:04No data—
Wed 28 OctRotterdam Centraal 17:480 min—
Tue 27 OctRotterdam Centraal 17:48Partial coverage0 min—
Mon 26 OctRotterdam Centraal 17:47Partial coverage+1 min+1 min
Sun 25 OctRotterdam Centraal 18:07No data—
Sat 24 OctRotterdam Centraal 18:11+9 min+9 min
Fri 23 OctRotterdam Centraal 18:200 min—
Thu 22 OctRotterdam Centraal 17:47No data—
Wed 21 OctRotterdam Centraal 18:12No data—
Tue 20 OctRotterdam Centraal 18:06No data—
Mon 19 OctRotterdam Centraal 17:48Partial coverage0 min—
Sun 18 OctRotterdam Centraal 17:50+4 min+4 min
Sat 17 OctRotterdam Centraal 17:470 min—
Fri 16 OctRotterdam Centraal 17:370 min—
Thu 15 OctRotterdam Centraal 17:37No data—
Wed 14 OctRotterdam Centraal 17:48No data—
Tue 13 OctRotterdam Centraal 17:48No data—
Mon 12 OctRotterdam Centraal 17:500 min—
Sun 11 OctRotterdam Centraal 17:470 min—
Sat 10 OctRotterdam Centraal 17:37+1 min+1 min
Fri 9 OctRotterdam Centraal 17:480 min—
Thu 8 OctRotterdam Centraal 17:47Partial coverage+1 min+1 min
Wed 7 OctAmersfoort Centraal 18:04Partial coverage+10 min+10 min
Tue 6 OctRotterdam Centraal 17:47Partial coverage0 min+1 min