Metro-North 1837 Danbury – South Norwalk

View line Metro-North

Danbury 07:28 → South Norwalk 08:21 Mon, Tue, Wed, Thu, Fri 0 h 53 min · 8 stops MTA Metro-North

Running now · updated 11:22

Heading to South Norwalk No data

Estimated arrival at South Norwalk 08:21

  1. Danbury07:28
  2. Bethel07:33
  3. Redding07:41
  4. Cannondale07:55
  5. Wilton07:59
  6. Merritt 708:04
  7. South Norwalk08:21
On-time · 30 days
79%
11/14 runs under 3 min
RT coverage: 14 full · 0 partial · 9 no data
On-time · 90 days
95%
53/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
+1min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at South Norwalk, 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 +45 min · last fix heading to South Station +45 min
  • Tue 17 Nov Max en route +18 min · last fix heading to Worcester +5 min
  • Wed 21 Oct Max en route +5 min · last fix heading to Forge Park/495 +5 min

Distribution · 90 days

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

  • Early 25% · 14
  • On time 70% · 39
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=10
  • 82% T n=11
  • 89% W n=9
  • 100% T n=8
  • 100% F n=6
  • 100% S n=6
  • 100% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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 10Today
07:28on time on time
07:33≈ on time ≈ on time
07:41≈ on time ≈ on time
07:49≈ on time ≈ on time
07:55≈ on time ≈ on time
07:59≈ on time ≈ on time
08:04≈ on time ≈ on time
08:21on time +1 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
Thu 19 NovSouth Norwalk 11:190 min—
Wed 18 NovWorcester 21:07−4 min+13 min
Tue 17 NovWorcester 21:15+5 min+18 min
Mon 16 NovReadville 22:46+1 min+21 min
Fri 13 NovProvidence 23:54No data—
Thu 12 NovProvidence 23:58No data—
Wed 11 NovReadville 00:10No data—
Tue 10 NovReadville 14:18Partial coverageNo data—
Mon 9 NovStoughton 23:33+1 min+17 min
Fri 6 NovSouth Norwalk 14:20No data—
Thu 5 NovSouth Norwalk 14:22No data—
Wed 4 NovFairmount 20:40−2 min+5 min
Tue 3 NovSouth Station 14:35−5 min+4 min
Mon 2 NovStoughton 23:56+2 min+6 min
Fri 30 OctForge Park/495 18:59No data—
Thu 29 OctStoughton 23:51No data—
Wed 28 OctFairmount 19:11No data—
Tue 27 OctSouth Station 18:40+45 min+45 min
Mon 26 OctSouth Norwalk 14:19−7 min+3 min
Sat 24 OctFairmount 18:49−1 min+11 min
Fri 23 OctSouth Station 19:53−1 min—
Thu 22 OctStoughton 23:55+1 min+20 min
Wed 21 OctForge Park/495 19:01+5 min+5 min
Tue 20 OctReadville 00:09−2 min+23 min
Mon 19 OctProvidence 01:07−4 min+16 min
Fri 16 OctProvidence 19:33−2 min+12 min
Thu 15 OctSouth Norwalk 14:21−3 min—
Wed 14 OctForge Park/495 01:100 min+3 min
Tue 13 OctGreenbush 00:42−3 min+5 min
Mon 12 OctGreenbush 16:13−4 min—