C5 71581 Karrantza – Aranguren

View line C5

Karrantza 06:35 → Aranguren 07:18 Mon, Tue, Wed, Thu, Fri 0 h 43 min · 6 stops RENFE

✓ Today’s run finished

Today it reached Aranguren at 07:18 −4 min

  1. Karrantza06:35
  2. Villaverde de Trucios06:51
  3. Artzentales06:58
  4. Traslaviña07:01
  5. Mimetiz07:13
  6. Aranguren07:18

Next service: tomorrow 06:35 from Karrantza · Fri 6 Nov

Next departure 06:35 tomorrow · Karrantza
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
88%
51/58 runs under 3 min
RT coverage: 58 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

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

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

Worst days

  • Tue 6 Oct Max en route +25 min · last fix heading to Aranguren +22 min
  • Fri 9 Oct Max en route +17 min · last fix heading to Mimetiz +13 min
  • Fri 18 Sept Max en route +13 min · last fix heading to Aranguren +12 min
  • Thu 17 Sept Max en route +8 min · last fix heading to Aranguren +8 min
  • Mon 5 Oct Max en route +5 min · last fix heading to Aranguren +5 min

Distribution · 90 days

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

  • Early 12% · 7
  • On time 76% · 44
  • 3–10 min 7% · 4
  • 10–30 min 5% · 3
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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
06:35on time on time
06:51≈ on time ≈ +1 min
06:58≈ on time ≈ +2 min
07:01≈ on time ≈ +2 min
07:13≈ on time ≈ +3 min
07:18on time +3 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
Thu 5 NovAranguren 07:18−4 min+1 min
Wed 4 NovAranguren 07:18+1 min+1 min
Tue 3 NovMimetiz 07:14+1 min+1 min
Mon 2 NovAranguren 07:19−2 min+2 min
Fri 30 OctMimetiz 07:160 min+1 min
Wed 28 OctMimetiz 07:160 min—
Tue 27 OctAranguren 07:29No data—
Mon 26 OctAranguren 07:18−2 min+1 min
Fri 23 OctMimetiz 07:17−4 min+1 min
Thu 22 OctMimetiz 07:22−1 min+5 min
Wed 21 OctMimetiz 07:17−4 min+2 min
Tue 20 OctMimetiz 07:160 min—
Mon 19 OctAranguren 07:24+1 min+5 min
Fri 16 OctMimetiz 07:18−3 min+1 min
Thu 15 OctMimetiz 07:160 min+1 min
Wed 14 OctMimetiz 07:160 min+1 min
Tue 13 OctAranguren 07:18−3 min+1 min
Fri 9 OctMimetiz 07:33+13 min+17 min
Thu 8 OctMimetiz 07:160 min—
Wed 7 OctMimetiz 07:22−1 min+3 min
Tue 6 OctAranguren 07:43+22 min+25 min
Mon 5 OctAranguren 07:23+5 min+5 min
Fri 2 OctAranguren 07:21+2 min+4 min
Thu 1 OctAranguren 07:170 min+1 min
Tue 29 SeptMimetiz 07:17+1 min+1 min
Fri 25 SeptAranguren 07:19+1 min+1 min
Thu 24 SeptAranguren 07:180 min+2 min
Wed 23 SeptAranguren 07:20+1 min+3 min
Tue 22 SeptAranguren 07:19+2 min+3 min
Mon 21 SeptAranguren 07:22+3 min+6 min