Train NS 8855 Woerden – 's-Hertogenbosch

Woerden 15:24 → 's-Hertogenbosch 16:27 Mon, Tue, Wed, Thu, Sat, Sun 1 h 03 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 15:24 from Woerden · Thu 5 Nov

Next departure 15:24 today · Woerden
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 5 full · 4 partial · 8 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 6 full · 4 partial · 42 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

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

  • Early 0% · 0
  • On time 100% · 10
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 100% W n=4
  • 100% T n=2
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 10 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
15:24on time on time
15:32≈ on time ≈ on time
15:36 / 15:40≈ on time ≈ on time
15:42≈ on time ≈ on time
15:45≈ on time ≈ on time
15:48 / 15:49≈ on time ≈ on time
15:52≈ on time ≈ +1 min
15:58≈ on time ≈ +1 min
16:06 / 16:12≈ on time ≈ +1 min
16:18≈ on time ≈ +1 min
16:27on time +1 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
Wed 4 NovZaltbommel 16:34Partial coverage0 min—
Tue 3 NovZaltbommel 16:32No data—
Mon 2 NovZaltbommel 16:32No data—
Thu 29 OctZaltbommel 16:330 min—
Wed 28 OctZaltbommel 16:320 min—
Tue 27 OctZaltbommel 16:40No data—
Mon 26 OctZaltbommel 16:46No data—
Thu 22 OctZaltbommel 16:33No data—
Wed 21 OctZaltbommel 16:34No data—
Tue 20 OctZaltbommel 16:32Partial coverage0 min—
Mon 19 OctZaltbommel 16:330 min—
Thu 15 OctZaltbommel 16:32No data—
Wed 14 OctZaltbommel 16:32Partial coverage0 min—
Tue 13 OctZaltbommel 16:32No data—
Mon 12 OctZaltbommel 16:32Partial coverage0 min—
Thu 8 OctZaltbommel 16:320 min—
Wed 7 OctZaltbommel 16:320 min—
Tue 6 OctZaltbommel 16:34+3 min+3 min
Thu 1 OctZaltbommel 16:32No data—
Wed 30 SeptZaltbommel 16:33No data—
Tue 29 SeptZaltbommel 16:32No data—
Mon 28 SeptZaltbommel 16:33No data—
Thu 24 SeptZaltbommel 16:32No data—
Wed 23 SeptZaltbommel 16:33No data—
Tue 22 SeptZaltbommel 16:36No data—
Mon 21 SeptZaltbommel 16:37No data—
Thu 17 SeptZaltbommel 16:32No data—
Wed 16 SeptZaltbommel 16:33No data—
Tue 15 SeptZaltbommel 16:33No data—
Mon 14 SeptZaltbommel 16:33No data—