K50 842426 Béthune – Lille Flandres

View line K50

Béthune 17:19 → Lille Flandres 17:54 Mon, Tue, Wed, Thu, Fri 0 h 35 min · 4 stops SNCF

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 17:19 from Béthune · Fri 13 Nov

Next departure 17:19 today · Béthune
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 16 full · 0 partial · 1 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Lille Flandres, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 24
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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:19on time on time
17:28 / 17:29≈ on time ≈ on time
17:44 / 17:46≈ on time ≈ on time
17:54on time on time

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 NovLille Flandres 17:540 min—
Tue 10 NovLille Flandres 17:540 min—
Mon 9 NovLille Flandres 17:540 min—
Fri 6 NovLille Flandres 17:540 min—
Thu 5 NovLille Flandres 17:54No data—
Wed 4 NovLille Flandres 17:540 min—
Tue 3 NovLille Flandres 17:550 min—
Mon 2 NovLille Flandres 17:540 min—
Fri 30 OctLille Flandres 17:550 min—
Thu 29 OctLille Flandres 17:550 min—
Wed 28 OctLille Flandres 17:550 min—
Thu 22 OctLille Flandres 17:560 min—
Wed 21 OctLille Flandres 17:560 min—
Tue 20 OctLille Flandres 17:550 min—
Mon 19 OctLille Flandres 17:550 min—
Fri 16 OctLille Flandres 17:550 min—
Thu 15 OctLille Flandres 17:550 min—
Wed 14 OctLille Flandres 17:550 min—
Tue 13 OctLille Flandres 17:550 min—
Mon 12 OctLille Flandres 17:550 min—
Fri 9 OctLille Flandres 17:550 min—
Thu 8 OctLille Flandres 17:550 min—
Wed 7 OctLille Flandres 17:550 min—
Tue 6 OctLille Flandres 17:550 min—
Mon 5 OctLille Flandres 17:550 min—