Train NS 6446 Weert – Tilburg Universiteit

Weert 12:20 → Tilburg Universiteit 13:29 Daily 1 h 09 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Tilburg at 13:38 No data

  1. Weert12:20
  2. Heeze12:33
  3. Geldrop12:37
  4. Eindhoven Strijp-S12:54
  5. Boxtel13:07
  6. Tilburg13:20
  7. Tilburg Universiteit13:29

Next service: tomorrow 12:20 from Weert · Sat 7 Nov

Next departure 12:20 tomorrow · Weert
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 7 full · 10 partial · 12 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 7 full · 13 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

  • Early 0% · 0
  • On time 100% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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
12:20on time on time
12:26≈ on time ≈ on time
12:33≈ on time ≈ on time
12:37≈ on time ≈ on time
12:43 / 12:51≈ on time ≈ on time
12:54≈ on time ≈ on time
13:00≈ on time ≈ on time
13:07≈ on time ≈ on time
13:14≈ on time ≈ on time
13:20 / 13:24≈ on time ≈ on time
13:29on time on time

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
Fri 6 NovTilburg 13:38No data—
Thu 5 NovTilburg 13:38No data—
Wed 4 NovTilburg 13:39Partial coverage0 min—
Tue 3 NovTilburg 13:38No data—
Mon 2 NovTilburg 13:39Partial coverage0 min—
Sat 31 OctGeldrop 12:52+1 min—
Fri 30 OctTilburg 13:380 min—
Thu 29 OctTilburg 13:40No data—
Wed 28 OctTilburg 13:39Partial coverage0 min—
Tue 27 OctTilburg 13:38No data—
Mon 26 OctTilburg 13:39No data—
Sun 25 OctTilburg 13:39No data—
Sat 24 OctTilburg 13:39Partial coverage+1 min—
Fri 23 OctTilburg 13:39Partial coverage0 min—
Thu 22 OctTilburg 13:43Partial coverage0 min—
Wed 21 OctTilburg 13:38Partial coverage0 min—
Tue 20 OctTilburg 13:39Partial coverage0 min—
Mon 19 OctTilburg 13:39Partial coverage0 min—
Sun 18 OctTilburg 13:380 min—
Sat 17 OctTilburg 13:38No data—
Fri 16 OctTilburg 13:380 min—
Thu 15 OctTilburg 13:38No data—
Wed 14 OctTilburg 13:39No data—
Tue 13 OctTilburg 13:39No data—
Mon 12 OctTilburg 13:40No data—
Sun 11 OctTilburg 13:380 min—
Sat 10 OctTilburg 13:380 min—
Fri 9 OctTilburg 13:380 min—
Thu 8 OctTilburg 13:39Partial coverage0 min—
Wed 7 OctTilburg 13:39Partial coverage0 min—