Train NS 3919 's-Hertogenbosch – Vlissingen

's-Hertogenbosch 07:13 → Vlissingen 09:09 Daily 1 h 56 min · 15 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Vlissingen Souburg at 09:24 +4 min

  1. 's-Hertogenbosch07:13
  2. Breda07:41
  3. Bergen op Zoom08:16
  4. Krabbendijke08:30
  5. Kapelle-Biezelinge08:42
  6. Vlissingen Souburg09:06
  7. Vlissingen09:09

Next service: tomorrow 07:13 from 's-Hertogenbosch · Sun 8 Nov

Next departure 07:13 tomorrow · 's-Hertogenbosch
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 23 full · 1 partial · 6 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 26 full · 1 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

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

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

Worst days

  • Sat 7 Nov Max en route +4 min · last fix heading to Vlissingen Souburg +4 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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
07:13on time on time
07:27 / 07:28≈ on time ≈ on time
07:41 / 07:45≈ on time ≈ on time
07:53≈ on time ≈ +1 min
08:03 / 08:06≈ on time ≈ +1 min
08:16≈ on time ≈ +1 min
08:26≈ on time ≈ +1 min
08:30≈ on time ≈ +1 min
08:36≈ on time ≈ +1 min
08:42≈ on time ≈ +1 min
08:47≈ on time ≈ +1 min
08:57≈ on time ≈ +2 min
09:02≈ on time ≈ +2 min
09:06≈ on time ≈ +2 min
09:09on time +2 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
Sat 7 NovVlissingen Souburg 09:24Partial coverage+4 min+4 min
Fri 6 NovSittard 08:43No data—
Thu 5 NovSittard 08:44No data—
Wed 4 NovRoermond 08:24+1 min+1 min
Tue 3 NovSittard 08:39No data—
Mon 2 NovSittard 08:49No data—
Sun 1 NovSittard 08:44+1 min+1 min
Sat 31 OctSittard 08:40+2 min+2 min
Fri 30 OctSittard 08:440 min—
Thu 29 OctSittard 08:470 min—
Wed 28 OctSittard 08:400 min—
Tue 27 OctSittard 08:430 min—
Mon 26 OctSittard 08:450 min—
Sun 25 OctSittard 08:42No data—
Sat 24 OctSittard 08:45+1 min+2 min
Fri 23 OctSittard 08:400 min—
Thu 22 OctSittard 08:420 min—
Wed 21 OctSittard 08:440 min—
Tue 20 OctSittard 08:400 min—
Mon 19 OctSittard 08:460 min—
Sun 18 OctSittard 08:43+1 min+1 min
Sat 17 OctSittard 08:430 min+1 min
Fri 16 OctSittard 08:450 min—
Thu 15 OctSittard 08:450 min—
Wed 14 OctSittard 08:440 min—
Tue 13 OctSittard 08:45No data—
Mon 12 OctSittard 08:420 min—
Sun 11 OctSittard 08:45+2 min+2 min
Sat 10 OctSittard 08:45+2 min+2 min
Fri 9 OctSittard 08:46+2 min+4 min