Train NS 21422 's-Hertogenbosch – Tilburg

's-Hertogenbosch 01:38 → Tilburg 01:52 Fri, Sat 0 h 14 min · 2 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:54 +1 min

  1. 's-Hertogenbosch01:38
  2. Tilburg01:52

Next service: Friday 01:38 from 's-Hertogenbosch · Fri 13 Nov

Full trip card
Next departure 01:38 Friday · 's-Hertogenbosch
On-time · 30 days
86%
6/7 runs under 3 min
RT coverage: 7 full · 0 partial · 2 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 7 full · 0 partial · 2 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Tilburg, in minutes. One bar per run.

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

Worst days

  • Sun 11 Oct Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 6
  • 3–10 min 14% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 7 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
's-Hertogenbosch
01:38on time on time
Tilburg
01:52+1 min +4 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
Sat 7 Nov— 01:54+1 min+1 min
Sun 1 Nov— 02:050 min—
Sat 31 Oct— 01:550 min—
Sun 25 Oct— 01:53No data—
Sat 24 Oct— 01:56+3 min+4 min
Sun 18 Oct— 01:55No data—
Sat 17 Oct— 01:55+1 min+2 min
Sun 11 Oct— 02:02+6 min+6 min
Sat 10 Oct— 01:55+2 min+2 min