K50 842437 Lille Flandres – Béthune

View line K50

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

It does not run today

Last recorded run: Tuesday 10 November 0 min

Next service: tomorrow 20:06 from Lille Flandres · Thu 12 Nov

Next departure 20:06 tomorrow · Lille Flandres
On-time · 30 days
63%
10/16 runs under 3 min
RT coverage: 15 full · 1 partial · 1 no data
On-time · 90 days
75%
21/28 runs under 3 min
RT coverage: 27 full · 1 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

  • Thu 29 Oct Max en route +45 min · last fix heading to Lille Flandres +45 min
  • Tue 25 Aug Max en route +30 min · last fix heading to StopPoint:OCETrain TER-8734243 +25 min
  • Tue 3 Nov Max en route +5 min · last fix heading to Béthune +5 min
  • Thu 22 Oct Max en route +5 min · last fix heading to Béthune +5 min
  • Wed 21 Oct Max en route +5 min · last fix heading to Béthune +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 21
  • 3–10 min 18% · 5
  • 10–30 min 4% · 1
  • 30+ min 4% · 1

On-time by weekday

  • 100% M n=5
  • 67% T n=6
  • 67% W n=6
  • 40% T n=5
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 28 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
20:06on time +7 min
20:14 / 20:16≈ on time ≈ +5 min
20:31 / 20:32≈ on time ≈ +4 min
20: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
Tue 10 NovBéthune 20:430 min—
Mon 9 NovBéthune 20:430 min—
Fri 6 NovBéthune 20:430 min—
Thu 5 NovBéthune 20:44No data—
Wed 4 NovBéthune 20:430 min—
Tue 3 NovBéthune 20:49+5 min+5 min
Mon 2 NovBéthune 20:430 min—
Fri 30 OctBéthune 20:430 min—
Thu 29 OctLille Flandres 20:14Partial coverage+45 min+45 min
Wed 28 OctBéthune 20:430 min—
Thu 22 OctBéthune 20:48+5 min+5 min
Wed 21 OctBéthune 20:48+5 min+5 min
Tue 20 OctBéthune 20:430 min—
Mon 19 OctBéthune 20:430 min—
Fri 16 OctBéthune 20:430 min—
Thu 15 OctBéthune 20:49+5 min+5 min
Wed 14 OctBéthune 20:48+5 min+5 min
Mon 12 OctBéthune 20:430 min—
Fri 9 OctBéthune 20:430 min—
Thu 8 OctBéthune 20:430 min—
Wed 7 OctBéthune 20:430 min—
Tue 6 OctBéthune 20:430 min—
Mon 5 OctBéthune 20:430 min—
Fri 25 SeptStopPoint:OCETrain TER-8734200 20:410 min+90 min
Thu 10 SeptStopPoint:OCETrain TER-8734200 20:420 min+50 min
Wed 2 SeptStopPoint:OCETrain TER-8734200 20:420 min+10 min
Tue 1 SeptStopPoint:OCETrain TER-8734200 20:410 min+5 min
Fri 28 AugStopPoint:OCETrain TER-8734200 20:410 min+80 min
Tue 25 AugStopPoint:OCETrain TER-8734243 20:42+25 min+30 min