CR-Franklin 1840 Forge Park/495 – Readville

View line CR-Franklin

Forge Park/495 23:28 → Readville 00:10 Daily 0 h 42 min · 11 stops MBTA

It does not run today

Last recorded run: Monday 9 November +10 min

On-time · 30 days
44%
8/18 runs under 3 min
RT coverage: 18 full · 0 partial · 4 no data
On-time · 90 days
78%
49/63 runs under 3 min
RT coverage: 63 full · 0 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +4 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +10 min

Last 30 days

Arrival delay at Readville, 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 +39 min · last fix heading to Worcester +39 min
  • Tue 20 Oct Max en route +11 min · last fix heading to Worcester +11 min
  • Mon 9 Nov Max en route +36 min · last fix heading to Readville +10 min
  • Sun 18 Oct Max en route +14 min · last fix heading to Worcester +7 min
  • Wed 4 Nov Max en route +7 min · last fix heading to Forge Park/495 +6 min

Distribution · 90 days

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

  • Early 13% · 8
  • On time 65% · 41
  • 3–10 min 19% · 12
  • 10–30 min 2% · 1
  • 30+ min 2% · 1

On-time by weekday

  • 75% M n=12
  • 78% T n=9
  • 78% W n=9
  • 82% T n=11
  • 78% F n=9
  • 80% S n=5
  • 75% S n=8

Stops and timetable

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

Last 90 days, 63 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
23:28on time on time
23:35≈ on time ≈ on time
23:42≈ on time ≈ on time
23:48≈ on time ≈ +1 min
23:52≈ on time ≈ +2 min
23:55≈ on time ≈ +2 min
23:57≈ on time ≈ +3 min
00:00≈ on time ≈ +3 min
00:02≈ on time ≈ +4 min
00:06≈ on time ≈ +5 min
00:10on time +5 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
Mon 9 NovReadville 00:18+10 min+36 min
Sun 8 NovWorcester 01:02+5 min+5 min
Fri 6 NovWorcester 23:42No data—
Thu 5 NovWorcester 01:53+39 min+39 min
Wed 4 NovForge Park/495 19:03+6 min+7 min
Tue 3 NovQuincy Center 10:34−2 min+8 min
Mon 2 NovSouth Station 08:53+2 min+11 min
Sun 1 NovReadville 00:09+1 min+13 min
Sat 31 OctReadville 23:21−3 min+9 min
Fri 30 OctReadville 00:11No data—
Thu 29 OctForge Park/495 19:00No data—
Wed 28 OctWorcester 01:11No data—
Tue 27 OctReadville 00:13+3 min+43 min
Mon 26 OctSouth Station 19:37−3 min+15 min
Sun 25 OctReadville 00:07−2 min+9 min
Sat 24 OctBack Bay 19:27+3 min+7 min
Fri 23 OctStoughton 20:43+5 min+8 min
Thu 22 OctWorcester 21:17+5 min+13 min
Wed 21 OctProvidence 23:52−8 min+21 min
Tue 20 OctWorcester 21:22+11 min+11 min
Mon 19 OctSouth Station 06:42+4 min+4 min
Sun 18 OctWorcester 01:05+7 min+14 min
Fri 16 OctWorcester 23:39+3 min+14 min
Thu 15 OctProvidence 23:54−6 min+5 min
Wed 14 OctStoughton 20:40+3 min+13 min
Tue 13 OctWorcester 01:19+4 min+6 min
Mon 12 OctWorcester 23:40+3 min+11 min
Fri 9 OctForge Park/495 19:02+4 min+16 min
Thu 8 OctProvidence 23:54−6 min+12 min
Wed 7 OctWorcester 01:19+3 min+8 min