Metro-North 1874 South Norwalk – Danbury

View line Metro-North

South Norwalk 20:05 → Danbury 20:55 Mon, Tue, Wed, Thu, Fri 0 h 50 min · 8 stops MTA Metro-North

It has not run yet today

Last recorded run: Tuesday 10 November No data

Next service: today 20:05 from South Norwalk · Wed 11 Nov

Next departure 20:05 today · South Norwalk
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 27 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 Danbury, 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

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

  • Early 0% · 0
  • On time 100% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=3
  • 100% W n=4
  • 100% T n=2
  • 100% F n=4
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 22 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
20:05on time on time
20:15≈ on time ≈ on time
20:21≈ on time ≈ on time
20:24≈ on time ≈ on time
20:30≈ on time ≈ on time
20:38≈ on time ≈ on time
20:45≈ on time ≈ on time
20:55on 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
Tue 10 NovDanbury 21:13No data—
Mon 9 NovDanbury 20:54No data—
Fri 6 NovBethel 20:49Partial coverageNo data—
Thu 5 NovDanbury 20:54No data—
Wed 4 NovBethel 20:49Partial coverageNo data—
Tue 3 NovBethel 20:50Partial coverageNo data—
Mon 2 NovDanbury 20:54No data—
Fri 30 OctDanbury 20:53No data—
Thu 29 OctBethel 20:50Partial coverageNo data—
Wed 28 OctBethel 20:48Partial coverageNo data—
Tue 27 OctDanbury 20:54No data—
Mon 26 OctDanbury 20:54No data—
Fri 23 OctDanbury 20:50No data—
Thu 22 OctDanbury 20:53No data—
Wed 21 OctDanbury 20:52No data—
Tue 20 OctDanbury 20:54No data—
Mon 19 OctBethel 20:49Partial coverageNo data—
Fri 16 OctDanbury 20:57No data—
Thu 15 OctDanbury 20:52No data—
Wed 14 OctDanbury 20:55No data—
Tue 13 OctDanbury 20:55No data—
Mon 12 OctDanbury 20:58No data—
Fri 9 OctBethel 20:47Partial coverageNo data—
Thu 8 OctBethel 20:53Partial coverageNo data—
Wed 7 OctBethel 20:48Partial coverageNo data—
Tue 6 OctDanbury 20:53No data—
Mon 5 OctDanbury 20:57No data—
Wed 30 Sept— 23:110 min—
Tue 29 Sept— 19:590 min—
Mon 28 Sept— 19:590 min—