Os 16820 16820 Žatec – Jirkov
Alerts for train 16820
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 16820.
✓ Today’s run finished
Today, last fix heading to Jirkov at 05:38 No data
- Žatec05:04
- Hořetice05:10
- Denětice05:12
- Březno u Chomutova05:16
- Chomutov05:28
- Chomutov město05:32
- Jirkov05:37
Next service: tomorrow 05:04 from Žatec · Tue 10 Nov
Last 30 days
Arrival delay at Jirkov, 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 14 Aug Max en route +7 min · last fix heading to — +6 min
- Wed 12 Aug Max en route +10 min · last fix heading to — +6 min
- Tue 22 Sept Max en route +4 min · last fix heading to — +4 min
- Wed 16 Sept Max en route +4 min · last fix heading to — +4 min
- Mon 7 Sept Max en route +8 min · last fix heading to — +4 min
Distribution · 90 days
38 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 76% · 29
- 3–10 min 24% · 9
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 71% M n=7
- 71% T n=7
- 63% W n=8
- 88% T n=8
- 88% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 38 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 |
|---|---|---|---|
| 05:04 | on time | on time | |
| 05:07 | ≈ on time | ≈ +1 min | |
| 05:10 / 05:11 | ≈ on time | ≈ +1 min | |
| 05:12 | ≈ on time | ≈ +1 min | |
| 05:14 | ≈ on time | ≈ +2 min | |
| 05:16 / 05:17 | ≈ on time | ≈ +2 min | |
| 05:28 / 05:29 | ≈ +1 min | ≈ +3 min | |
| 05:31 | ≈ +1 min | ≈ +3 min | |
| 05:32 | ≈ +1 min | ≈ +3 min | |
| 05:37 | +1 min | +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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 9 Nov | Jirkov 05:38 | No data | — |
| Fri 6 Nov | Jirkov 05:38 | No data | — |
| Thu 5 Nov | Jirkov 05:38 | No data | — |
| Wed 4 Nov | Jirkov 05:38 | No data | — |
| Tue 3 Nov | Jirkov 05:39 | No data | — |
| Mon 2 Nov | Jirkov 05:38 | No data | — |
| Fri 30 Oct | Jirkov 05:38 | No data | — |
| Thu 29 Oct | Jirkov 05:38 | No data | — |
| Tue 27 Oct | Jirkov 05:38 | No data | — |
| Mon 26 Oct | Jirkov 05:38 | No data | — |
| Fri 23 Oct | Jirkov 05:38 | No data | — |
| Thu 22 Oct | Jirkov 05:38 | No data | — |
| Wed 21 Oct | Jirkov 05:38 | No data | — |
| Tue 20 Oct | Jirkov 05:38 | No data | — |
| Mon 19 Oct | Jirkov 05:38 | No data | — |
| Fri 16 Oct | Jirkov 05:38 | No data | — |
| Thu 15 Oct | Jirkov 05:38 | No data | — |
| Wed 14 Oct | Jirkov 05:38 | No data | — |
| Tue 13 Oct | Jirkov 05:38 | No data | — |
| Mon 12 Oct | Jirkov 05:38 | No data | — |
| Fri 9 Oct | Jirkov 05:38 | No data | — |
| Thu 8 Oct | Jirkov 05:38 | No data | — |
| Wed 7 Oct | Jirkov 05:38 | No data | — |
| Tue 6 Oct | Jirkov 05:39 | No data | — |
| Mon 5 Oct | — 05:51 | −1 min | — |
| Fri 2 Oct | — 05:52 | +1 min | +2 min |
| Thu 1 Oct | — 05:53 | +2 min | +3 min |
| Wed 30 Sept | — 05:52 | +1 min | +3 min |
| Tue 29 Sept | — 05:52 | 0 min | — |
| Fri 25 Sept | — 05:52 | 0 min | — |