ScotRail 31T66
View line ScotRail
Alerts for train 31T66
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line ScotRail.
The mini-map returns when the train runs
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
On-time · 90 days
87%
67/77 runs under 3 min
RT coverage: 77 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +1 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
- Wed 29 Jul Max en route +19 min · last fix heading to 06421 +15 min
- Mon 5 Oct Max en route +7 min · last fix heading to Lenzie +7 min
- Thu 27 Aug Max en route +6 min · last fix heading to 06421 +6 min
- Sat 29 Aug Max en route +6 min · last fix heading to 06421 +5 min
- Wed 19 Aug Max en route +5 min · last fix heading to 06421 +5 min
Distribution · 90 days
77 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 14% · 11
- On time 73% · 56
- 3–10 min 12% · 9
- 10–30 min 1% · 1
- 30+ min 0% · 0
On-time by weekday
- 85% M n=13
- 100% T n=12
- 75% W n=12
- 85% T n=13
- 85% F n=13
- 92% S n=13
- 100% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 19 Oct | Bishopbriggs 23:03 | +1 min | +4 min |
| Sat 17 Oct | Bishopbriggs 23:03 | 0 min | +1 min |
| Fri 16 Oct | Bishopbriggs 23:02 | 0 min | +5 min |
| Thu 15 Oct | Lenzie 22:58 | −4 min | — |
| Wed 14 Oct | Lenzie 23:02 | 0 min | +1 min |
| Tue 13 Oct | Lenzie 22:56 | −7 min | +1 min |
| Mon 12 Oct | Lenzie 23:02 | −1 min | — |
| Sat 10 Oct | Lenzie 22:57 | −7 min | — |
| Fri 9 Oct | Bishopbriggs 23:03 | +1 min | +1 min |
| Thu 8 Oct | Lenzie 23:02 | 0 min | — |
| Wed 7 Oct | Bishopbriggs 23:03 | +1 min | +1 min |
| Tue 6 Oct | Bishopbriggs 23:03 | 0 min | +1 min |
| Mon 5 Oct | Lenzie 23:09 | +7 min | +7 min |
| Sun 4 Oct | — 02:41 | 0 min | — |
| Sat 3 Oct | 06421 22:54 | −8 min | — |
| Fri 2 Oct | 06421 23:02 | 0 min | — |
| Thu 1 Oct | 06421 23:04 | +1 min | +7 min |
| Wed 30 Sept | 06421 23:02 | 0 min | — |
| Tue 29 Sept | 06421 23:04 | +1 min | +1 min |
| Mon 28 Sept | 06421 23:02 | 0 min | — |
| Sat 26 Sept | 06421 23:03 | 0 min | +2 min |
| Fri 25 Sept | 06421 23:03 | +1 min | +1 min |
| Thu 24 Sept | 06421 22:57 | −5 min | — |
| Wed 23 Sept | 06421 23:02 | 0 min | — |
| Tue 22 Sept | 06421 23:02 | 0 min | — |
| Mon 21 Sept | 06421 23:03 | 0 min | — |
| Sat 19 Sept | 06421 23:03 | 0 min | — |
| Fri 18 Sept | 06421 23:04 | +2 min | +2 min |
| Thu 17 Sept | 06421 23:03 | 0 min | +2 min |
| Wed 16 Sept | 06421 23:02 | 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.