Train NS 2381 Amsterdam Centraal – Roosendaal

Amsterdam Centraal 23:05 → Roosendaal 00:59 Daily 1 h 54 min · 12 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 15 November +1 min

Next service: today 23:05 from Amsterdam Centraal · Mon 16 Nov

Next departure 23:05 today · Amsterdam Centraal
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 21 full · 2 partial · 3 no data
On-time · 90 days
100%
36/36 runs under 3 min
RT coverage: 34 full · 2 partial · 14 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 Roosendaal, 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

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

  • Early 0% · 0
  • On time 100% · 36
  • 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=6
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=6
  • 100% S n=4

Stops and timetable

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

Last 90 days, 36 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
23:05on time on time
23:10 / 23:12≈ on time ≈ on time
23:20 / 23:23≈ on time ≈ on time
23:40 / 23:45≈ on time ≈ on time
23:54 / 23:55≈ on time ≈ on time
23:58 / 00:00≈ on time ≈ on time
00:06≈ on time ≈ on time
00:14≈ on time ≈ on time
00:19 / 00:21≈ on time ≈ on time
00:24≈ on time ≈ on time
00:36 / 00:37≈ on time ≈ on time
00:59on 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
Sun 15 NovDordrecht 01:03Partial coverage+1 min—
Sat 14 NovAmsterdam Sloterdijk 00:39Partial coverage0 min—
Fri 13 Nov— 00:250 min—
Thu 12 Nov— 00:590 min—
Wed 11 Nov— 00:590 min—
Tue 10 Nov— 01:070 min—
Mon 9 Nov— 00:590 min—
Sun 8 NovDelft 00:220 min+3 min
Sat 7 NovAmsterdam Sloterdijk 00:130 min+1 min
Fri 6 Nov— 00:370 min—
Thu 5 Nov— 00:590 min—
Wed 4 Nov— 01:090 min—
Tue 3 Nov— 00:590 min—
Sat 31 OctAmsterdam Sloterdijk 01:020 min—
Thu 29 Oct— 01:060 min+3 min
Wed 28 Oct— 23:480 min—
Tue 27 Oct— 01:010 min—
Mon 26 Oct— 01:070 min—
Sun 25 OctDordrecht 01:08No data—
Sat 24 Oct— 00:400 min—
Fri 23 Oct— 00:400 min—
Thu 22 Oct— 01:01No data—
Wed 21 Oct— 01:12No data—
Tue 20 Oct— 01:010 min—
Mon 19 Oct— 23:59+1 min+1 min
Sun 18 OctDordrecht 00:550 min+8 min
Sat 17 OctRotterdam Blaak 00:380 min—
Fri 16 Oct— 00:390 min—
Thu 15 Oct— 01:010 min—
Wed 14 Oct— 01:010 min—