Govia Thameslink Railway 541T30
View line Govia Thameslink Railway
Alerts for train 541T30
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Govia Thameslink Railway.
The mini-map returns when the train runs
On-time · 30 days
36%
9/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
On-time · 90 days
30%
20/67 runs under 3 min
RT coverage: 67 full · 0 partial · 0 no data
Typical delay
+14min
Median at arrival, 90 days
30 days: +5 min
P90
+19min
9 in 10 runs arrive with less than this
30 days: +19 min
Last 30 days
Delay at the end of each run, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 20 Aug Max en route +78 min · last fix heading to 47213 +78 min
- Tue 3 Nov Max en route +43 min · last fix heading to Letchworth Garden City +43 min
- Sat 19 Sept Max en route +44 min · last fix heading to 46228 +38 min
- Fri 7 Aug Max en route +33 min · last fix heading to 46228 +33 min
- Sat 15 Aug Max en route +34 min · last fix heading to 46228 +30 min
Distribution · 90 days
67 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 10% · 7
- On time 19% · 13
- 3–10 min 15% · 10
- 10–30 min 48% · 32
- 30+ min 7% · 5
On-time by weekday
- 15% M n=13
- 36% T n=11
- 27% W n=11
- 27% T n=11
- 30% F n=10
- 45% S n=11
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 4 Nov | Watlington 14:42 | +3 min | +6 min |
| Tue 3 Nov | Letchworth Garden City 14:03 | +43 min | +43 min |
| Mon 2 Nov | Watlington 15:04 | +25 min | +29 min |
| Sat 31 Oct | Foxton 13:58 | 0 min | — |
| Fri 30 Oct | Watlington 14:50 | +3 min | +7 min |
| Thu 29 Oct | Watlington 14:49 | +1 min | +4 min |
| Wed 28 Oct | Watlington 15:04 | +17 min | +20 min |
| Tue 27 Oct | Watlington 14:52 | +5 min | +8 min |
| Mon 26 Oct | Watlington 14:45 | −3 min | +2 min |
| Sat 24 Oct | Watlington 15:04 | +17 min | +20 min |
| Fri 23 Oct | Watlington 14:49 | +2 min | +5 min |
| Thu 22 Oct | Watlington 14:45 | −2 min | +2 min |
| Wed 21 Oct | Watlington 15:03 | +16 min | +19 min |
| Tue 20 Oct | Watlington 14:46 | −1 min | +2 min |
| Mon 19 Oct | Watlington 15:04 | +17 min | +20 min |
| Fri 16 Oct | Watlington 15:04 | +16 min | +20 min |
| Thu 15 Oct | Watlington 15:07 | +19 min | +22 min |
| Wed 14 Oct | Watlington 14:53 | +6 min | +9 min |
| Tue 13 Oct | Watlington 15:04 | +17 min | +20 min |
| Mon 12 Oct | Watlington 14:45 | −2 min | +2 min |
| Sat 10 Oct | Foxton 13:57 | 0 min | +1 min |
| Fri 9 Oct | Watlington 14:51 | +4 min | +9 min |
| Thu 8 Oct | Watlington 14:44 | −3 min | +2 min |
| Wed 7 Oct | Watlington 15:05 | +18 min | +20 min |
| Tue 6 Oct | Watlington 15:06 | +18 min | +20 min |
| Mon 5 Oct | Watlington 14:51 | +3 min | +7 min |
| Sat 3 Oct | 46228 14:49 | +2 min | +6 min |
| Thu 1 Oct | 46228 15:03 | +16 min | +19 min |
| Wed 30 Sept | 47213 13:54 | +3 min | +3 min |
| Tue 29 Sept | 46228 15:05 | +18 min | +20 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.