Govia Thameslink Railway 629N17
View line Govia Thameslink Railway
Alerts for train 629N17
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.
It does not run today
Last recorded run: Monday 12 October 0 min
The mini-map returns when the train runs
On-time · 30 days
79%
11/14 runs under 3 min
RT coverage: 14 full · 0 partial · 0 no data
On-time · 90 days
63%
22/35 runs under 3 min
RT coverage: 35 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+14min
9 in 10 runs arrive with less than this
30 days: +9 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 13 Aug Max en route +23 min · last fix heading to Brighton +23 min
- Fri 28 Aug Max en route +21 min · last fix heading to Brighton +19 min
- Thu 27 Aug Max en route +19 min · last fix heading to Earlswood (Surrey) +19 min
- Fri 11 Sept Max en route +16 min · last fix heading to Brighton +16 min
- Wed 7 Oct Max en route +14 min · last fix heading to Brighton +12 min
Distribution · 90 days
35 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 3% · 1
- On time 60% · 21
- 3–10 min 11% · 4
- 10–30 min 26% · 9
- 30+ min 0% · 0
On-time by weekday
- 75% M n=8
- 83% T n=6
- 33% W n=6
- 57% T n=7
- 25% F n=4
- 100% S n=1
- 100% S n=3
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 12 Oct | — 09:51 | 0 min | — |
| Sun 11 Oct | Three Bridges 01:02 | 0 min | +1 min |
| Sat 10 Oct | Three Bridges 01:00 | 0 min | +4 min |
| Thu 8 Oct | Brighton 01:42 | +7 min | +8 min |
| Wed 7 Oct | Brighton 01:47 | +12 min | +14 min |
| Tue 6 Oct | Brighton 01:37 | +2 min | +2 min |
| Mon 5 Oct | Brighton 01:35 | 0 min | +2 min |
| Thu 1 Oct | — 11:12 | −4 min | — |
| Mon 28 Sept | Brighton 01:33 | −1 min | +1 min |
| Sun 27 Sept | 87927 00:59 | −1 min | — |
| Fri 25 Sept | Brighton 01:31 | −1 min | — |
| Thu 24 Sept | 87927 00:59 | −1 min | +2 min |
| Wed 23 Sept | Brighton 01:42 | +10 min | +11 min |
| Tue 22 Sept | 87927 00:59 | 0 min | +9 min |
| Fri 11 Sept | Brighton 01:48 | +16 min | +16 min |
| Thu 10 Sept | 87927 00:59 | +1 min | +5 min |
| Wed 9 Sept | 87927 00:59 | +2 min | +5 min |
| Tue 8 Sept | 87927 00:59 | −1 min | +5 min |
| Mon 7 Sept | 87927 00:59 | −1 min | +2 min |
| Fri 28 Aug | Brighton 01:51 | +19 min | +21 min |
| Thu 27 Aug | Earlswood (Surrey) 00:59 | +19 min | +19 min |
| Wed 26 Aug | Three Bridges 00:59 | +2 min | +16 min |
| Tue 25 Aug | Three Bridges 00:59 | +12 min | +24 min |
| Mon 24 Aug | Gatwick Airport 00:59 | +11 min | +12 min |
| Thu 13 Aug | Brighton 01:56 | +23 min | +23 min |
| Wed 12 Aug | Three Bridges 00:59 | +6 min | +8 min |
| Tue 11 Aug | 87927 00:59 | −1 min | +13 min |
| Mon 10 Aug | Three Bridges 00:59 | +12 min | +13 min |
| Mon 3 Aug | Brighton 01:32 | 0 min | +1 min |
| Sun 2 Aug | 87927 00:59 | 0 min | +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.