Train NS 1831 Breda – Amersfoort Schothorst

Breda 08:14 → Amersfoort Schothorst 09:54 Daily 1 h 40 min · 8 stops NS (Nederlandse Spoorwegen)

Running now · updated 08:14

Heading to Amersfoort Schothorst 0 min

Estimated arrival at Amersfoort Schothorst 09:54 · 3 km/h

  1. Breda08:14
  2. Rotterdam Centraal08:37
  3. Schiphol Airport09:07
  4. Duivendrecht09:20
  5. Hilversum09:36
  6. Amersfoort Centraal09:48
  7. Amersfoort Schothorst09:54

Today it is running no worse than usual: typical arrival delay is 0 min; 95% of the last 21 runs arrived on time.

On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 18 full · 3 partial · 7 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 25 full · 4 partial · 54 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 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

  • Sun 1 Nov Max en route +5 min · last fix heading to Amersfoort Centraal +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=5
  • 100% T n=3
  • 100% F n=5
  • 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, 29 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 10Today
08:14on time on time
08:37 / 08:41≈ on time ≈ on time
09:07 / 09:08≈ on time ≈ +1 min
09:15 / 09:16≈ on time ≈ +1 min
09:20≈ on time ≈ +1 min
09:36 / 09:37≈ on time ≈ +2 min
09:48 / 09:50≈ on time ≈ +2 min
09:54on 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 NovBreda 08:09Partial coverage0 min—
Thu 12 NovAmersfoort Centraal 10:07+3 min+4 min
Wed 11 NovAmersfoort Centraal 10:040 min—
Tue 10 NovAmersfoort Centraal 10:190 min+16 min
Mon 9 NovAmersfoort Centraal 10:040 min—
Fri 6 NovAmersfoort Centraal 10:04No data—
Thu 5 NovAmersfoort Centraal 10:04No data—
Wed 4 NovAmersfoort Centraal 10:040 min—
Tue 3 NovAmersfoort Centraal 10:04No data—
Mon 2 NovAmersfoort Centraal 10:040 min—
Sun 1 NovAmersfoort Centraal 10:08+4 min+5 min
Sat 31 OctAmersfoort Centraal 10:05+1 min+1 min
Fri 30 OctAmersfoort Centraal 10:35Partial coverage0 min—
Thu 29 OctAmersfoort Centraal 10:07No data—
Wed 28 OctAmersfoort Centraal 10:04No data—
Tue 27 OctAmersfoort Centraal 10:040 min—
Mon 26 OctAmersfoort Centraal 10:090 min—
Sun 25 OctAmersfoort Centraal 10:04No data—
Sat 24 OctAmersfoort Centraal 10:040 min—
Fri 23 OctAmersfoort Centraal 10:07Partial coverage0 min—
Thu 22 OctAmersfoort Centraal 10:040 min—
Wed 21 OctAmersfoort Centraal 10:190 min—
Tue 20 OctAmersfoort Centraal 10:070 min—
Mon 19 OctAmersfoort Centraal 10:050 min—
Sun 18 OctHilversum 09:53+2 min+2 min
Sat 17 OctHilversum 09:56+2 min+2 min
Fri 16 OctHilversum 09:510 min—
Thu 15 OctDuivendrecht 10:58No data—
Wed 14 OctHilversum 10:080 min—
Tue 13 OctHilversum 09:52No data—