Os 2183 2183 České Budějovice – Borovany
Alerts for train 2183
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 2183.
It does not run today
Last recorded run: Friday 6 November No data
Next service: Monday 11:10 from České Budějovice · Mon 9 Nov
Last 30 days
Arrival delay at Borovany, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 31 Aug Max en route +24 min · last fix heading to — +23 min
- Tue 18 Aug Max en route +24 min · last fix heading to — +23 min
- Tue 11 Aug Max en route +23 min · last fix heading to — +22 min
- Mon 10 Aug Max en route +24 min · last fix heading to — +22 min
- Mon 24 Aug Max en route +13 min · last fix heading to — +13 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 15% · 6
- 3–10 min 60% · 24
- 10–30 min 25% · 10
- 30+ min 0% · 0
On-time by weekday
- 0% M n=8
- 25% T n=8
- 13% W n=8
- 25% T n=8
- 13% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 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 |
|---|---|---|---|
| 11:10 | +8 min | +11 min | |
| 11:12 | ≈ +7 min | ≈ +11 min | |
| 11:17 / 11:18 | ≈ +7 min | ≈ +13 min | |
| 11:24 | ≈ +6 min | ≈ +14 min | |
| 11:26 | ≈ +6 min | ≈ +14 min | |
| 11:29 | +6 min | +14 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 | Borovany 11:29 | No data | — |
| Thu 5 Nov | Borovany 11:29 | No data | — |
| Wed 4 Nov | Borovany 11:29 | No data | — |
| Tue 3 Nov | Borovany 11:29 | No data | — |
| Mon 2 Nov | Borovany 11:29 | No data | — |
| Fri 30 Oct | Borovany 11:30 | No data | — |
| Thu 29 Oct | Borovany 11:30 | No data | — |
| Tue 27 Oct | Borovany 11:30 | No data | — |
| Mon 26 Oct | Borovany 11:30 | No data | — |
| Fri 23 Oct | Borovany 11:30 | No data | — |
| Thu 22 Oct | Borovany 11:30 | No data | — |
| Wed 21 Oct | Borovany 11:30 | No data | — |
| Tue 20 Oct | Borovany 11:30 | No data | — |
| Mon 19 Oct | Borovany 11:30 | No data | — |
| Fri 16 Oct | Borovany 11:30 | No data | — |
| Thu 15 Oct | Borovany 11:30 | No data | — |
| Wed 14 Oct | Borovany 11:30 | No data | — |
| Tue 13 Oct | Borovany 11:30 | No data | — |
| Mon 12 Oct | Borovany 11:30 | No data | — |
| Fri 9 Oct | Borovany 11:30 | No data | — |
| Thu 8 Oct | Borovany 11:30 | No data | — |
| Wed 7 Oct | Borovany 11:30 | No data | — |
| Tue 6 Oct | Borovany 11:30 | No data | — |
| Mon 5 Oct | — 11:53 | +10 min | +11 min |
| Fri 2 Oct | — 11:50 | +6 min | +7 min |
| Thu 1 Oct | — 11:47 | +3 min | +3 min |
| Wed 30 Sept | — 11:50 | +7 min | +9 min |
| Tue 29 Sept | — 11:53 | +10 min | +10 min |
| Fri 25 Sept | — 11:45 | +2 min | +4 min |
| Thu 24 Sept | — 11:51 | +7 min | +8 min |