CR-Foxboro 9761
Alerts for train 9761
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line CR-Foxboro.
Train 9761: final delay under 3 min on 5 of its 5 runs with data in the last 90 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 17:39 (GMT-5).
An alert on this phone or computer when the 9761 is 5 min or more late, every day it runs. No account, no email.
Not running right now
Last recorded run: Friday 2 October 0 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
Distribution · 90 days
5 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 5
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- 100% F n=3
- 100% S n=1
- 100% S n=1
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 2 Oct | NEC-2287-05 17:11 | 0 min | — |
| Fri 11 Sept | FS-0049-S 17:46 | 0 min | — |
| Sun 6 Sept | FS-0049-S 17:50 | 0 min | — |
| Fri 4 Sept | FS-0049-S 17:47 | 0 min | — |
| Sat 29 Aug | FS-0049-S 17:49 | 0 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 10 July 2026.