Os 20203 20203 Hradec Král. hl. n. – Rychnov nad Kněž.
Alerts for train 20203
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Os 20203.
✓ Today’s run finished
Today, last fix heading to Rychnov nad Kněž. at 06:54 No data
- Hradec Král. hl. n.06:06
- Hradec Králové-Slezské Předměstí06:11
- Třebechovice pod Orebem06:21
- Lípa nad Orlicí06:33
- Častolovice06:40
- Synkov06:46
- Rychnov nad Kněž.06:55
Next service: tomorrow 06:06 from Hradec Král. hl. n. · Sun 15 Nov
Last 30 days
Arrival delay at Rychnov nad Kněž., in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Distribution · 90 days
15 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 40% · 6
- On time 60% · 9
- 3–10 min 0% · 0
- 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
- 100% 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 06:06 | on time | +2 min | |
| 06:09 | ≈ on time | ≈ +2 min | |
| 06:11 / 06:12 | ≈ on time | ≈ +2 min | |
| 06:17 | ≈ on time | ≈ +2 min | |
| 06:21 / 06:22 | ≈ on time | ≈ +2 min | |
| 06:26 / 06:27 | ≈ on time | ≈ +1 min | |
| 06:30 / 06:31 | ≈ on time | ≈ +1 min | |
| 06:33 / 06:34 | ≈ 1 min early | ≈ +1 min | |
| 06:37 | ≈ 1 min early | ≈ +1 min | |
| 06:40 / 06:41 | ≈ 1 min early | ≈ +1 min | |
| 06:42 / 06:43 | ≈ 1 min early | ≈ +1 min | |
| 06:46 / 06:47 | ≈ 1 min early | ≈ on time | |
| 06:49 / 06:50 | ≈ 1 min early | ≈ on time | |
| 06:55 | 1 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 14 Nov | Rychnov nad Kněž. 06:54 | No data | — |
| Sun 8 Nov | Rychnov nad Kněž. 06:54 | No data | — |
| Sat 7 Nov | Rychnov nad Kněž. 06:54 | No data | — |
| Sun 1 Nov | Rychnov nad Kněž. 06:56 | No data | — |
| Sat 31 Oct | Rychnov nad Kněž. 06:56 | No data | — |
| Wed 28 Oct | Rychnov nad Kněž. 06:56 | No data | — |
| Sun 25 Oct | Rychnov nad Kněž. 06:56 | No data | — |
| Sat 24 Oct | Rychnov nad Kněž. 06:56 | No data | — |
| Sun 18 Oct | Rychnov nad Kněž. 06:56 | No data | — |
| Sat 17 Oct | Rychnov nad Kněž. 06:56 | No data | — |
| Sun 11 Oct | Rychnov nad Kněž. 06:56 | No data | — |
| Sat 10 Oct | Rychnov nad Kněž. 06:56 | No data | — |
| Sun 4 Oct | — 07:08 | −2 min | +5 min |
| Sat 3 Oct | — 07:10 | −1 min | +3 min |
| Mon 28 Sept | — 07:08 | −2 min | — |
| Sun 27 Sept | — 07:08 | −2 min | — |
| Sat 26 Sept | — 07:09 | 0 min | +1 min |
| Sun 20 Sept | — 07:08 | −1 min | — |
| Sat 19 Sept | — 07:12 | +2 min | +4 min |
| Sun 13 Sept | — 07:07 | −2 min | — |
| Sat 12 Sept | — 07:08 | −2 min | — |
| Sun 6 Sept | — 07:08 | −1 min | — |
| Sat 5 Sept | — 07:10 | 0 min | +4 min |
| Sun 30 Aug | — 07:07 | −2 min | — |
| Sat 29 Aug | — 07:08 | −1 min | +1 min |
| Sun 23 Aug | — 07:08 | −1 min | +1 min |
| Sat 22 Aug | — 07:09 | 0 min | +2 min |