Os 6233 6233 Hradec Král. hl. n. – Pardubice centrum

View line Os 6233

Hradec Král. hl. n. 09:05 → Pardubice centrum 09:32 Daily 0 h 27 min · 10 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Pardubice centrum at 09:33 No data

  1. Hradec Král. hl. n.09:05
  2. Opatovice nad Labem09:10
  3. Čeperka09:13
  4. Stéblová obec09:17
  5. Pardubice-Semtín09:21
  6. Pardubice hl. n.09:28
  7. Pardubice centrum09:32

Next service: tomorrow 09:05 from Hradec Král. hl. n. · Fri 6 Nov

Next departure 09:05 tomorrow · Hradec Král. hl. n.
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
98%
58/59 runs under 3 min
RT coverage: 59 full · 0 partial · 31 no data
Typical delay
−2min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Pardubice centrum, 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 25 Sept Max en route +7 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 51% · 30
  • On time 47% · 28
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=8
  • 100% W n=8
  • 100% T n=8
  • 88% F n=8
  • 100% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 59 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
09:05on time +3 min
09:09≈ on time ≈ +2 min
09:10≈ on time ≈ +2 min
09:13≈ on time ≈ +2 min
09:16≈ on time ≈ +2 min
09:17≈ on time ≈ +2 min
09:21≈ 1 min early ≈ +1 min
09:23 / 09:25≈ 1 min early ≈ +1 min
09:28 / 09:30≈ 1 min early ≈ on time
09:322 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 5 NovPardubice centrum 09:33No data—
Wed 4 NovPardubice centrum 09:33No data—
Tue 3 NovPardubice centrum 09:33No data—
Mon 2 NovPardubice centrum 09:33No data—
Sun 1 NovPardubice centrum 09:33No data—
Sat 31 OctPardubice centrum 09:33No data—
Fri 30 OctPardubice centrum 09:33No data—
Thu 29 OctPardubice centrum 09:33No data—
Wed 28 OctPardubice centrum 09:33No data—
Tue 27 OctPardubice centrum 09:33No data—
Mon 26 OctPardubice centrum 09:33No data—
Sun 25 OctPardubice centrum 09:33No data—
Sat 24 OctPardubice centrum 09:33No data—
Fri 23 OctPardubice centrum 09:34No data—
Thu 22 OctPardubice centrum 09:34No data—
Wed 21 OctPardubice centrum 09:33No data—
Tue 20 OctPardubice centrum 09:33No data—
Mon 19 OctPardubice centrum 09:33No data—
Sun 18 OctPardubice centrum 09:33No data—
Sat 17 OctPardubice centrum 09:33No data—
Fri 16 OctPardubice centrum 09:33No data—
Thu 15 OctPardubice centrum 09:33No data—
Wed 14 OctPardubice centrum 09:33No data—
Tue 13 OctPardubice centrum 09:33No data—
Mon 12 OctPardubice centrum 09:33No data—
Sun 11 OctPardubice centrum 09:33No data—
Sat 10 OctPardubice centrum 09:33No data—
Fri 9 OctPardubice centrum 09:33No data—
Thu 8 OctPardubice centrum 09:33No data—
Wed 7 OctPardubice centrum 09:33No data—