Train NS 6088 's-Hertogenbosch – Utrecht Centraal

's-Hertogenbosch 23:59 → Utrecht Centraal 00:41 Daily 0 h 42 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 23:59 from 's-Hertogenbosch · Fri 6 Nov

Full trip card

Next departure 23:59 today · 's-Hertogenbosch

On-time · 30 days

96%

23/24 runs under 3 min

RT coverage: 21 full · 3 partial · 4 no data

On-time · 90 days

96%

26/27 runs under 3 min

RT coverage: 23 full · 4 partial · 13 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 Utrecht Centraal, in minutes. One bar per run.

On time (<3 min)
3–10 min
10–30 min
30+ min
Partial coverage
No data

Worst days

Wed 4 Nov Max en route +15 min · last fix heading to — +14 min

Distribution · 90 days

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

Early 0% · 0
On time 96% · 26
3–10 min 0% · 0
10–30 min 4% · 1
30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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
's-Hertogenbosch	23:59	on time	on time
Zaltbommel	00:09	≈ on time	≈ on time
Geldermalsen	00:16	≈ on time	≈ +1 min
Culemborg	00:22	≈ on time	≈ +1 min
Houten Castellum	00:27 / 00:28	≈ on time	≈ +1 min
Houten	00:31	≈ on time	≈ +1 min
Utrecht Lunetten	00:35	≈ on time	≈ +1 min
Utrecht Vaartsche Rijn	00:38	≈ on time	≈ +1 min
Utrecht Centraal	00:41	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
Thu 5 Nov	— 00:43	No data	—
Wed 4 Nov	— 01:09	+14 min	+15 min
Mon 2 Nov	— 00:44	+2 min	+2 min
Sun 1 Nov	Utrecht Vaartsche Rijn 00:53Partial coverage	0 min	—
Sat 31 Oct	— 00:42	0 min	—
Fri 30 Oct	— 01:01	No data	—
Thu 29 Oct	— 00:45	+1 min	+2 min
Wed 28 Oct	— 00:43	0 min	—
Tue 27 Oct	— 00:47	0 min	—
Mon 26 Oct	— 00:42	0 min	—
Sun 25 Oct	Utrecht Vaartsche Rijn 01:13	No data	—
Sat 24 Oct	— 00:40	No data	—
Fri 23 Oct	— 00:41	0 min	—
Thu 22 Oct	— 00:42	0 min	—
Wed 21 Oct	— 01:01	0 min	—
Tue 20 Oct	— 00:42	0 min	—
Mon 19 Oct	— 00:56	0 min	—
Sun 18 Oct	Utrecht Vaartsche Rijn 00:56	0 min	—
Sat 17 Oct	Utrecht Vaartsche Rijn 00:54Partial coverage	0 min	—
Fri 16 Oct	— 00:48	+2 min	+4 min
Thu 15 Oct	— 00:49	0 min	—
Wed 14 Oct	— 00:45	0 min	—
Tue 13 Oct	— 00:49	0 min	—
Mon 12 Oct	— 00:42	0 min	—
Sun 11 Oct	Utrecht Vaartsche Rijn 00:52Partial coverage	0 min	—
Sat 10 Oct	— 00:43	0 min	—
Fri 9 Oct	— 00:42	0 min	—
Thu 8 Oct	— 00:42	0 min	—
Wed 7 Oct	— 00:42	0 min	—
Tue 6 Oct	— 00:42	0 min	—