Train NS 1846 Amersfoort Schothorst – Breda

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

✓ Today’s run finished

Today, last fix heading to Rotterdam Centraal at 16:02 +9 min

  1. Amersfoort Schothorst14:04
  2. Amersfoort Centraal14:08
  3. Hilversum14:22
  4. Amsterdam Zuid14:43
  5. Schiphol Airport14:50
  6. Rotterdam Centraal15:18
  7. Breda15:46

Next service: tomorrow 14:04 from Amersfoort Schothorst · Sat 14 Nov

Next departure 14:04 tomorrow · Amersfoort Schothorst
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 16 full · 4 partial · 8 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 21 full · 7 partial · 57 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: +2 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

  • Tue 10 Nov Max en route +10 min · last fix heading to Rotterdam Centraal +10 min
  • Fri 13 Nov Max en route +9 min · last fix heading to Rotterdam Centraal +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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