Train NS 21425 Tilburg – 's-Hertogenbosch

Tilburg 01:58 → 's-Hertogenbosch 02:13 Fri, Sat 0 h 15 min · 2 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 02:14 0 min

  1. Tilburg01:58
  2. 's-Hertogenbosch02:13

Next service: Friday 01:58 from Tilburg · Fri 13 Nov

Full trip card
Next departure 01:58 Friday · Tilburg
On-time · 30 days
78%
7/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
78%
7/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

Worst days

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 7
  • 3–10 min 22% · 2
  • 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
  • 80% S n=5
  • 75% S n=4

Stops and timetable

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

Last 90 days, 9 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
Tilburg
01:58on time +1 min
's-Hertogenbosch
02:13on time +5 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— 02:140 min—
Sun 1 Nov— 02:230 min—
Sat 31 Oct— 02:140 min—
Sun 25 Oct— 02:140 min—
Sat 24 Oct— 02:150 min—
Sun 18 Oct— 02:210 min—
Sat 17 Oct— 02:140 min—
Sun 11 Oct— 02:25+5 min+5 min
Sat 10 Oct— 02:29+6 min+8 min