Train NMBS 2587 Roosendaal – Puurs

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

✓ Today’s run finished

Today, last fix heading to Roosendaal at 16:37 No data

  1. Roosendaal16:22
  2. Essen16:29
  3. Kalmthout16:40
  4. Sint-Mariaburg16:55
  5. Antwerpen-Luchtbal17:05
  6. Antwerpen-Zuid17:22
  7. Puurs17:53

Next service: tomorrow 16:22 from Roosendaal · Fri 6 Nov

Next departure 16:22 tomorrow · Roosendaal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 5 full · 7 partial · 18 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 5 full · 9 partial · 75 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 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=3
  • 100% W n=2
  • 100% T n=1
  • 100% F n=1
  • 100% S n=2
  • 100% S n=1

Stops and timetable

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

Last 90 days, 14 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
16:22on time on time
16:29 / 16:32≈ on time ≈ on time
16:36≈ on time ≈ on time
16:40 / 16:41≈ on time ≈ on time
16:43≈ on time ≈ on time
16:45 / 16:46≈ on time ≈ on time
16:51 / 16:52≈ on time ≈ on time
16:55≈ on time ≈ on time
16:57 / 16:58≈ on time ≈ on time
17:02≈ on time ≈ on time
17:05≈ on time ≈ on time
17:10 / 17:13≈ on time ≈ on time
17:17 / 17:18≈ on time ≈ on time
17:22 / 17:23≈ on time ≈ on time
17:28≈ on time ≈ on time
17:33≈ on time ≈ on time
17:36≈ on time ≈ on time
17:39≈ on time ≈ on time
17:43 / 17:45≈ on time ≈ on time
17:49≈ on time ≈ on time
17:53on 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 NovRoosendaal 16:37No data—
Wed 4 NovRoosendaal 16:34No data—
Tue 3 NovRoosendaal 16:34Partial coverage0 min—
Mon 2 NovRoosendaal 16:34Partial coverage0 min—
Sun 1 NovRoosendaal 16:36No data—
Sat 31 OctRoosendaal 16:36No data—
Fri 30 OctRoosendaal 16:36No data—
Thu 29 OctRoosendaal 16:37No data—
Wed 28 OctRoosendaal 16:36Partial coverage0 min—
Tue 27 OctRoosendaal 16:36No data—
Mon 26 OctRoosendaal 16:36No data—
Sun 25 OctRoosendaal 16:36No data—
Sat 24 OctRoosendaal 16:360 min—
Fri 23 OctRoosendaal 16:36No data—
Thu 22 OctRoosendaal 16:36No data—
Wed 21 OctRoosendaal 16:37No data—
Tue 20 OctRoosendaal 16:360 min—
Mon 19 OctRoosendaal 16:370 min—
Sun 18 OctRoosendaal 16:360 min—
Sat 17 OctRoosendaal 16:36No data—
Fri 16 OctRoosendaal 16:36No data—
Thu 15 OctRoosendaal 16:36No data—
Wed 14 OctRoosendaal 16:36No data—
Tue 13 OctRoosendaal 16:36No data—
Mon 12 OctRoosendaal 16:36Partial coverage0 min—
Sun 11 OctRoosendaal 16:36No data—
Sat 10 OctRoosendaal 16:360 min—
Fri 9 OctRoosendaal 16:36Partial coverage0 min—
Thu 8 OctRoosendaal 16:36Partial coverage0 min—
Wed 7 OctRoosendaal 16:36Partial coverage0 min—