K80 19723 Lille Flandres → Courtrai

View line K80

Lille Flandres 15:09 → Courtrai 15:45 Sat, Sun 0 h 36 min · 5 stops SNCF

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 15:09 from Lille Flandres · Sat 21 Nov

Next departure 15:09 today · Lille Flandres
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 14 full · 0 partial · 0 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: +1 min

Last 30 days

Arrival delay at Courtrai, in minutes. One bar per run.

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

Worst days

  • Sat 7 Nov Max en route +5 min · last fix heading to Courtrai +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • 100% W n=1
  • — T n=0
  • — F n=0
  • 83% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 14 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
15:09on time on time
15:18 / 15:19≈ on time ≈ on time
15:23 / 15:24≈ on time ≈ on time
15:29 / 15:36≈ on time ≈ on time
15:45on 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
Sun 15 NovCourtrai 15:440 min—
Sat 14 NovCourtrai 15:450 min—
Wed 11 NovCourtrai 15:440 min—
Sun 8 NovCourtrai 15:440 min—
Sat 7 NovCourtrai 15:49+5 min+5 min
Sun 1 NovCourtrai 15:460 min—
Sat 31 OctCourtrai 15:470 min—
Sun 25 OctCourtrai 15:460 min—
Sat 24 OctCourtrai 15:460 min+5 min
Sun 18 OctCourtrai 15:460 min—
Sat 17 OctCourtrai 15:460 min—
Sun 11 OctCourtrai 15:460 min—
Sat 10 OctCourtrai 15:470 min—
Sun 4 OctStopPoint:OCETrain TE~a783e42f 15:460 min—