Os 6570 6570 Ústí n. L. hl. n. – Most
Alerts for train 6570
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 6570.
It does not run today
Last recorded run: Friday 6 November No data
Next service: Monday 03:50 from Ústí n. L. hl. n. · Mon 9 Nov
Last 30 days
Arrival delay at Most, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 20 Aug Max en route +14 min · last fix heading to — +8 min
- Fri 28 Aug Max en route +6 min · last fix heading to — +6 min
- Fri 25 Sept Max en route +4 min · last fix heading to — +4 min
- Fri 4 Sept Max en route +4 min · last fix heading to — +4 min
- Thu 3 Sept Max en route +4 min · last fix heading to — +4 min
Distribution · 90 days
40 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 73% · 29
- 3–10 min 28% · 11
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 75% M n=8
- 88% T n=8
- 75% W n=8
- 63% T n=8
- 63% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
Last 90 days, 40 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 |
|---|---|---|---|
| 03:50 | on time | on time | |
| 03:52 | ≈ on time | ≈ on time | |
| 04:02 | ≈ on time | ≈ +1 min | |
| 04:03 | ≈ on time | ≈ +1 min | |
| 04:06 | ≈ +1 min | ≈ +1 min | |
| 04:08 / 04:10 | ≈ +1 min | ≈ +2 min | |
| 04:12 | ≈ +1 min | ≈ +2 min | |
| 04:14 | ≈ +1 min | ≈ +2 min | |
| 04:16 | ≈ +1 min | ≈ +2 min | |
| 04:18 | ≈ +1 min | ≈ +2 min | |
| 04:21 | ≈ +1 min | ≈ +3 min | |
| 04:24 / 04:25 | ≈ +1 min | ≈ +3 min | |
| 04:27 | ≈ +1 min | ≈ +3 min | |
| 04:31 | ≈ +1 min | ≈ +4 min | |
| 04:36 | +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 |
|---|---|---|---|
| Fri 6 Nov | Most 04:37 | No data | — |
| Thu 5 Nov | Most 04:37 | No data | — |
| Wed 4 Nov | Most 04:37 | No data | — |
| Tue 3 Nov | Most 04:37 | No data | — |
| Mon 2 Nov | Most 04:37 | No data | — |
| Fri 30 Oct | Most 04:37 | No data | — |
| Thu 29 Oct | Most 04:37 | No data | — |
| Tue 27 Oct | Most 04:37 | No data | — |
| Mon 26 Oct | Most 04:37 | No data | — |
| Fri 23 Oct | Most 04:37 | No data | — |
| Thu 22 Oct | Most 04:37 | No data | — |
| Wed 21 Oct | Most 04:37 | No data | — |
| Tue 20 Oct | Most 04:37 | No data | — |
| Mon 19 Oct | Most 04:37 | No data | — |
| Fri 16 Oct | Most 04:37 | No data | — |
| Thu 15 Oct | Most 04:37 | No data | — |
| Wed 14 Oct | Most 04:37 | No data | — |
| Tue 13 Oct | Most 04:37 | No data | — |
| Mon 12 Oct | Most 04:37 | No data | — |
| Fri 9 Oct | Most 04:37 | No data | — |
| Thu 8 Oct | Most 04:37 | No data | — |
| Wed 7 Oct | Most 04:37 | No data | — |
| Tue 6 Oct | Most 04:37 | No data | — |
| Mon 5 Oct | — 04:53 | +2 min | +2 min |
| Fri 2 Oct | — 04:52 | +2 min | +2 min |
| Thu 1 Oct | — 04:51 | +1 min | +2 min |
| Wed 30 Sept | — 04:52 | +2 min | +2 min |
| Tue 29 Sept | — 04:51 | +1 min | +1 min |
| Fri 25 Sept | — 04:55 | +4 min | +4 min |
| Thu 24 Sept | — 04:52 | +2 min | +2 min |