Os 16311 16311 Raspenava – Bílý Potok p.Sm.
Alerts for train 16311
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 16311.
It has not run yet today
Last recorded run: Wednesday 11 November No data
Next service: today 11:00 from Raspenava · Thu 12 Nov
Last 30 days
Arrival delay at Bílý Potok p.Sm., 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 1 Oct Max en route +11 min · last fix heading to — +9 min
- Wed 19 Aug Max en route +9 min · last fix heading to — +8 min
- Wed 30 Sept Max en route +7 min · last fix heading to — +6 min
- Wed 23 Sept Max en route +6 min · last fix heading to — +5 min
- Sat 19 Sept Max en route +5 min · last fix heading to — +5 min
Distribution · 90 days
51 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 6% · 3
- On time 80% · 41
- 3–10 min 14% · 7
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=8
- 100% T n=7
- 50% W n=6
- 86% T n=7
- 86% F n=7
- 88% S n=8
- 88% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 51 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 |
|---|---|---|---|
| 11:00 | +2 min | +4 min | |
| 11:02 | ≈ +2 min | ≈ +4 min | |
| 11:04 | ≈ +1 min | ≈ +4 min | |
| 11:08 | ≈ +1 min | ≈ +4 min | |
| 11:13 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 11 Nov | Bílý Potok p.Sm. 11:14 | No data | — |
| Tue 10 Nov | Bílý Potok p.Sm. 11:14 | No data | — |
| Mon 9 Nov | Bílý Potok p.Sm. 11:14 | No data | — |
| Sun 8 Nov | Bílý Potok p.Sm. 11:14 | No data | — |
| Sat 7 Nov | Bílý Potok p.Sm. 11:14 | No data | — |
| Fri 6 Nov | Bílý Potok p.Sm. 11:14 | No data | — |
| Thu 5 Nov | Bílý Potok p.Sm. 11:14 | No data | — |
| Wed 4 Nov | Bílý Potok p.Sm. 11:14 | No data | — |
| Tue 3 Nov | Bílý Potok p.Sm. 11:14 | No data | — |
| Mon 2 Nov | Bílý Potok p.Sm. 11:14 | No data | — |
| Sun 1 Nov | Bílý Potok p.Sm. 11:14 | No data | — |
| Sat 31 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Fri 30 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Thu 29 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Wed 28 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Tue 27 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Mon 26 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Sun 25 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Sat 24 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Fri 23 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Thu 22 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Wed 21 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Tue 20 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Mon 19 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Sun 18 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Sat 17 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Fri 16 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Thu 15 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Wed 14 Oct | Bílý Potok p.Sm. 11:14 | No data | — |
| Tue 13 Oct | Bílý Potok p.Sm. 11:14 | No data | — |