Train NS 1832 Amersfoort Schothorst – Breda

Amersfoort Schothorst 10:34 → Breda 12:16 Daily 1 h 42 min · 8 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 10:34 from Amersfoort Schothorst · Mon 9 Nov

Next departure 10:34 Monday · Amersfoort Schothorst
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 12 full · 8 partial · 9 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 12 full · 11 partial · 63 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Sun 18 Oct Max en route +54 min · last fix heading to Hilversum +8 min
  • Tue 6 Oct Max en route +8 min · last fix heading to Rotterdam Centraal +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 67% T n=3
  • 100% W n=3
  • 100% T n=3
  • 100% F n=4
  • 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, 23 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
10:34on time on time
10:38 / 10:41≈ on time ≈ on time
10:52 / 10:53≈ on time ≈ on time
11:08≈ on time ≈ on time
11:13 / 11:14≈ on time ≈ on time
11:20 / 11:22≈ on time ≈ on time
11:48 / 11:53≈ on time ≈ on time
12:16on time on time

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 6 NovRotterdam Centraal 12:17No data—
Thu 5 NovRotterdam Centraal 12:17Partial coverage0 min—
Wed 4 NovRotterdam Centraal 12:18Partial coverage0 min—
Tue 3 NovRotterdam Centraal 12:19Partial coverage0 min—
Mon 2 NovRotterdam Centraal 12:28Partial coverage0 min—
Sun 1 NovRotterdam Centraal 12:170 min—
Sat 31 OctRotterdam Centraal 12:170 min—
Fri 30 OctRotterdam Centraal 12:520 min—
Thu 29 OctRotterdam Centraal 12:36Partial coverage0 min—
Wed 28 OctRotterdam Centraal 12:17Partial coverage0 min—
Tue 27 OctRotterdam Centraal 12:18Partial coverage0 min—
Mon 26 OctRotterdam Centraal 12:34No data—
Sun 25 OctRotterdam Centraal 12:18No data—
Sat 24 OctRotterdam Centraal 12:170 min—
Fri 23 OctRotterdam Centraal 12:410 min—
Thu 22 OctRotterdam Centraal 12:20No data—
Wed 21 OctRotterdam Centraal 12:17No data—
Tue 20 OctRotterdam Centraal 12:17No data—
Mon 19 OctRotterdam Centraal 12:22Partial coverage0 min—
Sun 18 OctHilversum 19:38+8 min+54 min
Sat 17 OctAmsterdam Zuid 12:170 min—
Fri 16 OctRotterdam Centraal 12:170 min—
Thu 15 OctRotterdam Centraal 12:17No data—
Wed 14 OctRotterdam Centraal 12:17No data—
Tue 13 OctRotterdam Centraal 12:37No data—
Mon 12 OctRotterdam Centraal 12:180 min—
Sun 11 OctRotterdam Centraal 12:170 min—
Sat 10 OctRotterdam Centraal 12:170 min—
Fri 9 OctRotterdam Centraal 12:180 min—
Thu 8 OctRotterdam Centraal 12:17Partial coverage0 min—