CR-Fairmount 1819 Danbury – Grand Central
Alerts for train 1819
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-Fairmount.
It does not run today
Last recorded run: Friday 6 November No data
Next service: tomorrow 06:12 from Danbury · Mon 9 Nov
Last 30 days
Arrival delay at Grand Central, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Tue 27 Oct Max en route +115 min · last fix heading to Stoughton +8 min
- Wed 4 Nov Max en route +6 min · last fix heading to South Station +6 min
Distribution · 90 days
52 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 33% · 17
- On time 63% · 33
- 3–10 min 4% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=9
- 86% T n=7
- 89% W n=9
- 100% T n=7
- 100% F n=7
- 100% S n=6
- 100% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 52 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 06:12 | on time | on time | |
| 06:18 | ≈ on time | ≈ on time | |
| 06:26 | ≈ on time | ≈ on time | |
| 06:35 | ≈ on time | ≈ on time | |
| 06:41 | ≈ on time | ≈ on time | |
| 06:45 | ≈ on time | ≈ on time | |
| 06:52 | ≈ on time | ≈ on time | |
| 07:04 | ≈ on time | ≈ on time | |
| 07:16 | ≈ on time | ≈ on time | |
| 07:54 | ≈ on time | ≈ on time | |
| 08:08 | on time | on time |
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.
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 |
|---|---|---|---|
| Fri 6 Nov | Readville 22:43Partial coverage | No data | — |
| Thu 5 Nov | Providence 21:39 | −5 min | +10 min |
| Wed 4 Nov | South Station 00:22 | +6 min | +6 min |
| Tue 3 Nov | Providence 21:38 | −4 min | +7 min |
| Mon 2 Nov | South Station 21:26 | −1 min | +12 min |
| Fri 30 Oct | Providence 17:23 | No data | — |
| Thu 29 Oct | South Station 00:21 | No data | — |
| Wed 28 Oct | Providence 17:27 | No data | — |
| Tue 27 Oct | Stoughton 00:01 | +8 min | +115 min |
| Mon 26 Oct | Providence 21:43 | 0 min | +11 min |
| Sun 25 Oct | South Station 00:37 | −2 min | +7 min |
| Sat 24 Oct | South Station 00:36 | −3 min | +9 min |
| Fri 23 Oct | South Station 00:16 | −2 min | +8 min |
| Thu 22 Oct | Providence 17:32 | +3 min | +12 min |
| Wed 21 Oct | South Station 20:25 | −1 min | +11 min |
| Tue 20 Oct | Readville 22:46 | 0 min | +14 min |
| Mon 19 Oct | Providence 23:56 | −4 min | +24 min |
| Fri 16 Oct | Providence 23:57 | −4 min | +19 min |
| Thu 15 Oct | South Station 21:18 | −5 min | +25 min |
| Wed 14 Oct | Providence 17:31 | 0 min | +11 min |
| Tue 13 Oct | South Station 00:15 | −2 min | +13 min |
| Mon 12 Oct | Providence 17:26 | −4 min | +12 min |
| Sun 11 Oct | Foxboro 10:56 | −7 min | — |
| Sat 10 Oct | South Station 21:09 | +1 min | +13 min |
| Fri 9 Oct | South Station 00:13 | −3 min | +7 min |
| Thu 8 Oct | South Station 21:21 | −2 min | +10 min |
| Wed 7 Oct | Providence 17:31 | +1 min | +12 min |
| Tue 6 Oct | South Station 00:14 | −2 min | +15 min |
| Mon 5 Oct | Providence 21:37 | −6 min | +10 min |
| Wed 30 Sept | — 20:38 | 0 min | — |