Train NS 3686 Vlissingen – Roosendaal

Vlissingen 23:20 → Roosendaal 00:24 Daily 1 h 04 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 23:20 from Vlissingen · Fri 6 Nov

Full trip card
Next departure 23:20 today · Vlissingen
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 18 full · 5 partial · 5 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 21 full · 5 partial · 17 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Roosendaal, in minutes. One bar per run.

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

Worst days

  • Mon 2 Nov Max en route +6 min · last fix heading to — +6 min
  • Wed 4 Nov Max en route +6 min · last fix heading to — +6 min
  • Wed 7 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 23
  • 3–10 min 12% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=4
  • 33% W n=3
  • 100% T n=3
  • 100% F n=3
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 26 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
Vlissingen
23:20on time on time
Vlissingen Souburg
23:24≈ on time ≈ on time
Middelburg
23:29≈ on time ≈ +1 min
Arnemuiden
23:33≈ on time ≈ +1 min
Goes
23:43 / 23:44≈ on time ≈ +1 min
Kapelle-Biezelinge
23:49≈ on time ≈ +1 min
Kruiningen-Yerseke
23:54≈ on time ≈ +2 min
Krabbendijke
00:00≈ on time ≈ +2 min
Rilland-Bath
00:04≈ on time ≈ +2 min
Bergen op Zoom
00:14≈ on time ≈ +3 min
Roosendaal
00:24on time +3 min

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— 01:08No data—
Wed 4 Nov— 00:34+6 min+6 min
Tue 3 Nov— 00:280 min—
Mon 2 Nov— 00:28+6 min+6 min
Sun 1 NovBergen op Zoom 00:29Partial coverage+3 min+3 min
Sat 31 OctVlissingen 00:34Partial coverage0 min—
Thu 29 Oct— 00:28+2 min+2 min
Wed 28 Oct— 00:26No data—
Tue 27 Oct— 00:300 min—
Mon 26 Oct— 00:400 min—
Sun 25 OctBergen op Zoom 00:29Partial coverage0 min—
Sat 24 Oct— 00:280 min—
Fri 23 Oct— 00:280 min—
Thu 22 Oct— 00:34No data—
Wed 21 Oct— 00:26No data—
Tue 20 Oct— 00:53No data—
Mon 19 Oct— 00:280 min+1 min
Sun 18 OctBergen op Zoom 00:30Partial coverage+2 min+2 min
Sat 17 OctBergen op Zoom 00:28Partial coverage0 min—
Fri 16 Oct— 00:28+2 min+2 min
Thu 15 Oct— 00:260 min—
Wed 14 Oct— 00:260 min—
Tue 13 Oct— 00:250 min—
Mon 12 Oct— 00:260 min—
Sun 11 OctBergen op Zoom 00:290 min—
Sat 10 Oct— 00:28+3 min+3 min
Fri 9 Oct— 00:290 min+2 min
Thu 8 Oct— 00:26+1 min+1 min
Wed 7 Oct— 00:31+3 min+3 min
Tue 6 Oct— 00:29+3 min+3 min