K5 872739 Toulouse Matabiau – Pau

View line K5

Toulouse Matabiau 19:31 → Pau 22:02 Daily 2 h 31 min · 13 stops SNCF

Running now · updated 21:37

Position estimated from the timetable

Between Tarbes and Lourdes +5 min

Estimated arrival at Pau 22:07 22:02 · 64 km/h

  1. Toulouse Matabiau19:31
  2. Muret19:46
  3. Saint-Gaudens20:25
  4. Lannemezan20:48
  5. Tarbes21:16
  6. Lourdes21:32
  7. Pau22:02

Today it is running worse than usual: typical arrival delay is 0 min; 59% of the last 29 runs arrived on time.

On-time · 30 days
59%
17/29 runs under 3 min
RT coverage: 28 full · 1 partial · 1 no data
On-time · 90 days
62%
45/73 runs under 3 min
RT coverage: 72 full · 1 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+44min
9 in 10 runs arrive with less than this
30 days: +40 min

Last 30 days

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

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

Worst days

  • Mon 2 Nov Max en route +110 min · last fix heading to Pau +110 min
  • Tue 27 Oct Max en route +90 min · last fix heading to Pau +90 min
  • Mon 31 Aug Max en route +70 min · last fix heading to StopPoint:OCETrain TER-8767117 +70 min
  • Tue 3 Nov Max en route +60 min · last fix heading to Pau +60 min
  • Wed 9 Sept Max en route +50 min · last fix heading to StopPoint:OCETrain TER-8767100 +50 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 62% · 45
  • 3–10 min 12% · 9
  • 10–30 min 10% · 7
  • 30+ min 16% · 12

On-time by weekday

  • 64% M n=11
  • 42% T n=12
  • 69% W n=13
  • 73% T n=11
  • 67% F n=12
  • 71% S n=7
  • 43% S n=7

Stops and timetable

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

Last 90 days, 73 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 10Today
19:31on time +10 minPassed
19:35 / 19:37≈ on time ≈ +11 minPassed
19:46 / 19:47≈ on time ≈ +13 minPassed
20:11 / 20:12≈ on time ≈ +21 minPassed
20:25 / 20:26≈ on time ≈ +22 minPassed
20:36 / 20:37≈ on time ≈ +22 minPassed
20:48 / 20:49≈ on time ≈ +26 minPassed
20:54 / 20:55≈ on time ≈ +27 minPassed
21:04 / 21:05≈ on time ≈ +31 minPassed
21:16 / 21:18≈ on time ≈ +33 minPassed
21:32 / 21:34≈ on time ≈ +36 minNext
21:49 / 21:50≈ on time ≈ +41 min
22:02on time +45 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
Sun 15 NovLourdes 21:34Partial coverage+5 min+5 min
Sat 14 NovPau 22:030 min—
Fri 13 NovPau 22:040 min—
Thu 12 NovPau 22:040 min—
Wed 11 NovPau 22:030 min—
Tue 10 NovPau 22:09+5 min+5 min
Mon 9 NovPau 22:040 min—
Sun 8 NovPau 22:08+5 min+5 min
Sat 7 NovPau 22:030 min—
Fri 6 NovPau 22:040 min—
Thu 5 NovPau 22:04No data—
Wed 4 NovPau 22:19+15 min+15 min
Tue 3 NovPau 23:07+60 min+60 min
Mon 2 NovPau 23:54+110 min+110 min
Sun 1 NovPau 22:030 min—
Sat 31 OctPau 22:24+20 min+20 min
Fri 30 OctPau 22:060 min—
Thu 29 OctPau 22:060 min—
Wed 28 OctPau 22:060 min—
Tue 27 OctPau 23:36+90 min+90 min
Mon 26 OctPau 22:070 min—
Sun 25 OctPau 22:28+25 min+25 min
Sat 24 OctPau 22:040 min—
Fri 23 OctPau 22:32+25 min+25 min
Thu 22 OctPau 22:060 min+10 min
Wed 21 OctPau 22:41+35 min+35 min
Tue 20 OctPau 22:060 min—
Mon 19 OctPau 22:060 min—
Sun 18 OctPau 22:030 min—
Sat 17 OctPau 22:38+35 min+40 min