Train NS 4095 Amsterdam Centraal – Breukelen

Amsterdam Centraal 00:49 → Breukelen 01:18 Daily 0 h 29 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:19 0 min

  1. Amsterdam Centraal00:49
  2. Amsterdam Muiderpoort00:54
  3. Amsterdam Amstel00:58
  4. Amsterdam Bijlmer ArenA01:04
  5. Amsterdam Holendrecht01:06
  6. Abcoude01:10
  7. Breukelen01:18

Next service: tomorrow 00:49 from Amsterdam Centraal · Sun 15 Nov

Next departure 00:49 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 26 full · 2 partial · 1 no data
On-time · 90 days
100%
38/38 runs under 3 min
RT coverage: 36 full · 2 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Breukelen, 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 100% F n=5
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 38 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
00:49on time on time
00:54≈ on time ≈ on time
00:58≈ on time ≈ on time
01:01≈ on time ≈ on time
01:04≈ on time ≈ on time
01:06≈ on time ≈ on time
01:10≈ on time ≈ on time
01:18on time on time

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
Sat 14 Nov— 01:190 min+2 min
Fri 13 Nov— 01:240 min—
Thu 12 Nov— 01:240 min—
Wed 11 Nov— 01:420 min—
Tue 10 Nov— 01:420 min—
Mon 9 NovAbcoude 01:24Partial coverage0 min—
Sun 8 Nov— 01:420 min—
Sat 7 Nov— 01:190 min—
Fri 6 Nov— 01:42No data—
Thu 5 Nov— 01:430 min—
Wed 4 Nov— 01:430 min—
Tue 3 Nov— 01:42+3 min+3 min
Sun 1 Nov— 01:250 min—
Sat 31 Oct— 02:230 min—
Fri 30 Oct— 01:420 min—
Thu 29 Oct— 01:420 min—
Wed 28 Oct— 01:420 min—
Tue 27 Oct— 01:420 min—
Mon 26 OctAbcoude 01:41Partial coverage0 min—
Sun 25 Oct— 01:420 min—
Sat 24 Oct— 01:430 min—
Fri 23 Oct— 01:420 min—
Thu 22 Oct— 01:420 min—
Wed 21 Oct— 01:420 min—
Tue 20 Oct— 00:470 min—
Mon 19 OctAbcoude 01:420 min—
Sun 18 OctAbcoude 01:240 min—
Sat 17 Oct— 01:420 min—
Fri 16 Oct— 01:420 min—
Thu 15 Oct— 01:420 min—