Os 1476 1476 Pardubice centrum – Jaroměř

View line Os 1476

Pardubice centrum 10:05 → Jaroměř 10:58 Daily 0 h 53 min · 16 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Jaroměř at 10:59 No data

  1. Pardubice centrum10:05
  2. Pardubice-Semtín10:14
  3. Stéblová10:17
  4. Opatovice nad Labem-Pohřebačka10:20
  5. Předměřice nad Labem10:39
  6. Černožice10:52
  7. Jaroměř10:58

Next service: tomorrow 10:05 from Pardubice centrum · Sat 7 Nov

Next departure 10:05 tomorrow · Pardubice centrum
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
76%
44/58 runs under 3 min
RT coverage: 58 full · 0 partial · 32 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 Jaroměř, 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 26 Aug Max en route +15 min · last fix heading to — +11 min
  • Wed 2 Sept Max en route +9 min · last fix heading to — +9 min
  • Fri 28 Aug Max en route +9 min · last fix heading to — +8 min
  • Sat 22 Aug Max en route +8 min · last fix heading to — +7 min
  • Mon 24 Aug Max en route +7 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 74% · 43
  • 3–10 min 22% · 13
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=9
  • 75% T n=8
  • 50% W n=8
  • 88% T n=8
  • 88% F n=8
  • 63% S n=8
  • 100% S n=9

Stops and timetable

Timetable of the latest run from the operator’s GTFS (16 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
10:05on time +1 min
10:07 / 10:09≈ on time ≈ +1 min
10:12≈ on time ≈ +1 min
10:14≈ on time ≈ +1 min
10:16≈ on time ≈ +1 min
10:17≈ on time ≈ +1 min
10:18≈ on time ≈ +1 min
10:19≈ on time ≈ +1 min
10:20≈ on time ≈ +1 min
10:25 / 10:35≈ on time ≈ +2 min
10:39 / 10:40≈ on time ≈ +3 min
10:42 / 10:43≈ on time ≈ +3 min
10:46 / 10:50≈ on time ≈ +3 min
10:52 / 10:53≈ on time ≈ +4 min
10:55≈ on time ≈ +4 min
10:58on 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 NovJaroměř 10:59No data—
Thu 5 NovJaroměř 10:59No data—
Wed 4 NovJaroměř 10:59No data—
Tue 3 NovJaroměř 10:59No data—
Mon 2 NovJaroměř 10:59No data—
Sun 1 NovJaroměř 10:59No data—
Sat 31 OctJaroměř 10:59No data—
Fri 30 OctJaroměř 10:59No data—
Thu 29 OctJaroměř 10:59No data—
Wed 28 OctJaroměř 10:59No data—
Tue 27 OctJaroměř 10:59No data—
Mon 26 OctJaroměř 10:59No data—
Sun 25 OctJaroměř 10:59No data—
Sat 24 OctJaroměř 10:59No data—
Fri 23 OctJaroměř 10:59No data—
Thu 22 OctJaroměř 10:59No data—
Wed 21 OctJaroměř 10:59No data—
Tue 20 OctJaroměř 10:59No data—
Mon 19 OctJaroměř 10:59No data—
Sun 18 OctJaroměř 10:59No data—
Sat 17 OctJaroměř 10:59No data—
Fri 16 OctJaroměř 10:59No data—
Thu 15 OctJaroměř 10:59No data—
Wed 14 OctJaroměř 10:59No data—
Tue 13 OctJaroměř 10:59No data—
Mon 12 OctJaroměř 10:59No data—
Sun 11 OctJaroměř 10:59No data—
Sat 10 OctJaroměř 10:59No data—
Fri 9 OctJaroměř 10:59No data—
Thu 8 OctJaroměř 10:59No data—