Train NS 2378 Roosendaal – Amsterdam Centraal

Roosendaal 22:31 → Amsterdam Centraal 00:25 Daily 1 h 54 min · 13 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 22:31 from Roosendaal · Fri 6 Nov

Next departure 22:31 today · Roosendaal
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 2 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 19 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 Amsterdam Centraal, 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

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

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

Stops and timetable

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

Last 90 days, 28 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
22:31on time on time
22:53 / 22:54≈ on time ≈ on time
23:05≈ on time ≈ on time
23:08 / 23:11≈ on time ≈ on time
23:16≈ on time ≈ on time
23:24≈ on time ≈ on time
23:31 / 23:32≈ on time ≈ on time
23:35 / 23:36≈ on time ≈ on time
23:45 / 23:47≈ on time ≈ on time
00:01≈ on time ≈ on time
00:06 / 00:10≈ on time ≈ on time
00:19≈ on time ≈ on time
00:25on 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
Thu 5 Nov— 00:270 min—
Wed 4 Nov— 00:270 min—
Mon 2 Nov— 00:240 min—
Sun 1 NovDelft 23:42+1 min+1 min
Sat 31 OctRotterdam Blaak 00:280 min—
Fri 30 Oct— 00:260 min—
Wed 28 Oct— 23:510 min—
Tue 27 Oct— 00:270 min—
Mon 26 Oct— 00:260 min—
Sun 25 OctAmsterdam Sloterdijk 00:34No data—
Sat 24 OctRoosendaal 00:270 min—
Fri 23 Oct— 00:270 min—
Thu 22 Oct— 00:270 min—
Wed 21 Oct— 00:270 min—
Tue 20 Oct— 00:280 min—
Mon 19 Oct— 00:260 min—
Sun 18 OctAmsterdam Sloterdijk 00:34+1 min—
Sat 17 OctAmsterdam Sloterdijk 00:33No data—
Fri 16 Oct— 00:27+1 min—
Thu 15 Oct— 00:260 min—
Wed 14 Oct— 00:310 min—
Tue 13 Oct— 00:260 min—
Mon 12 Oct— 00:270 min—
Sun 11 OctAmsterdam Sloterdijk 00:350 min—
Sat 10 Oct— 23:100 min—
Fri 9 Oct— 00:260 min—
Thu 8 Oct— 00:260 min—
Wed 7 Oct— 00:260 min—
Tue 6 Oct— 00:270 min—
Mon 5 OctHaarlem 00:270 min—