Train NS 6477 Tilburg Universiteit – Weert

Tilburg Universiteit 21:34 → Weert 22:40 Daily 1 h 06 min · 11 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 21:34 from Tilburg Universiteit · Fri 6 Nov

Next departure 21:34 today · Tilburg Universiteit
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 13 full · 4 partial · 11 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 16 full · 4 partial · 28 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Weert, 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 +7 min · last fix heading to — +7 min
  • Fri 23 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 18
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 67% W n=3
  • 100% T n=3
  • 67% F n=3
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 20 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:34on time on time
21:38 / 21:39≈ on time ≈ +1 min
21:45≈ on time ≈ +1 min
21:52 / 21:53≈ on time ≈ +1 min
21:59≈ on time ≈ +2 min
22:05≈ on time ≈ +2 min
22:09 / 22:17≈ on time ≈ +2 min
22:22≈ on time ≈ +3 min
22:26≈ on time ≈ +3 min
22:33≈ on time ≈ +3 min
22:40+1 min +3 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
Thu 5 Nov— 22:39No data—
Wed 4 Nov— 22:48+7 min+7 min
Mon 2 Nov— 22:390 min—
Sun 1 NovMaarheeze 22:49+1 min—
Sat 31 OctMaarheeze 22:48No data—
Fri 30 Oct— 22:41No data—
Thu 29 Oct— 22:44+1 min+1 min
Wed 28 Oct— 22:44No data—
Tue 27 Oct— 22:44No data—
Mon 26 Oct— 22:430 min—
Sun 25 OctMaarheeze 22:48No data—
Sat 24 OctMaarheeze 22:47Partial coverage0 min—
Fri 23 Oct— 22:48+4 min+4 min
Thu 22 Oct— 22:440 min—
Wed 21 Oct— 22:44No data—
Tue 20 Oct— 22:470 min—
Mon 19 Oct— 22:42No data—
Sun 18 OctMaarheeze 22:48Partial coverage+1 min+1 min
Sat 17 OctMaarheeze 22:49No data—
Fri 16 Oct— 22:420 min+1 min
Thu 15 Oct— 22:44No data—
Wed 14 Oct— 22:42+1 min—
Tue 13 Oct— 22:42No data—
Mon 12 Oct— 22:47+2 min+3 min
Sun 11 OctMaarheeze 22:48Partial coverage0 min+1 min
Sat 10 OctEindhoven Strijp-S 22:44Partial coverage+1 min+2 min
Fri 9 Oct— 22:46+2 min+3 min
Thu 8 Oct— 22:440 min+1 min
Wed 7 Oct— 22:46+1 min+2 min
Tue 6 Oct— 22:420 min+1 min