K50 842425 Lille Flandres – Béthune

View line K50

Lille Flandres 17:06 → Béthune 17:42 Mon, Tue, Wed, Thu, Fri 0 h 36 min · 4 stops SNCF

✓ Today’s run finished

Today, last fix heading to Béthune at 17:43 No data

  1. Lille Flandres17:06
  2. Lille Centre Hospitalier Régional17:14
  3. La Bassée17:31
  4. Béthune17:42

Next service: tomorrow 17:06 from Lille Flandres · Fri 6 Nov

Next departure 17:06 tomorrow · Lille Flandres
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
86%
18/21 runs under 3 min
RT coverage: 21 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Béthune, in minutes. One bar per run.

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

Worst days

  • Wed 7 Oct Max en route +30 min · last fix heading to Béthune +30 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Béthune +5 min
  • Wed 28 Oct Max en route +5 min · last fix heading to Béthune +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 18
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 5% · 1

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 40% W n=5
  • 100% T n=4
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 21 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
17:06on time on time
17:14 / 17:16≈ on time ≈ +1 min
17:31 / 17:32≈ on time ≈ +3 min
17:42on 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 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
Thu 5 NovBéthune 17:43No data—
Wed 4 NovBéthune 17:48+5 min+5 min
Tue 3 NovBéthune 17:440 min—
Mon 2 NovBéthune 17:430 min—
Fri 30 OctBéthune 17:430 min—
Thu 29 OctBéthune 17:430 min—
Wed 28 OctBéthune 17:48+5 min+5 min
Mon 26 OctBéthune 17:440 min—
Thu 22 OctBéthune 17:440 min—
Wed 21 OctBéthune 17:440 min—
Tue 20 OctBéthune 17:430 min—
Mon 19 OctBéthune 17:430 min—
Fri 16 OctBéthune 17:430 min—
Thu 15 OctBéthune 17:430 min—
Wed 14 OctBéthune 17:430 min—
Tue 13 OctBéthune 17:440 min—
Mon 12 OctBéthune 17:430 min—
Fri 9 OctBéthune 17:430 min—
Thu 8 OctBéthune 17:440 min—
Wed 7 OctBéthune 18:13+30 min+30 min
Tue 6 OctBéthune 17:430 min—
Mon 5 OctBéthune 17:430 min—