C2 29541 Bilbao-Intermod. Abando Indalecio Prieto – Muskiz

View line C2

Bilbao-Intermod. Abando Indalecio Prieto 15:03 → Muskiz 15:40 Sat, Sun 0 h 37 min · 18 stops RENFE

✓ Today’s run finished

Today it reached Muskiz at 15:45 +5 min

  1. Bilbao-Intermod. Abando Indalecio Prieto15:03
  2. Autonomía15:07
  3. Zorrotza15:11
  4. Galindo15:21
  5. Valle de Trápaga/Trapagaran15:24
  6. Ortuella15:30
  7. Muskiz15:40

Next service: tomorrow 15:03 from Bilbao-Intermod. Abando Indalecio Prieto · Sun 8 Nov

Next departure 15:03 tomorrow · Bilbao-Intermod. Abando Indalecio Prieto
On-time · 30 days
30%
3/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
On-time · 90 days
31%
8/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +3 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

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

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

Worst days

  • Sun 16 Aug Max en route +17 min · last fix heading to Muskiz +13 min
  • Sat 29 Aug Max en route +10 min · last fix heading to Muskiz +10 min
  • Sun 18 Oct Max en route +7 min · last fix heading to Muskiz +7 min
  • Sat 26 Sept Max en route +7 min · last fix heading to Muskiz +7 min
  • Sat 7 Nov Max en route +5 min · last fix heading to Muskiz +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 31% · 8
  • 3–10 min 62% · 16
  • 10–30 min 8% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 23% S n=13
  • 33% S n=12

Stops and timetable

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

Last 90 days, 26 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
15:03on time on time
15:04≈ on time ≈ on time
15:06≈ on time ≈ +1 min
15:07≈ on time ≈ +1 min
15:08≈ on time ≈ +1 min
15:09≈ on time ≈ +1 min
15:11≈ +1 min ≈ +2 min
15:13≈ +1 min ≈ +2 min
15:17≈ +1 min ≈ +3 min
15:21≈ +1 min ≈ +3 min
15:22≈ +2 min ≈ +4 min
15:24≈ +2 min ≈ +4 min
15:26≈ +2 min ≈ +4 min
15:28≈ +2 min ≈ +5 min
15:30 / 15:33≈ +2 min ≈ +5 min
15:34≈ +3 min ≈ +6 min
15:37≈ +3 min ≈ +6 min
15:40+3 min +7 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
Sat 7 NovMuskiz 15:49+5 min+5 min
Sun 1 NovMuskiz 15:45+4 min+4 min
Sat 31 OctMuskiz 15:44+3 min+3 min
Sun 25 OctMuskiz 15:44+4 min+4 min
Sat 24 OctMuskiz 15:43+2 min+3 min
Sun 18 OctMuskiz 15:48+7 min+7 min
Sat 17 OctMuskiz 15:43+3 min+4 min
Mon 12 OctMuskiz 15:43+2 min+3 min
Sun 11 OctMuskiz 15:43+3 min+3 min
Sat 10 OctMuskiz 15:43+2 min+2 min
Sun 4 OctMuskiz 15:430 min+3 min
Sat 3 OctMuskiz 15:46+1 min+5 min
Sun 27 SeptMuskiz 15:45+5 min+5 min
Sat 26 SeptMuskiz 15:47+7 min+7 min
Sun 20 SeptMuskiz 15:43+3 min+4 min
Sat 19 SeptMuskiz 15:44+4 min+4 min
Sun 13 SeptMuskiz 15:43+3 min+4 min
Sat 12 SeptMuskiz 15:45+4 min+5 min
Sun 6 SeptMuskiz 15:43+2 min+3 min
Sat 5 SeptMuskiz 15:44+3 min+4 min
Sun 30 AugMuskiz 15:42+2 min+3 min
Sat 29 AugMuskiz 15:51+10 min+10 min
Sun 23 AugMuskiz 15:42+2 min+3 min
Sat 22 AugMuskiz 15:44+4 min+4 min
Sun 16 AugMuskiz 15:54+13 min+17 min
Sat 15 AugMuskiz 15:43+3 min+3 min