Train NS 1830 Amersfoort Schothorst – Breda

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

✓ Today’s run finished

Today, last fix heading to Rotterdam Centraal at 11:47 0 min

  1. Amersfoort Schothorst10:04
  2. Amersfoort Centraal10:08
  3. Hilversum10:22
  4. Amsterdam Zuid10:43
  5. Schiphol Airport10:50
  6. Rotterdam Centraal11:18
  7. Breda11:46

Next service: tomorrow 10:04 from Amersfoort Schothorst · Fri 6 Nov

Next departure 10:04 tomorrow · Amersfoort Schothorst
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 14 full · 9 partial · 7 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 14 full · 10 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: +1 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 +11 min · last fix heading to Rotterdam Centraal +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=4
  • 50% W n=2
  • 100% T n=4
  • 100% F n=4
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

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