Metro-North 1442 Grand Central – South Norwalk

View line Metro-North

Grand Central 16:00 → South Norwalk 17:08 Mon, Tue, Wed, Thu, Fri 1 h 08 min · 7 stops MTA Metro-North

It has not run yet today

Last recorded run: Friday 13 November No data

Next service: today 16:00 from Grand Central · Mon 16 Nov

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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 12 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
16:00on time on time
16:10≈ on time ≈ on time
16:49≈ on time ≈ on time
16:54≈ on time ≈ on time
16:57≈ on time ≈ on time
17:00≈ on time ≈ on time
17:08on 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 13 NovSouth Norwalk 17:06No data—
Thu 12 NovRowayton 17:03Partial coverageNo data—
Wed 11 NovSouth Norwalk 17:06No data—
Tue 10 NovSouth Norwalk 17:05No data—
Mon 9 NovRowayton 17:00Partial coverageNo data—
Fri 6 NovSouth Norwalk 17:07No data—
Thu 5 NovSouth Norwalk 17:09No data—
Wed 4 NovSouth Norwalk 17:05No data—
Tue 3 NovSouth Norwalk 17:05No data—
Mon 2 NovSouth Norwalk 17:08No data—
Fri 30 OctSouth Norwalk 17:11No data—
Thu 29 OctSouth Norwalk 17:05No data—
Wed 28 OctRowayton 17:00Partial coverageNo data—
Tue 27 OctRowayton 17:00Partial coverageNo data—
Mon 26 OctRowayton 17:00Partial coverageNo data—
Fri 23 OctSouth Norwalk 17:07No data—
Thu 22 OctSouth Norwalk 17:05No data—
Wed 21 OctSouth Norwalk 17:06No data—
Tue 20 OctSouth Norwalk 17:09No data—
Mon 19 OctSouth Norwalk 17:08No data—
Fri 16 OctRowayton 17:02Partial coverageNo data—
Thu 15 OctSouth Norwalk 17:04No data—
Wed 14 OctSouth Norwalk 17:13No data—
Tue 13 OctRowayton 17:03Partial coverageNo data—
Mon 12 OctRowayton 17:10Partial coverageNo data—
Fri 9 OctRowayton 17:01Partial coverageNo data—
Thu 8 OctSouth Norwalk 17:04No data—
Wed 7 OctRowayton 17:03Partial coverageNo data—
Tue 6 OctRowayton 17:01Partial coverageNo data—
Mon 5 OctRowayton 17:00Partial coverageNo data—