CR-Kingston 6027 South Station – Wickford Junction
Alerts for train 6027
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-Kingston.
Running now · updated 20:22
Heading to Wickford Junction −5 min
Estimated arrival at Wickford Junction 18:33 · 86 km/h
- South Station16:52
- Ruggles17:01
- Sharon17:17
- Attleboro17:34
- Pawtucket/Central Falls17:43
- TF Green Airport18:07
- Wickford Junction18:33
Last 30 days
Arrival delay at Wickford Junction, 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
10 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 10
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — T n=0
- — W n=0
- — T n=0
- 100% F n=2
- 100% S n=3
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 10 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 | Today |
|---|---|---|---|---|
| 16:52 | on time | on time | ||
| 16:57 | ≈ on time | ≈ on time | ||
| 17:01 | ≈ on time | ≈ on time | ||
| 17:17 | ≈ on time | ≈ on time | ||
| 17:25 | ≈ on time | ≈ on time | ||
| 17:34 | ≈ on time | ≈ on time | ||
| 17:43 | ≈ on time | ≈ on time | ||
| 17:52 / 17:53 | ≈ on time | ≈ on time | ||
| 18:07 | ≈ on time | ≈ on time | ||
| 18:33 | 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 2 Oct | KB-0351-S 17:07Partial coverage | 0 min | — |
| Sat 26 Sept | KB-0351-S 17:08 | 0 min | — |
| Sun 13 Sept | KB-0351-S 17:06 | 0 min | — |
| Fri 11 Sept | KB-0351-S 17:06 | 0 min | — |
| Mon 7 Sept | KB-0351-S 17:07 | 0 min | — |
| Sun 6 Sept | KB-0351-S 17:07 | 0 min | — |
| Sat 5 Sept | KB-0351-S 17:12 | 0 min | — |
| Sun 30 Aug | KB-0351-S 17:07 | 0 min | — |
| Sat 29 Aug | KB-0351-S 17:07 | 0 min | — |
| Sun 23 Aug | KB-0351-S 17:08 | 0 min | — |