Train NS 1839 Breda – Amersfoort Schothorst

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

✓ Today’s run finished

Today, last fix heading to Amersfoort Centraal at 12:04 0 min

  1. Breda10:14
  2. Rotterdam Centraal10:37
  3. Schiphol Airport11:07
  4. Duivendrecht11:21
  5. Hilversum11:36
  6. Amersfoort Centraal11:48
  7. Amersfoort Schothorst11:54

Next service: tomorrow 10:14 from Breda · Fri 13 Nov

Next departure 10:14 tomorrow · Breda
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 8 full · 10 partial · 10 no data
On-time · 90 days
96%
24/25 runs under 3 min
RT coverage: 12 full · 13 partial · 60 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 +5 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 96% · 24
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 100% W n=5
  • 100% T n=4
  • 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
10:14on time on time
10:37 / 10:41≈ on time ≈ on time
11:07 / 11:08≈ on time ≈ +1 min
11:14 / 11:16≈ on time ≈ +1 min
11:21≈ on time ≈ +1 min
11:36 / 11:37≈ on time ≈ +1 min
11:48 / 11:50≈ on time ≈ +2 min
11: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
Thu 12 NovAmersfoort Centraal 12:04Partial coverage0 min+2 min
Wed 11 NovAmersfoort Centraal 12:04Partial coverage0 min—
Tue 10 NovAmersfoort Centraal 12:19Partial coverage0 min+12 min
Mon 9 NovAmersfoort Centraal 12:04Partial coverage+1 min+2 min
Fri 6 NovAmersfoort Centraal 12:04No data—
Thu 5 NovAmersfoort Centraal 12:04Partial coverage0 min—
Wed 4 NovAmersfoort Centraal 12:04Partial coverage+2 min+2 min
Tue 3 NovAmersfoort Centraal 12:04No data—
Mon 2 NovAmersfoort Centraal 12:04No data—
Sun 1 NovAmersfoort Centraal 12:10+5 min+5 min
Sat 31 OctAmersfoort Centraal 12:06+2 min+2 min
Fri 30 OctAmersfoort Centraal 12:040 min—
Thu 29 OctAmersfoort Centraal 12:060 min—
Wed 28 OctAmersfoort Centraal 12:13Partial coverage0 min—
Tue 27 OctAmersfoort Centraal 12:05Partial coverage0 min—
Mon 26 OctAmersfoort Centraal 12:17No data—
Sun 25 OctAmersfoort Centraal 12:16No data—
Sat 24 OctAmersfoort Centraal 12:05+1 min+4 min
Fri 23 OctAmersfoort Centraal 12:16No data—
Thu 22 OctAmersfoort Centraal 12:05No data—
Wed 21 OctAmersfoort Centraal 12:05Partial coverage0 min—
Tue 20 OctAmersfoort Centraal 12:08No data—
Mon 19 OctAmersfoort Centraal 12:27Partial coverage0 min—
Sun 18 OctHilversum 11:52+1 min+1 min
Sat 17 OctHilversum 11:530 min—
Fri 16 OctHilversum 11:550 min—
Thu 15 OctRotterdam Centraal 17:26No data—
Wed 14 OctHilversum 12:03No data—
Tue 13 OctHilversum 11:550 min—
Mon 12 OctHilversum 11:52No data—