127 7050 Forge Park/495 – Readville

View line 127

Forge Park/495 23:28 → Readville 00:12 Mon, Tue, Wed, Thu, Fri 0 h 44 min · 11 stops MARTA

It has not run yet today

Last recorded run: Monday 5 October No data

Next service: today 23:28 from Forge Park/495 · Thu 5 Nov

Next departure 23:28 today · Forge Park/495
On-time · 30 days
—
Too little data (0/0 runs with data)
RT coverage: 0 full · 0 partial · 0 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 1 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 Readville, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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:49≈ on time ≈ on time
23:52≈ on time ≈ on time
23:55≈ on time ≈ on time
23:57≈ on time ≈ on time
00:00≈ on time ≈ on time
00:03≈ on time ≈ on time
00:06≈ on time ≈ on time
00:12on 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
Mon 5 Oct— 06:18No data—
Fri 2 Oct— 17:110 min—
Thu 1 Oct— 19:070 min—
Wed 30 Sept— 19:590 min—
Tue 29 Sept— 19:590 min—
Sun 30 Aug— 21:380 min—
Sat 29 Aug— 19:590 min—
Fri 28 Aug— 17:410 min—
Thu 27 Aug— 19:590 min—
Wed 26 Aug— 19:590 min—
Tue 25 Aug— 21:260 min—
Mon 24 Aug— 19:590 min—
Fri 21 Aug— 02:170 min—
Thu 20 Aug— 19:590 min—
Wed 19 Aug— 19:590 min—
Tue 18 Aug— 19:590 min—
Mon 17 Aug— 19:590 min—
Sun 16 Aug— 10:470 min—
Sat 15 Aug— 19:590 min—
Fri 14 Aug— 13:240 min—
Thu 13 Aug— 19:580 min—
Tue 11 Aug— 08:040 min—
Mon 10 Aug— 19:580 min—
Sun 9 Aug— 19:580 min—
Sat 8 Aug— 19:580 min—