Train NS 8845 Woerden – 's-Hertogenbosch

Woerden 12:54 → 's-Hertogenbosch 13: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: Wednesday 4 November 0 min

Next service: today 12:54 from Woerden · Thu 5 Nov

Next departure 12:54 today · Woerden
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 3 full · 4 partial · 10 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 4 full · 4 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

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

  • Early 0% · 0
  • On time 100% · 8
  • 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=3
  • 100% T n=1
  • — 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, 8 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
12:54on time on time
13:02— —
13:06 / 13:10— —
13:12— —
13:15— —
13:18 / 13:19— —
13:22— —
13:28— —
13:36 / 13:42— —
13:48— —
13:57— —

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 14:02Partial coverage0 min—
Tue 3 NovZaltbommel 14:09No data—
Mon 2 NovZaltbommel 14:04No data—
Thu 29 OctZaltbommel 14:02No data—
Wed 28 OctZaltbommel 14:02No data—
Tue 27 OctZaltbommel 14:03Partial coverage0 min—
Mon 26 OctZaltbommel 14:02No data—
Thu 22 OctZaltbommel 14:02No data—
Wed 21 OctZaltbommel 14:02No data—
Tue 20 OctZaltbommel 14:02No data—
Mon 19 OctZaltbommel 14:020 min—
Thu 15 OctZaltbommel 14:03No data—
Wed 14 OctZaltbommel 14:02Partial coverage0 min—
Tue 13 OctZaltbommel 14:02No data—
Mon 12 OctZaltbommel 14:02Partial coverage0 min—
Thu 8 OctZaltbommel 14:020 min—
Wed 7 OctZaltbommel 14:05+2 min+3 min
Tue 6 OctZaltbommel 14:020 min—
Thu 1 OctZaltbommel 14:02No data—
Wed 30 SeptZaltbommel 14:02No data—
Tue 29 SeptZaltbommel 14:02No data—
Mon 28 SeptZaltbommel 14:03No data—
Thu 24 SeptZaltbommel 14:02No data—
Wed 23 SeptZaltbommel 14:02No data—
Tue 22 SeptZaltbommel 14:02No data—
Mon 21 SeptZaltbommel 14:02No data—
Thu 17 SeptZaltbommel 14:02No data—
Wed 16 SeptZaltbommel 14:03No data—
Tue 15 SeptZaltbommel 14:02No data—
Mon 14 SeptZaltbommel 14:03No data—