Train NS 8849 Woerden – 's-Hertogenbosch

Woerden 13:54 → 's-Hertogenbosch 14:57 Mon, Tue, Wed, Thu, Sat, Sun 1 h 03 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 13:54 from Woerden · Tue 10 Nov

Next departure 13:54 today · Woerden
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 3 full · 7 partial · 9 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 6 full · 7 partial · 40 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 '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

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

  • Early 0% · 0
  • On time 100% · 13
  • 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=3
  • 100% W n=4
  • 100% T n=2
  • — F n=0
  • 100% S n=1
  • 100% S n=1

Stops and timetable

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

Last 90 days, 13 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
13:54on time on time
14:02≈ on time ≈ on time
14:06 / 14:10≈ on time ≈ on time
14:12≈ on time ≈ +1 min
14:15≈ on time ≈ +1 min
14:18 / 14:19≈ on time ≈ +1 min
14:22≈ on time ≈ +1 min
14:28≈ on time ≈ +1 min
14:36 / 14:42≈ on time ≈ +1 min
14:48≈ on time ≈ +2 min
14:57on 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
Mon 9 NovZaltbommel 15:02Partial coverage0 min—
Sun 8 NovZaltbommel 15:04+2 min+2 min
Sat 7 NovZaltbommel 15:020 min—
Thu 5 NovZaltbommel 15:04Partial coverage0 min—
Wed 4 NovZaltbommel 15:04Partial coverage+2 min+2 min
Tue 3 NovZaltbommel 15:02No data—
Mon 2 NovZaltbommel 15:02No data—
Thu 29 OctZaltbommel 15:02No data—
Wed 28 OctZaltbommel 15:03Partial coverage0 min—
Tue 27 OctZaltbommel 15:03Partial coverage0 min—
Mon 26 OctZaltbommel 15:02No data—
Thu 22 OctZaltbommel 15:02No data—
Wed 21 OctZaltbommel 15:02Partial coverage0 min—
Tue 20 OctZaltbommel 15:02Partial coverage0 min—
Mon 19 OctZaltbommel 15:020 min—
Thu 15 OctZaltbommel 15:04No data—
Wed 14 OctZaltbommel 15:03No data—
Tue 13 OctZaltbommel 15:02No data—
Mon 12 OctZaltbommel 15:02No data—
Thu 8 OctZaltbommel 15:020 min—
Wed 7 OctZaltbommel 15:05+3 min+3 min
Tue 6 OctZaltbommel 15:020 min—
Thu 1 OctZaltbommel 15:02No data—
Wed 30 SeptZaltbommel 15:02No data—
Tue 29 SeptZaltbommel 15:02No data—
Mon 28 SeptZaltbommel 15:02No data—
Thu 24 SeptZaltbommel 15:03No data—
Wed 23 SeptZaltbommel 15:02No data—
Tue 22 SeptZaltbommel 15:03No data—
Mon 21 SeptZaltbommel 15:02No data—