Os 2632 2632 Liberec – Harrachov
Alerts for train 2632
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 2632.
It has not run yet today
Last recorded run: Wednesday 4 November No data
Next service: today 15:35 from Liberec · Thu 5 Nov
Last 30 days
Arrival delay at Harrachov, 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
5 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 5
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=1
- 100% W n=1
- 100% T n=1
- 100% F n=1
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (25 stops).
Last 90 days, 5 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 |
|---|---|---|---|
| 15:35 | on time | +1 min | |
| 15:38 | ≈ on time | ≈ +1 min | |
| 15:41 | ≈ on time | ≈ +1 min | |
| 15:42 | ≈ on time | ≈ +1 min | |
| 15:45 | ≈ on time | ≈ +1 min | |
| 15:50 | ≈ on time | ≈ +1 min | |
| 15:55 / 15:56 | ≈ on time | ≈ +1 min | |
| 15:57 | ≈ on time | ≈ +1 min | |
| 15:59 | ≈ on time | ≈ +1 min | |
| 16:00 | ≈ on time | ≈ +1 min | |
| 16:02 | ≈ on time | ≈ +1 min | |
| 16:06 | ≈ on time | ≈ +1 min | |
| 16:11 / 16:12 | ≈ on time | ≈ +1 min | |
| 16:13 | ≈ +1 min | ≈ +1 min | |
| 16:14 | ≈ +1 min | ≈ +1 min | |
| 16:17 | ≈ on time | ≈ +1 min | |
| 16:20 | ≈ on time | ≈ +1 min | |
| 16:25 / 16:28 | ≈ on time | ≈ +1 min | |
| 16:31 / 16:32 | ≈ on time | ≈ +1 min | |
| 16:34 | ≈ on time | ≈ +1 min | |
| 16:36 | ≈ on time | ≈ +1 min | |
| 16:38 | ≈ on time | ≈ +1 min | |
| 16:40 | ≈ on time | ≈ +1 min | |
| 16:43 / 16:44 | ≈ on time | ≈ +1 min | |
| 16:52 | on time | +2 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 4 Nov | Harrachov 16:53 | No data | — |
| Tue 3 Nov | Harrachov 16:53 | No data | — |
| Mon 2 Nov | Harrachov 16:53 | No data | — |
| Sun 1 Nov | Harrachov 16:53 | No data | — |
| Sat 31 Oct | Harrachov 16:53 | No data | — |
| Fri 30 Oct | Harrachov 16:53 | No data | — |
| Thu 29 Oct | Harrachov 16:53 | No data | — |
| Tue 27 Oct | Harrachov 16:53 | No data | — |
| Mon 26 Oct | Harrachov 16:53 | No data | — |
| Fri 23 Oct | Harrachov 16:53 | No data | — |
| Thu 22 Oct | Harrachov 16:53 | No data | — |
| Wed 21 Oct | Harrachov 16:53 | No data | — |
| Tue 20 Oct | Harrachov 16:53 | No data | — |
| Mon 19 Oct | Harrachov 16:53 | No data | — |
| Fri 16 Oct | Harrachov 16:53 | No data | — |
| Thu 15 Oct | Harrachov 16:53 | No data | — |
| Wed 14 Oct | Harrachov 16:53 | No data | — |
| Tue 13 Oct | Harrachov 16:53 | No data | — |
| Mon 12 Oct | Harrachov 16:53 | No data | — |
| Fri 9 Oct | Harrachov 16:53 | No data | — |
| Thu 8 Oct | Harrachov 16:53 | No data | — |
| Wed 7 Oct | Harrachov 16:53 | No data | — |
| Tue 6 Oct | Harrachov 16:53 | No data | — |
| Mon 5 Oct | Harrachov 16:53 | 0 min | +4 min |
| Fri 2 Oct | — 17:07 | +1 min | +5 min |
| Thu 1 Oct | — 17:08 | 0 min | +2 min |
| Wed 30 Sept | — 17:09 | +2 min | +3 min |
| Tue 29 Sept | — 17:06 | 0 min | +2 min |