Govia Thameslink Railway 871W86 London Victoria → Brighton

View line Govia Thameslink Railway

London Victoria 16:29 → Brighton 17:35 Mon, Tue, Wed, Thu, Fri 1 h 06 min · 7 stops Govia Thameslink Railway

It does not run today

Last recorded run: Friday 20 November −1 min

Next service: Monday 16:29 from London Victoria · Mon 23 Nov

Next departure 16:29 Monday · London Victoria
On-time · 30 days
47%
8/17 runs under 3 min
RT coverage: 16 full · 1 partial · 0 no data
On-time · 90 days
42%
25/59 runs under 3 min
RT coverage: 58 full · 1 partial · 0 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +3 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +6 min

Last 30 days

Arrival delay at Brighton, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 28 Aug Max en route +35 min · last fix heading to Brighton +30 min
  • Fri 16 Oct Max en route +22 min · last fix heading to Brighton +20 min
  • Wed 23 Sept Max en route +20 min · last fix heading to Brighton +20 min
  • Wed 2 Sept Max en route +18 min · last fix heading to Brighton +16 min
  • Tue 1 Sept Max en route +20 min · last fix heading to Brighton +16 min

Distribution · 90 days

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

  • Early 10% · 6
  • On time 32% · 19
  • 3–10 min 47% · 28
  • 10–30 min 8% · 5
  • 30+ min 2% · 1

On-time by weekday

  • 55% M n=11
  • 46% T n=13
  • 36% W n=11
  • 50% T n=12
  • 25% F n=12
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 59 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:29on time +2 min
17:00 / 17:01≈ +1 min ≈ +5 min
17:11 / 17:13≈ +2 min ≈ +7 min
17:18≈ +2 min ≈ +8 min
17:22≈ +2 min ≈ +8 min
17:29≈ +3 min ≈ +9 min
17:35+3 min +10 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 11 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 20 NovBrighton 17:34−1 min+2 min
Thu 19 NovBrighton 17:39+5 min+6 min
Wed 18 NovBrighton 17:44+6 min+7 min
Tue 17 NovBrighton 17:39+3 min+5 min
Fri 13 NovPreston Park 17:34Partial coverage0 min+4 min
Thu 12 NovBrighton 17:34+3 min+6 min
Tue 10 NovBrighton 17:34+2 min+3 min
Mon 9 NovBrighton 17:43+7 min+7 min
Fri 6 NovBrighton 17:34+3 min+4 min
Thu 5 NovBrighton 20:20+5 min+5 min
Wed 4 NovBrighton 17:34+2 min+3 min
Tue 3 NovBrighton 17:34−2 min—
Mon 2 NovBrighton 17:38+2 min+4 min
Fri 30 OctBrighton 17:49+5 min+8 min
Thu 29 OctBrighton 17:43−1 min+2 min
Tue 27 OctBrighton 17:51+7 min+10 min
Mon 26 OctBrighton 17:42−2 min+2 min
Thu 22 OctBrighton 17:48+4 min+6 min
Wed 21 OctBrighton 17:43−1 min+1 min
Tue 20 OctBrighton 17:47+2 min+4 min
Mon 19 OctBrighton 17:48+4 min+6 min
Fri 16 OctBrighton 18:04+20 min+22 min
Thu 15 OctBrighton 17:440 min+4 min
Wed 14 OctBrighton 17:48+3 min+6 min
Tue 13 OctBrighton 17:440 min+3 min
Mon 12 OctBrighton 17:43−2 min+1 min
Fri 9 OctBrighton 17:51+7 min+10 min
Thu 8 OctBrighton 17:45+1 min+4 min
Wed 7 OctBrighton 17:46+2 min+5 min
Tue 6 OctBrighton 17:47+3 min+6 min