CR-Kingston 6027 South Station – Wickford Junction

View line CR-Kingston

South Station 16:52 → Wickford Junction 18:33 Mon, Tue, Wed, Thu, Fri 1 h 41 min · 10 stops MBTA

Running now · updated 20:22

Heading to Wickford Junction −5 min

Estimated arrival at Wickford Junction 18:33 · 86 km/h

  1. South Station16:52
  2. Ruggles17:01
  3. Sharon17:17
  4. Attleboro17:34
  5. Pawtucket/Central Falls17:43
  6. TF Green Airport18:07
  7. Wickford Junction18:33
On-time · 30 days
—
Too little data (0/0 runs with data)
RT coverage: 0 full · 0 partial · 0 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 9 full · 1 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

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.

StopSched.Usually 9 days in 10Today
16:52on 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:33on 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

DateLast stopFinalMax
Fri 2 OctKB-0351-S 17:07Partial coverage0 min—
Sat 26 SeptKB-0351-S 17:080 min—
Sun 13 SeptKB-0351-S 17:060 min—
Fri 11 SeptKB-0351-S 17:060 min—
Mon 7 SeptKB-0351-S 17:070 min—
Sun 6 SeptKB-0351-S 17:070 min—
Sat 5 SeptKB-0351-S 17:120 min—
Sun 30 AugKB-0351-S 17:070 min—
Sat 29 AugKB-0351-S 17:070 min—
Sun 23 AugKB-0351-S 17:080 min—