Train NS 6482 Eindhoven Centraal – Tilburg Universiteit

Eindhoven Centraal 21:51 → Tilburg Universiteit 22:29 Daily 0 h 38 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 21:51 from Eindhoven Centraal · Tue 10 Nov

Next departure 21:51 today · Eindhoven Centraal
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 13 full · 1 partial · 13 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 20 full · 1 partial · 27 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 Tilburg Universiteit, 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

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

  • Early 0% · 0
  • On time 100% · 21
  • 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=2
  • 100% W n=2
  • 100% T n=2
  • 100% F n=5
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 21 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
21:51on time on time
21:54≈ on time ≈ on time
22:00≈ on time ≈ on time
22:07≈ on time ≈ +1 min
22:14≈ on time ≈ +1 min
22:20 / 22:24≈ on time ≈ +1 min
22:29on 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

DateLast stopFinalMax
Mon 9 Nov— 22:290 min—
Sun 8 NovTilburg 22:39+1 min—
Sat 7 NovTilburg 22:38Partial coverage0 min—
Fri 6 Nov— 22:290 min—
Thu 5 Nov— 22:29No data—
Wed 4 Nov— 22:290 min—
Tue 3 Nov— 22:290 min—
Mon 2 Nov— 22:290 min—
Fri 30 Oct— 22:310 min—
Thu 29 Oct— 22:300 min—
Wed 28 Oct— 22:30No data—
Tue 27 Oct— 22:31No data—
Mon 26 Oct— 22:30No data—
Sun 25 OctTilburg 22:38No data—
Sat 24 OctTilburg 22:38No data—
Fri 23 Oct— 22:31+1 min+2 min
Thu 22 Oct— 22:31No data—
Wed 21 Oct— 22:30No data—
Tue 20 Oct— 22:30No data—
Mon 19 Oct— 21:570 min—
Sun 18 OctTilburg 22:42+3 min+3 min
Sat 17 OctTilburg 22:38No data—
Fri 16 Oct— 22:300 min—
Thu 15 Oct— 22:33No data—
Wed 14 Oct— 22:30No data—
Tue 13 Oct— 22:31No data—
Mon 12 Oct— 22:31+1 min—
Sun 11 OctTilburg 22:390 min—
Sat 10 OctBest 22:310 min—
Fri 9 Oct— 22:300 min—