Train NS 3686 Goes → Roosendaal

Goes 23:43 → Roosendaal 00:24 Daily 0 h 41 min · 7 stops NS (Nederlandse Spoorwegen)

NS 3686 Goes–Roosendaal: final delay under 3 min on 17 of its 22 runs with data in the last 30 days (77%). Median final delay: +1 min. Running now, on time. Expected at Roosendaal: 00:24. TrainsRadar data as of 23 Nov 2026, 00:10 (GMT+1).

Running now · updated 00:10

Heading to Roosendaal 0 min

Estimated arrival at Roosendaal 00:24 · 147 km/h

  1. Goes23:43
  2. Kapelle-Biezelinge23:48
  3. Kruiningen-Yerseke23:54
  4. Krabbendijke00:00
  5. Rilland-Bath00:05
  6. Bergen op Zoom00:15
  7. Roosendaal00:24

Today it is running no worse than usual: typical arrival delay is +1 min; 77% of the last 22 runs arrived on time.

On-time · 30 days
77%
17/22 runs under 3 min
RT coverage: 22 full · 0 partial · 2 no data
On-time · 90 days
85%
33/39 runs under 3 min
RT coverage: 39 full · 0 partial · 12 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +7 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 9 Nov Max en route +11 min · last fix heading to — +11 min
  • Tue 10 Nov Max en route +8 min · last fix heading to — +8 min
  • Thu 12 Nov Max en route +9 min · last fix heading to — +7 min
  • 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 33
  • 3–10 min 13% · 5
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 71% M n=7
  • 83% T n=6
  • 60% W n=5
  • 80% T n=5
  • 100% F n=4
  • 100% S n=6
  • 100% S n=6

Stops and timetable

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

Last 90 days, 39 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 10Today
23:43on time on time
23:48≈ on time ≈ +1 min
23:54≈ on time ≈ +2 min
00:00≈ on time ≈ +2 min
00:05≈ on time ≈ +3 min
00:15≈ on time ≈ +4 min
00:24on time +6 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
Sun 22 NovRilland-Bath 00:090 min—
Sat 21 Nov— 00:270 min—
Thu 19 Nov— 00:290 min+2 min
Wed 18 Nov— 00:24+1 min+1 min
Tue 17 Nov— 00:23+1 min+1 min
Mon 16 Nov— 00:28+3 min+3 min
Sun 15 NovBergen op Zoom 00:290 min—
Sat 14 Nov— 00:440 min+3 min
Thu 12 Nov— 00:42+7 min+9 min
Wed 11 Nov— 00:240 min—
Tue 10 Nov— 00:34+8 min+8 min
Mon 9 Nov— 00:48+11 min+11 min
Fri 6 Nov— 00:28+2 min+2 min
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:29+3 min+3 min
Sat 31 OctVlissingen 00:340 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:290 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