Train NS 1873 Breda – Amersfoort Schothorst

Breda 18:44 → Amersfoort Schothorst 20:24 Daily 1 h 40 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 13 November +4 min

Next service: today 18:44 from Breda · Sat 14 Nov

Next departure 18:44 today · Breda
On-time · 30 days
74%
14/19 runs under 3 min
RT coverage: 13 full · 6 partial · 8 no data
On-time · 90 days
81%
22/27 runs under 3 min
RT coverage: 19 full · 8 partial · 35 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 Amersfoort Schothorst, in minutes. One bar per run.

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

Worst days

  • Thu 29 Oct Max en route +15 min · last fix heading to — +15 min
  • Sun 18 Oct Max en route +7 min · last fix heading to Hilversum +7 min
  • Tue 10 Nov Max en route +5 min · last fix heading to — +5 min
  • Mon 2 Nov Max en route +5 min · last fix heading to — +5 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Breda +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 22
  • 3–10 min 15% · 4
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 50% T n=2
  • 100% W n=3
  • 75% T n=4
  • 83% F n=6
  • 100% 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, 27 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
18:44on time on time
19:07 / 19:11≈ on time ≈ +3 min
19:37 / 19:38≈ on time ≈ +4 min
19:45 / 19:46≈ on time ≈ +4 min
19:50≈ on time ≈ +5 min
20:06 / 20:07≈ on time ≈ +5 min
20:18 / 20:20≈ on time ≈ +6 min
20:24on time +6 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
Fri 13 NovBreda 20:32Partial coverage+4 min+5 min
Thu 12 Nov— 20:29+2 min+3 min
Wed 11 Nov— 20:380 min+10 min
Tue 10 Nov— 19:19+5 min+5 min
Mon 9 Nov— 20:24+1 min—
Fri 6 NovBreda 20:24Partial coverage0 min—
Thu 5 Nov— 20:390 min—
Wed 4 Nov— 20:390 min+9 min
Tue 3 Nov— 20:28No data—
Mon 2 Nov— 20:24+5 min+5 min
Sun 1 NovAmersfoort Centraal 20:34Partial coverage0 min—
Sat 31 OctAmersfoort Centraal 20:34Partial coverage0 min—
Fri 30 OctBreda 20:310 min—
Thu 29 Oct— 20:41+15 min+15 min
Wed 28 Oct— 20:41No data—
Tue 27 Oct— 20:28No data—
Mon 26 OctSchiphol Airport 20:38No data—
Sun 25 OctAmersfoort Centraal 20:34No data—
Sat 24 OctAmersfoort Centraal 20:41Partial coverage0 min—
Fri 23 OctRotterdam Centraal 20:26Partial coverage0 min+1 min
Thu 22 OctBreda 20:26No data—
Wed 21 Oct— 20:28No data—
Tue 20 OctBreda 20:26No data—
Mon 19 Oct— 20:500 min—
Sun 18 OctHilversum 20:32+7 min+7 min
Sat 17 OctHilversum 20:260 min—
Fri 16 OctRotterdam Centraal 20:250 min—
Thu 15 Oct— 20:41No data—
Wed 14 OctRotterdam Centraal 21:03No data—
Tue 13 Oct— 20:21No data—