Os 2181 2181 České Budějovice – Borovany
Alerts for train 2181
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 2181.
✓ Today’s run finished
Today, last fix heading to Borovany at 07:24 No data
- České Budějovice07:05
- Nové Hodějovice07:08
- Nová Ves u Českých Budějovic07:13
- Trocnov07:19
- Radostice u Trocnova07:21
- Borovany07:24
Next service: tomorrow 07:05 from České Budějovice · Fri 6 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
- Fri 18 Sept Max en route +10 min · last fix heading to — +9 min
- Fri 4 Sept Max en route +8 min · last fix heading to — +8 min
- Thu 24 Sept Max en route +5 min · last fix heading to — +4 min
- Tue 11 Aug Max en route +6 min · last fix heading to — +4 min
- Tue 15 Sept Max en route +3 min · last fix heading to — +3 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 83% · 33
- 3–10 min 18% · 7
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 88% M n=8
- 75% T n=8
- 100% W n=8
- 75% T n=8
- 75% 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 |
|---|---|---|---|
| 07:05 | on time | +5 min | |
| 07:08 | ≈ on time | ≈ +5 min | |
| 07:13 / 07:14 | ≈ on time | ≈ +5 min | |
| 07:19 | ≈ on time | ≈ +4 min | |
| 07:21 | ≈ on time | ≈ +4 min | |
| 07:24 | on time | +3 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 |
|---|---|---|---|
| Thu 5 Nov | Borovany 07:24 | No data | — |
| Wed 4 Nov | Borovany 07:24 | No data | — |
| Tue 3 Nov | Borovany 07:24 | No data | — |
| Mon 2 Nov | Borovany 07:24 | No data | — |
| Fri 30 Oct | Borovany 07:25 | No data | — |
| Thu 29 Oct | Borovany 07:25 | No data | — |
| Tue 27 Oct | Borovany 07:25 | No data | — |
| Mon 26 Oct | Borovany 07:25 | No data | — |
| Fri 23 Oct | Borovany 07:25 | No data | — |
| Thu 22 Oct | Borovany 07:25 | No data | — |
| Wed 21 Oct | Borovany 07:25 | No data | — |
| Tue 20 Oct | Borovany 07:25 | No data | — |
| Mon 19 Oct | Borovany 07:25 | No data | — |
| Fri 16 Oct | Borovany 07:25 | No data | — |
| Thu 15 Oct | Borovany 07:25 | No data | — |
| Wed 14 Oct | Borovany 07:25 | No data | — |
| Tue 13 Oct | Borovany 07:25 | No data | — |
| Mon 12 Oct | Borovany 07:25 | No data | — |
| Fri 9 Oct | Borovany 07:25 | No data | — |
| Thu 8 Oct | Borovany 07:26 | No data | — |
| Wed 7 Oct | Borovany 07:25 | No data | — |
| Tue 6 Oct | Borovany 07:25 | No data | — |
| Mon 5 Oct | — 07:41 | +2 min | +2 min |
| Fri 2 Oct | — 07:41 | +2 min | +2 min |
| Thu 1 Oct | — 07:39 | +1 min | +1 min |
| Wed 30 Sept | — 07:39 | 0 min | — |
| Tue 29 Sept | — 07:39 | 0 min | +1 min |
| Fri 25 Sept | — 07:39 | 0 min | — |
| Thu 24 Sept | — 07:42 | +4 min | +5 min |
| Wed 23 Sept | — 07:39 | 0 min | +1 min |