Train NS 3682 Vlissingen – 's-Hertogenbosch

Vlissingen 22:20 → 's-Hertogenbosch 00:19 Daily 1 h 59 min · 15 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: Monday 22:20 from Vlissingen · Mon 9 Nov

Full trip card
Next departure 22:20 Monday · Vlissingen
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 5 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 23 full · 1 partial · 20 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 's-Hertogenbosch, in minutes. One bar per run.

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

Worst days

  • Thu 8 Oct Max en route +17 min · last fix heading to — +16 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=4
  • 50% T n=2
  • 100% F n=4
  • 100% S n=1
  • 100% S n=4

Stops and timetable

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

Last 90 days, 24 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
22:20on time on time
Vlissingen Souburg
22:24≈ on time ≈ on time
Middelburg
22:29≈ on time ≈ on time
Arnemuiden
22:33≈ on time ≈ on time
Goes
22:43 / 22:44≈ on time ≈ on time
Kapelle-Biezelinge
22:49≈ on time ≈ on time
Kruiningen-Yerseke
22:54≈ on time ≈ on time
Krabbendijke
23:00≈ on time ≈ on time
Rilland-Bath
23:04≈ on time ≈ on time
Bergen op Zoom
23:14≈ on time ≈ on time
Roosendaal
23:24 / 23:27≈ on time ≈ on time
Etten-Leur
23:37≈ on time ≈ on time
Breda
23:45 / 23:49≈ on time ≈ on time
Tilburg
00:02 / 00:04≈ on time ≈ on time
's-Hertogenbosch
00:19on 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
Fri 6 Nov— 00:190 min—
Thu 5 Nov— 01:04No data—
Wed 4 Nov— 00:190 min—
Tue 3 Nov— 00:190 min—
Mon 2 Nov— 00:190 min—
Sun 1 NovTilburg 00:180 min—
Sat 31 OctBergen op Zoom 23:44No data—
Fri 30 Oct— 00:470 min—
Wed 28 Oct— 00:210 min—
Mon 26 Oct— 00:160 min—
Sun 25 OctTilburg 01:090 min—
Fri 23 Oct— 00:340 min+3 min
Thu 22 Oct— 00:330 min—
Wed 21 Oct— 00:21No data—
Tue 20 Oct— 02:380 min—
Mon 19 Oct— 22:280 min—
Sun 18 OctTilburg 00:220 min+1 min
Sat 17 OctTilburg 00:23No data—
Fri 16 Oct— 00:200 min—
Thu 15 Oct— 23:26No data—
Wed 14 Oct— 00:330 min—
Tue 13 Oct— 00:200 min—
Mon 12 Oct— 00:310 min+1 min
Sun 11 OctTilburg 00:270 min+3 min
Sat 10 Oct— 00:210 min—
Thu 8 Oct— 00:53+16 min+17 min
Wed 7 Oct— 00:200 min—
Tue 6 Oct— 00:200 min—
Mon 5 OctTilburg 00:20Partial coverage0 min—
Sun 4 OctTilburg 00:18No data—