Train NS 8841 Woerden – 's-Hertogenbosch
Running now · updated 11:41
Heading to 's-Hertogenbosch No data
Estimated arrival at 's-Hertogenbosch 12:57
- Woerden11:54
- Utrecht Centraal12:06
- Utrecht Vaartsche Rijn12:12
- Houten12:18
- Culemborg12:28
- Geldermalsen12:36
- 's-Hertogenbosch12:57
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
17 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 17
- 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=3
- 100% W n=4
- 100% T n=3
- — 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, 17 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.
| Stop | Sched. | Usually | 9 days in 10 | Today |
|---|---|---|---|---|
| 11:54 | on time | on time | ||
| 12:02 | ≈ on time | ≈ on time | ||
| 12:06 / 12:10 | ≈ on time | ≈ on time | ||
| 12:12 | ≈ on time | ≈ on time | ||
| 12:15 | ≈ on time | ≈ on time | ||
| 12:18 / 12:19 | ≈ on time | ≈ on time | ||
| 12:22 | ≈ on time | ≈ +1 min | ||
| 12:28 | ≈ on time | ≈ +1 min | ||
| 12:36 / 12:42 | ≈ on time | ≈ +1 min | ||
| 12:48 | ≈ on time | ≈ +1 min | ||
| 12:57 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Tue 10 Nov | Woerden 11:39 | No data | — |
| Mon 9 Nov | Zaltbommel 13:02Partial coverage | 0 min | — |
| Sun 8 Nov | Zaltbommel 13:02 | 0 min | — |
| Sat 7 Nov | Zaltbommel 13:04 | +2 min | +3 min |
| Thu 5 Nov | Zaltbommel 13:02 | No data | — |
| Wed 4 Nov | Zaltbommel 13:02Partial coverage | 0 min | — |
| Tue 3 Nov | Zaltbommel 12:59 | No data | — |
| Mon 2 Nov | Zaltbommel 13:02Partial coverage | 0 min | — |
| Thu 29 Oct | Zaltbommel 13:02Partial coverage | 0 min | — |
| Wed 28 Oct | Zaltbommel 13:02Partial coverage | 0 min | — |
| Tue 27 Oct | Zaltbommel 13:05Partial coverage | 0 min | — |
| Mon 26 Oct | Zaltbommel 13:03Partial coverage | 0 min | — |
| Thu 22 Oct | Zaltbommel 13:02 | No data | — |
| Wed 21 Oct | Zaltbommel 13:02 | No data | — |
| Tue 20 Oct | Zaltbommel 13:02Partial coverage | 0 min | — |
| Mon 19 Oct | Zaltbommel 13:02 | 0 min | — |
| Thu 15 Oct | Zaltbommel 13:05Partial coverage | 0 min | — |
| Wed 14 Oct | Zaltbommel 13:02Partial coverage | 0 min | — |
| Tue 13 Oct | Zaltbommel 13:02 | No data | — |
| Mon 12 Oct | Zaltbommel 13:02Partial coverage | 0 min | — |
| Thu 8 Oct | Zaltbommel 13:02 | 0 min | — |
| Wed 7 Oct | Zaltbommel 13:07 | 0 min | — |
| Tue 6 Oct | Zaltbommel 13:02 | 0 min | — |
| Thu 1 Oct | Zaltbommel 13:03 | No data | — |
| Wed 30 Sept | Zaltbommel 13:02 | No data | — |
| Tue 29 Sept | Zaltbommel 13:02 | No data | — |
| Mon 28 Sept | Zaltbommel 13:03 | No data | — |
| Thu 24 Sept | Zaltbommel 13:02 | No data | — |
| Wed 23 Sept | Zaltbommel 13:02 | No data | — |
| Tue 22 Sept | Zaltbommel 13:03 | No data | — |