CR-Kingston 1841 Danbury – Grand Central

View line CR-Kingston

Danbury 07:51 → Grand Central 09:55 Mon, Tue, Wed, Thu, Fri 2 h 04 min · 14 stops MBTA

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 07:51 from Danbury · Mon 9 Nov

Next departure 07:51 tomorrow · Danbury
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 14 full · 0 partial · 9 no data
On-time · 90 days
96%
54/56 runs under 3 min
RT coverage: 56 full · 0 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +4 min

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

  • Thu 5 Nov Max en route +43 min · last fix heading to Kingston +9 min
  • Tue 3 Nov Max en route +12 min · last fix heading to Kingston +5 min

Distribution · 90 days

56 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 14% · 8
  • On time 82% · 46
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 91% T n=11
  • 100% W n=9
  • 88% T n=8
  • 100% F n=8
  • 100% S n=5
  • 100% S n=7

Stops and timetable

Timetable of the latest run from the operator’s GTFS (14 stops).

Last 90 days, 56 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 10
07:51on time on time
07:57≈ on time ≈ on time
08:05≈ on time ≈ on time
08:14≈ on time ≈ on time
08:21≈ on time ≈ on time
08:25≈ on time ≈ on time
08:31≈ on time ≈ on time
08:45≈ on time ≈ on time
08:50≈ on time ≈ on time
08:53≈ on time ≈ on time
08:56≈ on time ≈ on time
09:03≈ on time ≈ on time
09:43≈ on time ≈ +1 min
09:55on time +2 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.

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 6 NovKingston 18:33Partial coverageNo data—
Thu 5 NovKingston 01:11+9 min+43 min
Wed 4 NovGreenbush 00:48+3 min+13 min
Tue 3 NovKingston 01:05+5 min+12 min
Mon 2 NovSouth Station 18:53+2 min+18 min
Fri 30 OctForge Park/495 17:41No data—
Thu 29 OctSouth Station 23:54No data—
Wed 28 OctNeedham Heights 00:44No data—
Tue 27 OctForge Park/495 01:100 min+19 min
Mon 26 OctKingston 18:28−3 min+7 min
Sun 25 OctKingston 17:090 min+2 min
Fri 23 OctKingston 18:28−3 min+8 min
Thu 22 OctFall River Depot 00:10−2 min+3 min
Wed 21 OctWickford Junction 17:31+3 min+12 min
Tue 20 OctGreenbush 00:48+2 min+3 min
Mon 19 OctGrand Central 09:50No data—
Fri 16 OctGrand Central 09:58No data—
Thu 15 OctGrand Central 09:50No data—
Wed 14 OctGrand Central 09:54No data—
Tue 13 OctGrand Central 09:52No data—
Mon 12 OctGrand Central 09:55−4 min—
Sun 11 OctForge Park/495 01:07−3 min+35 min
Sat 10 OctFairmount 17:41−1 min+14 min
Fri 9 OctSouth Station 12:27−1 min+10 min
Thu 8 OctReadville 00:120 min+4 min
Wed 7 OctWorcester 23:37+1 min+14 min
Tue 6 OctSouth Station 19:52−3 min+13 min
Mon 5 OctStoughton 23:55+2 min+9 min
Wed 23 Sept— 00:370 min—
Tue 22 Sept— 19:590 min—