Os 20204 20204 Rychnov nad Kněž. – Hradec Král. hl. n.

View line Os 20204

Rychnov nad Kněž. 07:06 → Hradec Král. hl. n. 07:58 Tue, Sat, Sun 0 h 52 min · 14 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Hradec Král. hl. n. at 07:59 No data

  1. Rychnov nad Kněž.07:06
  2. Synkov07:13
  3. Častolovice07:19
  4. Týniště nad Orlicí07:29
  5. Třebechovice pod Orebem07:40
  6. Hradec Králové-Slezské Předměstí07:49
  7. Hradec Král. hl. n.07:58

Next service: tomorrow 07:06 from Rychnov nad Kněž. · Sun 15 Nov

Next departure 07:06 tomorrow · Rychnov nad Kněž.
On-time · 30 days
—
Too little data (0/10 runs with data)
RT coverage: 0 full · 0 partial · 10 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 15 full · 0 partial · 12 no data
Typical delay
−1min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Hradec Král. hl. n., in minutes. One bar per run.

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

Worst days

  • Sat 3 Oct Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 86% S n=7
  • 100% S n=7

Stops and timetable

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

Last 90 days, 15 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
07:06on time +2 min
07:10≈ on time ≈ +2 min
07:13≈ on time ≈ +2 min
07:17≈ on time ≈ +2 min
07:19 / 07:20≈ on time ≈ +2 min
07:22≈ on time ≈ +2 min
07:25 / 07:26≈ on time ≈ +2 min
07:29 / 07:32≈ on time ≈ +1 min
07:35 / 07:36≈ 1 min early ≈ +1 min
07:40 / 07:41≈ 1 min early ≈ +1 min
07:44 / 07:45≈ 1 min early ≈ +1 min
07:49 / 07:51≈ 1 min early ≈ +1 min
07:53 / 07:54≈ 1 min early ≈ +1 min
07:581 min early +2 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 14 NovHradec Král. hl. n. 07:59No data—
Sun 8 NovHradec Král. hl. n. 07:59No data—
Sat 7 NovHradec Král. hl. n. 07:59No data—
Sun 1 NovHradec Král. hl. n. 07:59No data—
Sat 31 OctHradec Král. hl. n. 07:59No data—
Wed 28 OctHradec Král. hl. n. 07:59No data—
Sun 25 OctHradec Král. hl. n. 07:59No data—
Sat 24 OctHradec Král. hl. n. 07:59No data—
Sun 18 OctHradec Král. hl. n. 07:59No data—
Sat 17 OctHradec Král. hl. n. 07:59No data—
Sun 11 OctHradec Král. hl. n. 07:59No data—
Sat 10 OctHradec Král. hl. n. 07:59No data—
Sun 4 Oct— 08:160 min+2 min
Sat 3 Oct— 08:22+6 min+6 min
Mon 28 Sept— 08:12−1 min+2 min
Sun 27 Sept— 08:12−1 min+2 min
Sat 26 Sept— 08:12−1 min+1 min
Sun 20 Sept— 08:11−1 min+3 min
Sat 19 Sept— 08:14+1 min+2 min
Sun 13 Sept— 08:11−1 min+2 min
Sat 12 Sept— 08:130 min+6 min
Sun 6 Sept— 08:120 min+2 min
Sat 5 Sept— 08:14+2 min+2 min
Sun 30 Aug— 08:11−1 min+1 min
Sat 29 Aug— 08:12−1 min+2 min
Sun 23 Aug— 08:11−1 min—
Sat 22 Aug— 08:120 min+2 min