AV-MD 9131 A Coruña – Ourense

View line AV-MD

A Coruña 13:35 → Ourense 14:48 Mon, Tue, Wed, Thu, Fri 1 h 13 min · 3 stops RENFE

✓ Today’s run finished

Today it reached Ourense at 14:48 −2 min

  1. A Coruña13:35
  2. Santiago de Compostela-Daniel Castelao14:04
  3. Ourense14:48

Next service: tomorrow 13:35 from A Coruña · Fri 13 Nov

Next departure 13:35 tomorrow · A Coruña
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 0 no data
On-time · 90 days
98%
57/58 runs under 3 min
RT coverage: 58 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Ourense, 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 20 Aug Max en route +6 min · last fix heading to Ourense +6 min

Distribution · 90 days

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

  • Early 26% · 15
  • On time 72% · 42
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=12
  • 100% W n=12
  • 92% T n=12
  • 100% F n=11
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 58 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
13:35+1 min +2 min
14:04 / 14:08≈ on time ≈ +1 min
14:481 min early 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
Thu 12 NovOurense 14:43−2 min+2 min
Wed 4 NovOurense 18:590 min+3 min
Tue 3 NovOurense 14:490 min+1 min
Mon 2 NovOurense 14:44−1 min—
Fri 30 OctOurense 15:07+2 min+4 min
Thu 29 OctOurense 14:43−2 min+1 min
Wed 28 OctOurense 14:45−1 min+1 min
Tue 27 OctOurense 14:44−1 min+1 min
Mon 26 OctOurense 14:45−1 min+1 min
Fri 23 OctOurense 14:45−1 min+1 min
Thu 22 OctOurense 14:43−2 min—
Wed 21 OctOurense 14:450 min+1 min
Tue 20 OctOurense 14:450 min—
Mon 19 OctOurense 14:49−2 min+1 min
Fri 16 OctOurense 14:50−1 min+1 min
Thu 15 OctOurense 14:47−1 min+1 min
Wed 14 OctOurense 15:11−2 min+1 min
Tue 13 OctOurense 14:47−1 min+1 min
Fri 9 OctOurense 14:45−1 min+1 min
Thu 8 OctOurense 14:460 min+1 min
Wed 7 OctOurense 14:450 min+1 min
Tue 6 OctOurense 15:030 min—
Mon 5 OctOurense 14:480 min+1 min
Fri 2 OctOurense 14:520 min+1 min
Thu 1 OctOurense 14:44−2 min—
Wed 30 SeptOurense 14:47−1 min—
Tue 29 SeptOurense 14:45−2 min—
Mon 28 Sept— 15:03−1 min+1 min
Fri 25 SeptOurense 14:460 min+2 min
Thu 24 SeptOurense 15:21−2 min+1 min