Train NS 3684 Roosendaal – 's-Hertogenbosch

Roosendaal 23:57 → 's-Hertogenbosch 00:49 Daily 0 h 52 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 23:57 from Roosendaal · Fri 6 Nov

Next departure 23:57 today · Roosendaal
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 19 full · 2 partial · 4 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 21 full · 3 partial · 16 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

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 100% · 24
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
23:57on time on time
00:07≈ on time ≈ on time
00:15 / 00:19≈ on time ≈ on time
00:32 / 00:34≈ on time ≈ on time
00:49on 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 Nov— 00:49No data—
Wed 4 Nov— 00:53+1 min+3 min
Mon 2 Nov— 00:490 min—
Sun 1 NovTilburg 00:48Partial coverage0 min—
Fri 30 Oct— 00:520 min—
Thu 29 Oct— 00:500 min—
Wed 28 Oct— 00:500 min—
Tue 27 Oct— 00:500 min—
Mon 26 Oct— 01:010 min—
Sun 25 OctTilburg 00:49No data—
Sat 24 Oct— 00:510 min+1 min
Thu 22 Oct— 00:51No data—
Wed 21 Oct— 00:51No data—
Tue 20 Oct— 00:510 min—
Mon 19 Oct— 00:500 min—
Sun 18 OctTilburg 00:50Partial coverage0 min—
Sat 17 OctTilburg 00:500 min—
Fri 16 Oct— 00:510 min—
Thu 15 Oct— 00:500 min—
Wed 14 Oct— 00:490 min—
Tue 13 Oct— 00:500 min—
Mon 12 Oct— 00:500 min—
Sun 11 OctTilburg 00:490 min—
Fri 9 Oct— 00:510 min—
Thu 8 Oct— 00:530 min+4 min
Wed 7 Oct— 00:500 min+3 min
Tue 6 Oct— 00:500 min—
Mon 5 OctEtten-Leur 00:51Partial coverage+1 min+3 min
Sun 4 OctTilburg 00:48No data—
Sat 3 OctTilburg 00:48No data—