Train NS 1877 Breda – Amersfoort Schothorst

Breda 19:44 → Amersfoort Schothorst 21:24 Daily 1 h 40 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 19:44 from Breda · Thu 5 Nov

Next departure 19:44 today · Breda
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 32 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: +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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=2
  • 100% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 22 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
19:44on time on time
20:07 / 20:11≈ on time ≈ on time
20:37 / 20:38≈ on time ≈ +1 min
20:44 / 20:46≈ on time ≈ +1 min
20:50≈ on time ≈ +1 min
21:06 / 21:07≈ on time ≈ +1 min
21:18 / 21:20≈ on time ≈ +1 min
21:24on 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
Wed 4 Nov— 21:24+1 min+2 min
Tue 3 Nov— 20:12No data—
Mon 2 Nov— 21:240 min—
Sun 1 NovAmersfoort Centraal 21:340 min—
Sat 31 OctAmersfoort Centraal 21:460 min—
Fri 30 Oct— 20:19No data—
Thu 29 Oct— 21:26+1 min+2 min
Wed 28 Oct— 21:26No data—
Tue 27 Oct— 21:390 min—
Mon 26 OctBreda 21:250 min—
Sun 25 OctAmersfoort Centraal 21:36No data—
Sat 24 OctAmersfoort Centraal 21:360 min—
Fri 23 Oct— 21:390 min+11 min
Thu 22 Oct— 21:320 min—
Wed 21 Oct— 21:26No data—
Tue 20 Oct— 21:29No data—
Mon 19 Oct— 21:370 min—
Sun 18 OctHilversum 21:23+2 min+2 min
Sat 17 OctRotterdam Centraal 21:24No data—
Fri 16 OctBreda 21:27+3 min+4 min
Thu 15 Oct— 21:20No data—
Wed 14 OctBreda 22:030 min—
Tue 13 Oct— 21:21No data—
Mon 12 Oct— 20:080 min—
Sun 11 OctAmersfoort Centraal 21:340 min—
Sat 10 OctAmersfoort Centraal 21:34+1 min+1 min
Fri 9 Oct— 21:29+2 min+3 min
Thu 8 Oct— 21:27+1 min+2 min
Wed 7 Oct— 02:280 min+49 min
Tue 6 Oct— 21:260 min+2 min