K50 842423 Lille Flandres – Béthune

View line K50

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

✓ Today’s run finished

Today it reached Béthune at 17:20 +5 min

  1. Lille Flandres16:36
  2. Lille Centre Hospitalier Régional16:44
  3. La Bassée17:03
  4. Béthune17:15

Next service: tomorrow 16:36 from Lille Flandres · Fri 13 Nov

Next departure 16:36 tomorrow · Lille Flandres
On-time · 30 days
80%
16/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
88%
50/57 runs under 3 min
RT coverage: 57 full · 0 partial · 0 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

  • Tue 27 Oct Max en route +20 min · last fix heading to Béthune +20 min
  • Thu 24 Sept Max en route +10 min · last fix heading to StopPoint:OCETrain TER-8734200 +10 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Béthune +5 min
  • Tue 10 Nov Max en route +5 min · last fix heading to Béthune +5 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Béthune +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 50
  • 3–10 min 9% · 5
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 83% T n=12
  • 82% W n=11
  • 83% T n=12
  • 90% F n=10
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 57 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:36on time on time
16:44 / 16:46≈ on time ≈ +1 min
17:03 / 17:04≈ on time ≈ +3 min
17:15on 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 12 NovBéthune 17:19+5 min+5 min
Tue 10 NovBéthune 17:19+5 min+5 min
Mon 9 NovBéthune 17:140 min—
Fri 6 NovBéthune 17:140 min—
Thu 5 NovBéthune 17:140 min—
Wed 4 NovBéthune 17:19+5 min+5 min
Tue 3 NovBéthune 17:150 min—
Mon 2 NovBéthune 17:140 min—
Fri 30 OctBéthune 17:160 min—
Thu 29 OctBéthune 17:160 min—
Wed 28 OctBéthune 17:160 min—
Tue 27 OctBéthune 17:36+20 min+20 min
Mon 26 OctBéthune 17:170 min—
Thu 22 OctBéthune 17:170 min—
Wed 21 OctBéthune 17:160 min—
Tue 20 OctBéthune 17:160 min—
Mon 19 OctBéthune 17:170 min—
Fri 16 OctBéthune 17:160 min—
Thu 15 OctBéthune 17:160 min—
Wed 14 OctBéthune 17:160 min—
Tue 13 OctBéthune 17:160 min—
Mon 12 OctBéthune 17:160 min—
Fri 9 OctBéthune 17:160 min—
Thu 8 OctBéthune 17:160 min—
Wed 7 OctBéthune 17:160 min—
Tue 6 OctBéthune 17:160 min—
Mon 5 OctBéthune 17:160 min—
Fri 2 OctStopPoint:OCETrain TER-8734200 17:140 min+5 min
Thu 1 OctStopPoint:OCETrain TER-8734200 17:150 min+20 min
Wed 30 SeptStopPoint:OCETrain TER-8734200 17:140 min—