MD 12694 Ourense – Lugo

View line MD

Ourense 12:32 → Lugo 14:12 Daily 1 h 40 min · 4 stops RENFE

It has not run yet today

Last recorded run: Thursday 5 November −3 min

Next service: today 12:32 from Ourense · Fri 6 Nov

Next departure 12:32 today · Ourense
On-time · 30 days
46%
13/28 runs under 3 min
RT coverage: 27 full · 1 partial · 0 no data
On-time · 90 days
45%
40/88 runs under 3 min
RT coverage: 86 full · 2 partial · 0 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +3 min
P90
+12min
9 in 10 runs arrive with less than this
30 days: +13 min

Last 30 days

Arrival delay at Lugo, 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 30 Oct Max en route +68 min · last fix heading to Monforte de Lemos +67 min
  • Thu 1 Oct Max en route +35 min · last fix heading to Lugo +33 min
  • Thu 15 Oct Max en route +30 min · last fix heading to Lugo +23 min
  • Fri 21 Aug Max en route +28 min · last fix heading to Lugo +22 min
  • Mon 17 Aug Max en route +22 min · last fix heading to Lugo +22 min

Distribution · 90 days

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

  • Early 14% · 12
  • On time 32% · 28
  • 3–10 min 40% · 35
  • 10–30 min 13% · 11
  • 30+ min 2% · 2

On-time by weekday

  • 38% M n=13
  • 46% T n=13
  • 31% W n=13
  • 42% T n=12
  • 50% F n=12
  • 42% S n=12
  • 69% S n=13

Stops and timetable

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

Last 90 days, 88 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:32+5 min +12 min
13:18 / 13:19≈ +4 min ≈ +12 min
13:47≈ +4 min ≈ +12 min
14:12+3 min +12 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.

Delay compensation

Other days eligible for compensation

Unofficial notice: TrainsRadar is not the operator. We measure the delay from open data and it may differ from the official one; the operator decides. Only the delay at your final destination counts, and there are exceptions: extraordinary circumstances, tickets under €4 and, in some countries, suburban and regional trains.

Recent runs

DateLast stopFinalMax
Thu 5 NovLugo 14:09−3 min+4 min
Wed 4 NovLugo 14:19+9 min+12 min
Tue 3 NovLugo 14:04−4 min—
Mon 2 NovLugo 14:09+3 min+4 min
Sun 1 NovLugo 14:11−1 min+3 min
Sat 31 OctLugo 14:17+6 min+12 min
Fri 30 OctMonforte de Lemos 14:25Partial coverage+67 min+68 min
Wed 28 OctLugo 14:21+9 min+11 min
Tue 27 OctLugo 14:130 min+7 min
Mon 26 OctLugo 14:16+5 min+5 min
Sun 25 OctLugo 14:04−3 min+1 min
Sat 24 OctLugo 14:07−3 min—
Fri 23 OctLugo 14:07−4 min+4 min
Thu 22 OctLugo 14:14+4 min+8 min
Wed 21 OctLugo 14:07−4 min—
Tue 20 OctLugo 14:17+5 min+6 min
Mon 19 OctLugo 14:08−3 min—
Sun 18 OctLugo 14:13−2 min+1 min
Sat 17 OctLugo 14:18+6 min+7 min
Fri 16 OctLugo 14:14+3 min+10 min
Thu 15 OctLugo 14:34+23 min+30 min
Wed 14 OctLugo 14:26+14 min+16 min
Tue 13 OctLugo 14:16+5 min+8 min
Mon 12 OctLugo 14:16+5 min+13 min
Sun 11 OctLugo 14:13+1 min+4 min
Sat 10 OctLugo 14:07−3 min—
Fri 9 OctLugo 14:23+12 min+16 min
Thu 8 OctLugo 14:110 min+9 min
Wed 7 OctLugo 14:17+4 min+4 min
Tue 6 OctLugo 14:14+3 min+4 min