Train NS 1834 Amersfoort Schothorst – Breda

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

✓ Today’s run finished

Today, last fix heading to Rotterdam Centraal at 12:48 No data

  1. Amersfoort Schothorst11:04
  2. Amersfoort Centraal11:08
  3. Hilversum11:21
  4. Amsterdam Zuid11:43
  5. Schiphol Airport11:50
  6. Rotterdam Centraal12:18
  7. Breda12:46

Next service: tomorrow 11:04 from Amersfoort Schothorst · Thu 22 Oct

Next departure 11:04 tomorrow · Amersfoort Schothorst
On-time · 30 days
58%
7/12 runs under 3 min
RT coverage: 7 full · 5 partial · 18 no data
On-time · 90 days
58%
7/12 runs under 3 min
RT coverage: 7 full · 5 partial · 75 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +10 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 +20 min · last fix heading to Rotterdam Centraal +20 min
  • Mon 5 Oct Max en route +10 min · last fix heading to Rotterdam Centraal +10 min
  • Thu 8 Oct Max en route +8 min · last fix heading to Rotterdam Centraal +8 min
  • Sun 11 Oct Max en route +19 min · last fix heading to Rotterdam Centraal +4 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Rotterdam Centraal +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 58% · 7
  • 3–10 min 25% · 3
  • 10–30 min 17% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=1
  • 100% W n=1
  • 0% T n=1
  • 50% F n=2
  • 100% S n=2
  • 0% S n=2

Stops and timetable

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

StopSched.
11:04
11:08 / 11:10
11:21 / 11:23
11:38
11:43 / 11:44
11:50 / 11:52
12:18 / 12:23
12:46

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.

Recent runs

DateLast stopFinalMax
Wed 21 OctRotterdam Centraal 12:48No data—
Tue 20 OctRotterdam Centraal 12:47No data—
Mon 19 OctRotterdam Centraal 12:47Partial coverage0 min—
Sun 18 OctRotterdam Centraal 13:27+20 min+20 min
Sat 17 OctAmersfoort Centraal 12:380 min—
Fri 16 OctRotterdam Centraal 12:470 min—
Thu 15 OctRotterdam Centraal 13:00No data—
Wed 14 OctRotterdam Centraal 12:54No data—
Tue 13 OctRotterdam Centraal 12:37No data—
Mon 12 OctRotterdam Centraal 12:480 min—
Sun 11 OctRotterdam Centraal 13:24+4 min+19 min
Sat 10 OctRotterdam Centraal 12:470 min—
Fri 9 OctRotterdam Centraal 12:54+3 min+4 min
Thu 8 OctRotterdam Centraal 13:04Partial coverage+8 min+8 min
Wed 7 OctRotterdam Centraal 12:51Partial coverage+2 min+3 min
Tue 6 OctRotterdam Centraal 12:46Partial coverage0 min—
Mon 5 OctRotterdam Centraal 13:07Partial coverage+10 min+10 min
Sun 4 OctSchiphol Airport 12:06No data—
Sat 3 OctSchiphol Airport 12:07No data—
Fri 2 OctRotterdam Centraal 12:38No data—
Thu 1 OctRotterdam Centraal 12:39No data—
Wed 30 SeptRotterdam Centraal 12:39No data—
Tue 29 SeptRotterdam Centraal 12:37No data—
Mon 28 SeptRotterdam Centraal 12:38No data—
Sun 27 SeptRotterdam Centraal 12:38No data—
Sat 26 SeptRotterdam Centraal 12:37No data—
Fri 25 SeptRotterdam Centraal 12:37No data—
Thu 24 SeptRotterdam Centraal 12:37No data—
Wed 23 SeptRotterdam Centraal 12:37No data—
Tue 22 SeptRotterdam Centraal 12:37No data—