K80 19715 Lille Flandres → Courtrai

View line K80

Lille Flandres 12:09 → Courtrai 12:45 Mon, Tue, Wed, Thu, Fri 0 h 36 min · 5 stops SNCF

TER 19715 Lille Flandres–Courtrai: final delay under 3 min on 8 of its 9 runs with data in the last 30 days (89%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 10:28 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 12:09 from Lille Flandres · Mon 23 Nov

Next departure 12:09 tomorrow · 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
95%
39/41 runs under 3 min
RT coverage: 40 full · 1 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: +2 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

  • Fri 28 Aug Max en route +40 min · last fix heading to StopPoint:OCETrain TER-8728600 +40 min
  • Thu 12 Nov Max en route +10 min · last fix heading to Courtrai +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 39
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=8
  • 100% T n=9
  • 100% W n=8
  • 88% T n=8
  • 88% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 41 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
12:09on time on time
12:18 / 12:19≈ on time ≈ on time
12:23 / 12:24≈ on time ≈ on time
12:29 / 12:36≈ on time ≈ on time
12: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 12:470 min—
Thu 19 NovCourtrai 12:440 min—
Wed 18 NovCourtrai 12:440 min—
Tue 17 NovCourtrai 12:440 min—
Mon 16 NovCourtrai 12:440 min—
Fri 13 NovCourtrai 12:440 min—
Thu 12 NovCourtrai 12:54+10 min+10 min
Tue 10 NovCourtrai 12:440 min—
Mon 9 NovCourtrai 12:440 min—
Fri 23 OctCourtrai 12:460 min—
Thu 22 OctCourtrai 12:460 min—
Wed 21 OctCourtrai 12:460 min—
Tue 20 OctCourtrai 12:470 min—
Mon 19 OctCourtrai 12:460 min—
Fri 16 OctCourtrai 12:460 min—
Thu 15 OctCourtrai 12:460 min—
Wed 14 OctCourtrai 12:460 min—
Tue 13 OctCourtrai 12:460 min—
Mon 12 OctCourtrai 12:460 min—
Fri 9 OctCourtrai 12:460 min—
Thu 8 OctCourtrai 12:460 min—
Wed 7 OctCourtrai 12:460 min—
Tue 6 OctCourtrai 12:460 min—
Mon 5 OctStopPoint:OCETrain TE~a783e42f 12:46Partial coverage0 min—
Wed 30 SeptStopPoint:OCETrain TER-8896008 12:450 min—
Tue 29 SeptStopPoint:OCETrain TER-8896008 12:440 min—
Mon 28 SeptStopPoint:OCETrain TER-8896008 12:440 min—
Fri 11 SeptStopPoint:OCETrain TER-8896008 12:440 min—
Thu 10 SeptStopPoint:OCETrain TER-8896008 12:440 min—
Wed 9 SeptStopPoint:OCETrain TER-8896008 12:440 min—