Train NMBS 2577 Roosendaal – Puurs

Roosendaal 06:22 → Puurs 07:53 Mon, Tue, Wed, Thu, Fri 1 h 31 min · 21 stops NMBS

It has not run yet today

Last recorded run: Thursday 5 November No data

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

Full trip card
Next departure 06:22 today · Roosendaal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 6 full · 6 partial · 9 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 7 full · 6 partial · 50 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 13 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
Roosendaal
06:22on time on time
Essen
06:30 / 06:32≈ on time ≈ on time
Wildert
06:36≈ on time ≈ on time
Kalmthout
06:40 / 06:41≈ on time ≈ on time
Kijkuit
06:43≈ on time ≈ on time
Heide (B)
06:45 / 06:46≈ on time ≈ on time
Kapellen
06:51 / 06:52≈ on time ≈ on time
Sint-Mariaburg
06:55≈ on time ≈ on time
Ekeren
06:57 / 06:58≈ on time ≈ on time
Antwerpen-Noorderdokken
07:02≈ on time ≈ on time
Antwerpen-Luchtbal
07:05≈ on time ≈ on time
Antwerpen-Centraal
07:10 / 07:13≈ on time ≈ on time
Antwerpen-Berchem
07:17 / 07:18≈ on time ≈ on time
Antwerpen-Zuid
07:22 / 07:23≈ on time ≈ on time
Hoboken-Polder
07:28≈ on time ≈ on time
Hemiksem
07:33≈ on time ≈ on time
Schelle
07:36≈ on time ≈ on time
Niel
07:39≈ on time ≈ on time
Boom
07:43 / 07:45≈ on time ≈ on time
Ruisbroek-Sauvegarde
07:49≈ on time ≈ on time
Puurs
07: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 06:34No data—
Wed 4 NovRoosendaal 06:37Partial coverage0 min—
Tue 3 NovRoosendaal 06:34Partial coverage0 min—
Mon 2 NovRoosendaal 06:37No data—
Fri 30 OctRoosendaal 06:36Partial coverage0 min—
Thu 29 OctRoosendaal 06:36Partial coverage0 min—
Wed 28 OctRoosendaal 06:36Partial coverage0 min—
Tue 27 OctRoosendaal 06:36Partial coverage0 min—
Mon 26 OctRoosendaal 06:36No data—
Fri 23 OctRoosendaal 06:36No data—
Thu 22 OctRoosendaal 06:370 min—
Wed 21 OctRoosendaal 06:36No data—
Tue 20 OctRoosendaal 06:360 min—
Mon 19 OctRoosendaal 06:360 min—
Fri 16 OctRoosendaal 06:36No data—
Thu 15 OctRoosendaal 06:370 min—
Wed 14 OctRoosendaal 06:360 min—
Tue 13 OctRoosendaal 06:370 min—
Mon 12 OctRoosendaal 06:36No data—
Fri 9 OctRoosendaal 06:36No data—
Thu 8 OctRoosendaal 06:37No data—
Wed 7 OctRoosendaal 06:36No data—
Tue 6 OctRoosendaal 06:370 min—
Mon 5 OctRoosendaal 06:37No data—
Fri 2 OctRoosendaal 06:36No data—
Thu 1 OctRoosendaal 06:42No data—
Wed 30 SeptRoosendaal 06:36No data—
Tue 29 SeptRoosendaal 06:37No data—
Mon 28 SeptRoosendaal 06:36No data—
Fri 25 SeptRoosendaal 06:36No data—