Os 5080 5080 Pardubice hl. n. – Přelouč

View line Os 5080

Pardubice hl. n. 21:13 → Přelouč 21:26 Mon, Tue, Wed, Thu, Fri, Sun 0 h 13 min · 5 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 21:13 from Pardubice hl. n. · Sun 8 Nov

Next departure 21:13 today · Pardubice hl. n.
On-time · 30 days
—
Too little data (0/24 runs with data)
RT coverage: 0 full · 0 partial · 24 no data
On-time · 90 days
75%
24/32 runs under 3 min
RT coverage: 32 full · 0 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
P90
+4min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Přelouč, in minutes. One bar per run.

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

Worst days

  • Wed 16 Sept Max en route +21 min · last fix heading to — +20 min
  • Mon 17 Aug Max en route +16 min · last fix heading to — +16 min
  • Sun 20 Sept Max en route +6 min · last fix heading to — +6 min
  • Thu 1 Oct Max en route +4 min · last fix heading to — +4 min
  • Tue 29 Sept Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 24
  • 3–10 min 19% · 6
  • 10–30 min 6% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 60% M n=5
  • 67% T n=6
  • 83% W n=6
  • 80% T n=5
  • 80% F n=5
  • — S n=0
  • 80% S n=5

Stops and timetable

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

Last 90 days, 32 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
21:13on time +5 min
21:15≈ on time ≈ +5 min
21:18≈ on time ≈ +5 min
21:22≈ on time ≈ +4 min
21:26on time +4 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
Fri 6 NovPřelouč 21:27No data—
Thu 5 NovPřelouč 21:27No data—
Wed 4 NovPřelouč 21:27No data—
Tue 3 NovPřelouč 21:27No data—
Mon 2 NovPřelouč 21:28No data—
Sun 1 NovPřelouč 21:27No data—
Fri 30 OctPřelouč 21:27No data—
Thu 29 OctPřelouč 21:27No data—
Wed 28 OctPřelouč 21:27No data—
Tue 27 OctPřelouč 21:28No data—
Mon 26 OctPřelouč 21:27No data—
Sun 25 OctPřelouč 21:27No data—
Fri 23 OctPřelouč 21:27No data—
Thu 22 OctPřelouč 21:27No data—
Wed 21 OctPřelouč 21:27No data—
Tue 20 OctPřelouč 21:27No data—
Mon 19 OctPřelouč 21:28No data—
Sun 18 OctPřelouč 21:27No data—
Fri 16 OctPřelouč 21:27No data—
Thu 15 OctPřelouč 21:27No data—
Wed 14 OctPřelouč 21:27No data—
Tue 13 OctPřelouč 21:28No data—
Mon 12 OctPřelouč 21:28No data—
Sun 11 OctPřelouč 21:27No data—
Fri 9 OctPřelouč 21:27No data—
Thu 8 OctPřelouč 21:27No data—
Wed 7 OctPřelouč 21:27No data—
Tue 6 OctPřelouč 21:27No data—
Mon 5 OctPřelouč 21:27No data—
Sun 4 Oct— 21:400 min—