K80 19713 Lille Flandres → Courtrai

View line K80

Lille Flandres 11:09 → Courtrai 11:45 Daily 0 h 36 min · 5 stops SNCF

It has not run yet today

Last recorded run: Friday 20 November 0 min

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

Next departure 11:09 today · Lille Flandres
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
97%
36/37 runs under 3 min
RT coverage: 37 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: 0 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

  • Thu 12 Nov Max en route +10 min · last fix heading to Courtrai +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 36
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=5
  • 80% T n=5
  • 100% F n=5
  • 100% 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, 37 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
11:09on time on time
11:18 / 11:19≈ on time ≈ on time
11:23 / 11:24≈ on time ≈ on time
11:29 / 11:36≈ on time ≈ on time
11: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
Fri 20 NovCourtrai 11:450 min—
Thu 19 NovCourtrai 11:440 min—
Wed 18 NovCourtrai 11:440 min—
Tue 17 NovCourtrai 11:440 min—
Mon 16 NovCourtrai 11:440 min—
Sun 15 NovCourtrai 11:470 min—
Sat 14 NovCourtrai 11:440 min—
Fri 13 NovCourtrai 11:440 min—
Thu 12 NovCourtrai 11:49+5 min+10 min
Wed 11 NovCourtrai 11:440 min—
Tue 10 NovCourtrai 11:440 min—
Mon 9 NovCourtrai 11:440 min—
Sun 8 NovCourtrai 11:440 min—
Sat 7 NovCourtrai 11:440 min—
Sun 1 NovCourtrai 11:460 min—
Sat 31 OctCourtrai 11:470 min—
Sun 25 OctCourtrai 11:460 min—
Sat 24 OctCourtrai 11:460 min—
Fri 23 OctCourtrai 11:460 min—
Thu 22 OctCourtrai 11:460 min—
Wed 21 OctCourtrai 11:460 min—
Tue 20 OctCourtrai 11:460 min—
Mon 19 OctCourtrai 11:470 min—
Sun 18 OctCourtrai 11:460 min—
Sat 17 OctCourtrai 11:460 min—
Fri 16 OctCourtrai 11:460 min—
Thu 15 OctCourtrai 11:460 min—
Wed 14 OctCourtrai 11:460 min—
Tue 13 OctCourtrai 11:460 min—
Sun 11 OctCourtrai 11:460 min—