Os 16300 16300 Bílý Potok p.Sm. – Raspenava
Alerts for train 16300
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 16300.
✓ Today’s run finished
Today, last fix heading to Raspenava at 04:54 No data
- Bílý Potok p.Sm.04:41
- Hejnice04:44
- Lužec pod Smrkem04:47
- Luh pod Smrkem04:49
- Raspenava04:53
Next service: tomorrow 04:41 from Bílý Potok p.Sm. · Wed 11 Nov
Last 30 days
Arrival delay at Raspenava, 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 +15 min · last fix heading to — +15 min
- Mon 31 Aug Max en route +6 min · last fix heading to — +5 min
Distribution · 90 days
54 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 6% · 3
- On time 91% · 49
- 3–10 min 2% · 1
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 88% M n=8
- 100% T n=7
- 100% W n=7
- 88% T n=8
- 100% F n=8
- 100% S n=8
- 100% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 54 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 |
|---|---|---|---|
| 04:41 | on time | +2 min | |
| 04:44 | ≈ on time | ≈ +2 min | |
| 04:47 | ≈ on time | ≈ +1 min | |
| 04:49 | ≈ on time | ≈ +1 min | |
| 04:53 | on time | +1 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 |
|---|---|---|---|
| Tue 10 Nov | Raspenava 04:54 | No data | — |
| Mon 9 Nov | Raspenava 04:54 | No data | — |
| Sun 8 Nov | Raspenava 04:54 | No data | — |
| Sat 7 Nov | Raspenava 04:54 | No data | — |
| Fri 6 Nov | Raspenava 04:54 | No data | — |
| Thu 5 Nov | Raspenava 04:54 | No data | — |
| Wed 4 Nov | Raspenava 04:54 | No data | — |
| Tue 3 Nov | Raspenava 04:55 | No data | — |
| Mon 2 Nov | Raspenava 04:54 | No data | — |
| Sun 1 Nov | Raspenava 04:54 | No data | — |
| Sat 31 Oct | Raspenava 04:54 | No data | — |
| Fri 30 Oct | Raspenava 04:54 | No data | — |
| Thu 29 Oct | Raspenava 04:54 | No data | — |
| Wed 28 Oct | Raspenava 04:55 | No data | — |
| Tue 27 Oct | Raspenava 04:54 | No data | — |
| Mon 26 Oct | Raspenava 04:54 | No data | — |
| Sun 25 Oct | Raspenava 04:54 | No data | — |
| Sat 24 Oct | Raspenava 04:54 | No data | — |
| Fri 23 Oct | Raspenava 04:54 | No data | — |
| Thu 22 Oct | Raspenava 04:54 | No data | — |
| Wed 21 Oct | Raspenava 04:54 | No data | — |
| Tue 20 Oct | Raspenava 04:54 | No data | — |
| Mon 19 Oct | Raspenava 04:54 | No data | — |
| Sun 18 Oct | Raspenava 04:54 | No data | — |
| Sat 17 Oct | Raspenava 04:54 | No data | — |
| Fri 16 Oct | Raspenava 04:54 | No data | — |
| Thu 15 Oct | Raspenava 04:54 | No data | — |
| Wed 14 Oct | Raspenava 04:54 | No data | — |
| Tue 13 Oct | Raspenava 04:54 | No data | — |
| Mon 12 Oct | Raspenava 04:54 | No data | — |