Train NS 1818 Amersfoort Schothorst – Breda

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

✓ Today’s run finished

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

  1. Amersfoort Schothorst07:04
  2. Amersfoort Centraal07:08
  3. Hilversum07:21
  4. Amsterdam Zuid07:43
  5. Schiphol Airport07:50
  6. Rotterdam Centraal08:18
  7. Breda08:46

Next service: Monday 07:04 from Amersfoort Schothorst · Mon 9 Nov

Next departure 07:04 Monday · Amersfoort Schothorst
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 18 full · 9 partial · 3 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 18 full · 11 partial · 56 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

  • Sat 24 Oct Max en route +7 min · last fix heading to Schiphol Airport +7 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=3
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 75% 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, 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 10
07:04on time on time
07:08 / 07:10≈ on time ≈ on time
07:21 / 07:23≈ on time ≈ on time
07:38≈ on time ≈ +1 min
07:43 / 07:44≈ on time ≈ +1 min
07:50 / 07:52≈ on time ≈ +1 min
08:18 / 08:23≈ on time ≈ +1 min
08: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 6 NovRotterdam Centraal 09:09No data—
Thu 5 NovRotterdam Centraal 08:49Partial coverage0 min—
Wed 4 NovRotterdam Centraal 08:48Partial coverage0 min—
Tue 3 NovRotterdam Centraal 09:02Partial coverage0 min+8 min
Mon 2 NovRotterdam Centraal 08:37No data—
Sun 1 NovSchiphol Airport 08:22+1 min+1 min
Sat 31 OctSchiphol Airport 08:19+2 min+2 min
Fri 30 OctRotterdam Centraal 08:370 min—
Thu 29 OctRotterdam Centraal 08:47Partial coverage0 min—
Wed 28 OctRotterdam Centraal 08:48Partial coverage0 min—
Tue 27 OctRotterdam Centraal 08:48Partial coverage0 min—
Mon 26 OctRotterdam Centraal 08:47Partial coverage0 min—
Sun 25 OctSchiphol Airport 08:22No data—
Sat 24 OctSchiphol Airport 08:30+7 min+7 min
Fri 23 OctRotterdam Centraal 08:470 min—
Thu 22 OctRotterdam Centraal 08:500 min—
Wed 21 OctRotterdam Centraal 08:510 min—
Tue 20 OctRotterdam Centraal 08:56+3 min+3 min
Mon 19 OctRotterdam Centraal 09:11Partial coverage0 min—
Sun 18 OctSchiphol Airport 08:190 min—
Sat 17 OctSchiphol Airport 08:200 min—
Fri 16 OctRotterdam Centraal 08:500 min—
Thu 15 OctRotterdam Centraal 08:480 min—
Wed 14 OctRotterdam Centraal 08:370 min—
Tue 13 OctRotterdam Centraal 08:470 min—
Mon 12 OctAmersfoort Centraal 08:470 min—
Sun 11 OctSchiphol Airport 08:20+1 min+1 min
Sat 10 OctSchiphol Airport 08:190 min—
Fri 9 OctRotterdam Centraal 08:470 min—
Thu 8 OctRotterdam Centraal 08:48Partial coverage0 min—