Train NS 2988 Roermond – Eindhoven Centraal

Roermond 23:30 → Eindhoven Centraal 00:01 Daily 0 h 31 min · 3 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 23:30 from Roermond · Sat 14 Nov

Next departure 23:30 today · Roermond
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 23 full · 0 partial · 2 no data
On-time · 90 days
94%
32/34 runs under 3 min
RT coverage: 34 full · 0 partial · 12 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 Eindhoven Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 9 Oct Max en route +6 min · last fix heading to — +6 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 32
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 67% F n=6
  • 100% S n=2
  • 100% S n=2

Stops and timetable

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

Last 90 days, 34 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:30on time on time
23:44≈ on time ≈ on time
00:01on 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
Fri 13 Nov— 00:140 min—
Thu 12 Nov— 00:040 min—
Wed 11 Nov— 00:030 min—
Tue 10 Nov— 00:04+2 min+2 min
Mon 9 Nov— 00:030 min—
Fri 6 Nov— 00:030 min—
Thu 5 Nov— 00:030 min—
Wed 4 Nov— 00:040 min—
Tue 3 Nov— 00:040 min—
Mon 2 Nov— 00:040 min+2 min
Sat 31 OctSittard 00:03No data—
Fri 30 Oct— 00:030 min—
Thu 29 Oct— 00:030 min+2 min
Wed 28 Oct— 00:010 min—
Tue 27 Oct— 00:040 min—
Mon 26 Oct— 00:030 min—
Sun 25 OctWeert 00:03No data—
Fri 23 Oct— 00:15+5 min+5 min
Thu 22 Oct— 00:030 min—
Wed 21 Oct— 00:080 min—
Tue 20 Oct— 23:140 min—
Mon 19 Oct— 00:030 min—
Sun 18 OctWeert 00:010 min—
Sat 17 OctWeert 00:160 min—
Fri 16 Oct— 00:030 min—
Thu 15 Oct— 00:050 min—
Wed 14 Oct— 00:030 min—
Tue 13 Oct— 00:140 min—
Mon 12 Oct— 00:040 min—
Sun 11 OctWeert 00:030 min—