K50 842419 Lille Flandres – Béthune

View line K50

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

It does not run today

Last recorded run: Friday 13 November 0 min

Next service: tomorrow 14:06 from Lille Flandres · Mon 16 Nov

Next departure 14:06 tomorrow · Lille Flandres
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 16 full · 1 partial · 2 no data
On-time · 90 days
75%
24/32 runs under 3 min
RT coverage: 30 full · 2 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+30min
9 in 10 runs arrive with less than this
30 days: +12 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

  • Fri 23 Oct Max en route +60 min · last fix heading to Lille Flandres +60 min
  • Thu 15 Oct Max en route +70 min · last fix heading to Béthune +50 min
  • Mon 26 Oct Max en route +30 min · last fix heading to Béthune +30 min
  • Tue 6 Oct Max en route +30 min · last fix heading to Lille Centre Hospitalier Régional +30 min
  • Thu 8 Oct Max en route +25 min · last fix heading to Béthune +25 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 24
  • 3–10 min 9% · 3
  • 10–30 min 3% · 1
  • 30+ min 13% · 4

On-time by weekday

  • 80% M n=5
  • 75% T n=8
  • 86% W n=7
  • 67% T n=6
  • 67% 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, 32 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
14:06on time +29 min
14:14 / 14:16≈ on time ≈ +6 min
14:31 / 14:32≈ on time ≈ +5 min
14:42on time +7 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 13 NovBéthune 14:430 min—
Thu 12 NovBéthune 14:440 min—
Tue 10 NovBéthune 14:430 min—
Mon 9 NovBéthune 14:430 min—
Fri 6 NovBéthune 14:43No data—
Thu 5 NovBéthune 14:44No data—
Wed 4 NovBéthune 14:430 min—
Tue 3 NovBéthune 14:430 min—
Mon 2 NovBéthune 14:430 min—
Fri 30 OctBéthune 14:430 min—
Thu 29 OctBéthune 14:430 min—
Wed 28 OctBéthune 14:430 min—
Tue 27 OctBéthune 14:430 min—
Mon 26 OctBéthune 15:14+30 min+30 min
Fri 23 OctLille Flandres 14:40Partial coverage+60 min+60 min
Thu 22 OctBéthune 14:430 min—
Wed 21 OctBéthune 14:430 min—
Tue 20 OctBéthune 14:430 min—
Mon 19 OctBéthune 14:440 min—
Fri 16 OctBéthune 14:430 min—
Thu 15 OctBéthune 15:33+50 min+70 min
Wed 14 OctBéthune 14:430 min—
Tue 13 OctBéthune 14:48+5 min+5 min
Fri 9 OctBéthune 14:48+5 min+5 min
Thu 8 OctBéthune 15:08+25 min+25 min
Wed 7 OctBéthune 14:430 min—
Tue 6 OctLille Centre Hospitalier Régional 14:37Partial coverage+30 min+30 min
Mon 5 OctBéthune 14:440 min—
Fri 25 SeptStopPoint:OCETrain TER-8734200 14:410 min—
Thu 10 SeptStopPoint:OCETrain TER-8734200 14:410 min+15 min