MD 17030 Cáceres – Badajoz
Alerts for train 17030
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line MD.
Cancelled today · The operator has cancelled this train today. It is not running.
✓ Today’s run finished
Today it reached Badajoz at 07:12 +1 min
- Cáceres06:21
- Badajoz07:11
Next service: tomorrow 06:21 from Cáceres · Fri 20 Nov
Last 30 days
Arrival delay at Badajoz, 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 23 Sept Max en route +19 min · last fix heading to Badajoz +19 min
- Mon 9 Nov Max en route +9 min · last fix heading to Badajoz +9 min
- Tue 13 Oct Max en route +7 min · last fix heading to Badajoz +7 min
- Mon 5 Oct Max en route +6 min · last fix heading to Badajoz +6 min
- Wed 4 Nov Max en route +8 min · last fix heading to Badajoz +4 min
Distribution · 90 days
54 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 65% · 35
- 3–10 min 33% · 18
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 64% M n=11
- 80% T n=10
- 55% W n=11
- 67% T n=12
- 60% F n=10
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (2 stops).
Last 90 days, 54 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.
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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 19 Nov | Badajoz 07:13 | +1 min | +3 min |
| Mon 16 Nov | Badajoz 07:09 | +1 min | +1 min |
| Fri 13 Nov | Badajoz 07:14 | +3 min | +3 min |
| Thu 12 Nov | Badajoz 07:12 | +1 min | +1 min |
| Mon 9 Nov | Badajoz 07:19 | +9 min | +9 min |
| Fri 6 Nov | Badajoz 07:12 | +1 min | +2 min |
| Thu 5 Nov | Badajoz 07:14 | +3 min | +3 min |
| Wed 4 Nov | Badajoz 07:15 | +4 min | +8 min |
| Tue 3 Nov | Badajoz 07:13 | +2 min | +6 min |
| Fri 30 Oct | Badajoz 07:14 | +3 min | +3 min |
| Wed 28 Oct | Badajoz 07:11 | 0 min | +3 min |
| Tue 27 Oct | Badajoz 07:13 | +2 min | +2 min |
| Mon 26 Oct | Badajoz 07:10 | 0 min | +2 min |
| Fri 23 Oct | Badajoz 07:10 | −1 min | +2 min |
| Thu 22 Oct | Badajoz 07:12 | 0 min | +2 min |
| Wed 21 Oct | Badajoz 07:12 | 0 min | +1 min |
| Tue 20 Oct | Badajoz 07:11 | 0 min | +2 min |
| Mon 19 Oct | Badajoz 07:11 | 0 min | +2 min |
| Thu 15 Oct | Badajoz 07:12 | +1 min | +3 min |
| Wed 14 Oct | Badajoz 07:14 | +3 min | +3 min |
| Tue 13 Oct | Badajoz 07:18 | +7 min | +7 min |
| Fri 9 Oct | Badajoz 07:11 | 0 min | — |
| Thu 8 Oct | Badajoz 07:12 | 0 min | +2 min |
| Wed 7 Oct | Badajoz 07:11 | +1 min | +2 min |
| Tue 6 Oct | Badajoz 07:11 | 0 min | +3 min |
| Mon 5 Oct | Badajoz 07:17 | +6 min | +6 min |
| Fri 2 Oct | Badajoz 07:11 | 0 min | +2 min |
| Thu 1 Oct | Badajoz 07:12 | 0 min | +2 min |
| Wed 30 Sept | Badajoz 07:12 | +1 min | +2 min |
| Tue 29 Sept | Badajoz 07:11 | 0 min | +1 min |