Train NMBS 2591 Roosendaal – Puurs

Roosendaal 20:22 → Puurs 21:53 Daily 1 h 31 min · 21 stops NMBS

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 20:22 from Roosendaal · Sun 8 Nov

Next departure 20:22 today · Roosendaal
On-time · 30 days
100%
5/5 runs under 3 min
RT coverage: 4 full · 1 partial · 4 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 4 full · 1 partial · 23 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 Puurs, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 5 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
20:22on time on time
20:30 / 20:32— —
20:36— —
20:40 / 20:41— —
20:43— —
20:45 / 20:46— —
20:51 / 20:52— —
20:55— —
20:57 / 20:58— —
21:02— —
21:05— —
21:10 / 21:13— —
21:17 / 21:18— —
21:22 / 21:23— —
21:28— —
21:33— —
21:36— —
21:39— —
21:43 / 21:45— —
21:49— —
21:53— —

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 7 NovRoosendaal 20:34Partial coverage0 min—
Sun 1 NovRoosendaal 20:34No data—
Sat 31 OctRoosendaal 20:36No data—
Sun 25 OctRoosendaal 20:37No data—
Sat 24 OctRoosendaal 20:370 min—
Sun 18 OctRoosendaal 20:360 min—
Sat 17 OctRoosendaal 20:36No data—
Sun 11 OctRoosendaal 20:360 min—
Sat 10 OctRoosendaal 20:360 min—
Sun 4 OctRoosendaal 20:44No data—
Sat 3 OctRoosendaal 20:37No data—
Sun 27 SeptRoosendaal 20:36No data—
Sat 26 SeptRoosendaal 20:36No data—
Sun 20 SeptRoosendaal 20:36No data—
Sat 19 SeptRoosendaal 20:36No data—
Sun 13 SeptRoosendaal 20:29No data—
Sat 12 SeptRoosendaal 20:28No data—
Sun 6 SeptRoosendaal 20:36No data—
Sat 5 SeptRoosendaal 20:36No data—
Sun 30 AugRoosendaal 20:28No data—
Sat 29 AugRoosendaal 20:28No data—
Sun 23 AugRoosendaal 20:36No data—
Sat 22 AugRoosendaal 20:36No data—
Fri 21 AugRoosendaal 20:36No data—
Sun 16 AugRoosendaal 20:36No data—
Sat 15 AugRoosendaal 20:37No data—
Fri 14 AugRoosendaal 20:36No data—
Wed 12 AugRoosendaal 20:36No data—