Train NS 1836 Amersfoort Schothorst – Breda

Amersfoort Schothorst 11:34 → Breda 13: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: tomorrow 11:34 from Amersfoort Schothorst · Mon 9 Nov

Next departure 11:34 tomorrow · Amersfoort Schothorst
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 15 full · 5 partial · 8 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 16 full · 9 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

  • Tue 6 Oct Max en route +14 min · last fix heading to Rotterdam Centraal +14 min
  • Sun 18 Oct Max en route +9 min · last fix heading to Rotterdam Centraal +9 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 67% T n=3
  • 100% W n=3
  • 100% T n=5
  • 100% F n=3
  • 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, 25 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
11:34on time on time
11:38 / 11:41≈ on time ≈ on time
11:52 / 11:53≈ on time ≈ on time
12:08≈ on time ≈ on time
12:13 / 12:14≈ on time ≈ on time
12:20 / 12:22≈ on time ≈ on time
12:48 / 12:53≈ on time ≈ on time
13: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 13:17No data—
Thu 5 NovRotterdam Centraal 13:19Partial coverage0 min—
Wed 4 NovRotterdam Centraal 13:18Partial coverage0 min—
Tue 3 NovRotterdam Centraal 13:18No data—
Mon 2 NovRotterdam Centraal 13:18No data—
Sun 1 NovRotterdam Centraal 13:180 min—
Sat 31 OctRotterdam Centraal 13:180 min—
Fri 30 OctRotterdam Centraal 13:070 min—
Thu 29 OctRotterdam Centraal 13:170 min—
Wed 28 OctRotterdam Centraal 13:18Partial coverage0 min—
Tue 27 OctRotterdam Centraal 13:18Partial coverage0 min—
Mon 26 OctRotterdam Centraal 13:170 min—
Sun 25 OctRotterdam Centraal 13:07No data—
Sat 24 OctRotterdam Centraal 13:170 min—
Fri 23 OctRotterdam Centraal 13:17No data—
Thu 22 OctRotterdam Centraal 13:170 min—
Wed 21 OctRotterdam Centraal 13:08No data—
Tue 20 OctRotterdam Centraal 13:170 min—
Mon 19 OctRotterdam Centraal 13:18Partial coverage0 min—
Sun 18 OctRotterdam Centraal 13:11+9 min+9 min
Sat 17 OctRotterdam Centraal 13:170 min—
Fri 16 OctRotterdam Centraal 13:170 min—
Thu 15 OctRotterdam Centraal 13:200 min—
Wed 14 OctRotterdam Centraal 13:17No data—
Tue 13 OctRotterdam Centraal 13:07No data—
Mon 12 OctRotterdam Centraal 13:180 min—
Sun 11 OctRotterdam Centraal 13:170 min—
Sat 10 OctRotterdam Centraal 13:170 min+1 min
Fri 9 OctRotterdam Centraal 13:180 min—
Thu 8 OctRotterdam Centraal 13:17Partial coverage0 min—