Train NS 1867 Breda – Amersfoort Schothorst

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

✓ Today’s run finished

Today, last fix heading to Hilversum at 18:44 +3 min

  1. Breda17:14
  2. Rotterdam Centraal17:37
  3. Schiphol Airport18:07
  4. Duivendrecht18:20
  5. Hilversum18:36
  6. Amersfoort Centraal18:48
  7. Amersfoort Schothorst18:54

Next service: Monday 17:14 from Breda · Mon 9 Nov

Next departure 17:14 Monday · Breda
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 10 full · 8 partial · 12 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 13 full · 8 partial · 66 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: +3 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

  • Sat 24 Oct Max en route +7 min · last fix heading to Amersfoort Centraal +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 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, 21 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
17:14on time +1 min
17:37 / 17:41≈ on time ≈ +1 min
18:07 / 18:08≈ on time ≈ +1 min
18:15 / 18:16≈ on time ≈ +1 min
18:20≈ on time ≈ +1 min
18:36 / 18:37≈ on time ≈ +2 min
18:48 / 18:50≈ on time ≈ +2 min
18: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 6 NovHilversum 18:44Partial coverage+3 min+3 min
Thu 5 NovSchiphol Airport 19:12No data—
Wed 4 NovSchiphol Airport 19:120 min—
Tue 3 NovSchiphol Airport 18:59No data—
Mon 2 NovSchiphol Airport 18:22No data—
Sun 1 NovAmersfoort Centraal 19:04Partial coverage0 min—
Sat 31 OctAmersfoort Centraal 19:05Partial coverage+1 min—
Fri 30 OctAmersfoort Centraal 19:04No data—
Thu 29 OctBreda 19:02No data—
Wed 28 OctSchiphol Airport 19:08+1 min—
Tue 27 OctRotterdam Centraal 18:56No data—
Mon 26 OctSchiphol Airport 19:06+2 min+3 min
Sun 25 OctAmersfoort Centraal 19:17No data—
Sat 24 OctAmersfoort Centraal 19:17Partial coverage+7 min+7 min
Fri 23 OctAmersfoort Centraal 19:04Partial coverage+1 min+1 min
Thu 22 OctHilversum 19:060 min—
Wed 21 OctHilversum 18:56No data—
Tue 20 OctHilversum 18:500 min—
Mon 19 OctHilversum 19:02No data—
Sun 18 OctHilversum 18:530 min—
Sat 17 OctHilversum 18:560 min—
Fri 16 OctHilversum 18:520 min—
Thu 15 OctDuivendrecht 18:53No data—
Wed 14 OctHilversum 18:51No data—
Tue 13 OctHilversum 18:59No data—
Mon 12 OctHilversum 18:510 min—
Sun 11 OctAmersfoort Centraal 19:05Partial coverage+1 min—
Sat 10 OctAmersfoort Centraal 19:05Partial coverage+2 min+2 min
Fri 9 OctDuivendrecht 18:55Partial coverage0 min—
Thu 8 OctRotterdam Centraal 18:550 min—