Sp 7849 7849 Plzeň hl. n. – Rokycany
Alerts for train 7849
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Sp 7849.
✓ Today’s run finished
Today, last fix heading to Rokycany at 13:19 No data
- Plzeň hl. n.13:08
- Plzeň-Doubravka13:11
- Ejpovice13:15
- Klabava13:16
- Rokycany13:20
Next service: Monday 13:08 from Plzeň hl. n. · Mon 9 Nov
Last 30 days
Arrival delay at Rokycany, 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 14 Aug Max en route +11 min · last fix heading to — +10 min
- Mon 21 Sept Max en route +9 min · last fix heading to — +8 min
- Wed 9 Sept Max en route +4 min · last fix heading to — +4 min
- Wed 26 Aug Max en route +5 min · last fix heading to — +4 min
- Thu 1 Oct 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 75% · 30
- 3–10 min 23% · 9
- 10–30 min 3% · 1
- 30+ min 0% · 0
On-time by weekday
- 88% M n=8
- 100% T n=8
- 50% W n=8
- 88% T n=8
- 50% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 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 |
|---|---|---|---|
| 13:08 | +1 min | +3 min | |
| 13:11 | ≈ +1 min | ≈ +3 min | |
| 13:15 | ≈ on time | ≈ +3 min | |
| 13:16 | ≈ on time | ≈ +3 min | |
| 13:20 | 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 |
|---|---|---|---|
| Fri 6 Nov | Rokycany 13:19 | No data | — |
| Thu 5 Nov | Rokycany 13:19 | No data | — |
| Wed 4 Nov | Rokycany 13:19 | No data | — |
| Tue 3 Nov | Rokycany 13:19 | No data | — |
| Mon 2 Nov | Rokycany 13:19 | No data | — |
| Fri 30 Oct | Rokycany 13:21 | No data | — |
| Thu 29 Oct | Rokycany 13:21 | No data | — |
| Tue 27 Oct | Rokycany 13:21 | No data | — |
| Mon 26 Oct | Rokycany 13:21 | No data | — |
| Fri 23 Oct | Rokycany 13:21 | No data | — |
| Thu 22 Oct | Rokycany 13:21 | No data | — |
| Wed 21 Oct | Rokycany 13:21 | No data | — |
| Tue 20 Oct | Rokycany 13:21 | No data | — |
| Mon 19 Oct | Rokycany 13:21 | No data | — |
| Fri 16 Oct | Rokycany 13:21 | No data | — |
| Thu 15 Oct | Rokycany 13:21 | No data | — |
| Wed 14 Oct | Rokycany 13:21 | No data | — |
| Tue 13 Oct | Rokycany 13:21 | No data | — |
| Mon 12 Oct | Rokycany 13:21 | No data | — |
| Fri 9 Oct | Rokycany 13:21 | No data | — |
| Thu 8 Oct | Rokycany 13:21 | No data | — |
| Wed 7 Oct | Rokycany 13:21 | No data | — |
| Tue 6 Oct | Rokycany 13:21 | No data | — |
| Mon 5 Oct | — 13:34 | 0 min | — |
| Fri 2 Oct | — 13:36 | +1 min | +1 min |
| Thu 1 Oct | — 13:38 | +3 min | +3 min |
| Wed 30 Sept | — 13:37 | +2 min | +2 min |
| Tue 29 Sept | — 13:34 | 0 min | +1 min |
| Fri 25 Sept | — 13:38 | +3 min | +3 min |
| Thu 24 Sept | — 13:35 | 0 min | +1 min |