REG 10496 Hajnówka – Bielsk Podlaski
Alerts for train 10496
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line REG.
✓ Today’s run finished
Today it reached Bielsk Podlaski at 18:16 0 min
- Hajnówka17:47
- Chytra17:51
- Stare Berezowo17:55
- Orlanka18:02
- Mikłasze18:05
- Lewki18:12
- Bielsk Podlaski18:16
Next service: tomorrow 17:47 from Hajnówka · Thu 12 Nov
Last 30 days
Arrival delay at Bielsk Podlaski, 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 6 Nov Max en route +4 min · last fix heading to Bielsk Podlaski +4 min
- Thu 5 Nov Max en route +3 min · last fix heading to Bielsk Podlaski +3 min
Distribution · 90 days
28 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 93% · 26
- 3–10 min 7% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=4
- 100% W n=4
- 67% T n=3
- 75% F n=4
- 100% S n=4
- 100% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 28 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 |
|---|---|---|---|
| 17:47 | on time | +2 min | |
| 17:51 | ≈ on time | ≈ +2 min | |
| 17:55 | ≈ on time | ≈ +2 min | |
| 17:58 | ≈ on time | ≈ +2 min | |
| 18:02 / 18:03 | ≈ on time | ≈ +2 min | |
| 18:05 / 18:06 | ≈ on time | ≈ +2 min | |
| 18:12 | ≈ on time | ≈ +2 min | |
| 18:16 | 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 1 August 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 11 Nov | Bielsk Podlaski 18:17 | 0 min | — |
| Tue 10 Nov | Bielsk Podlaski 18:17 | 0 min | — |
| Mon 9 Nov | Bielsk Podlaski 18:17 | 0 min | — |
| Sun 8 Nov | Orlanka 17:59Partial coverage | 0 min | — |
| Sat 7 Nov | Bielsk Podlaski 18:17 | 0 min | — |
| Fri 6 Nov | Bielsk Podlaski 18:20 | +4 min | +4 min |
| Thu 5 Nov | Bielsk Podlaski 18:19 | +3 min | +3 min |
| Wed 4 Nov | Bielsk Podlaski 18:19 | +2 min | +2 min |
| Tue 3 Nov | Bielsk Podlaski 18:18 | 0 min | — |
| Mon 2 Nov | Bielsk Podlaski 18:17 | 0 min | — |
| Sun 1 Nov | Bielsk Podlaski 18:17 | No data | — |
| Sat 31 Oct | Bielsk Podlaski 18:18 | No data | — |
| Sun 25 Oct | Bielsk Podlaski 18:17 | No data | — |
| Sat 24 Oct | Bielsk Podlaski 18:17 | No data | — |
| Fri 23 Oct | Bielsk Podlaski 18:18 | No data | — |
| Thu 22 Oct | Bielsk Podlaski 18:18 | No data | — |
| Wed 21 Oct | Bielsk Podlaski 18:17 | No data | — |
| Tue 20 Oct | Bielsk Podlaski 18:17 | No data | — |
| Mon 19 Oct | Bielsk Podlaski 18:17 | No data | — |
| Sun 18 Oct | Bielsk Podlaski 18:18 | 0 min | — |
| Sat 17 Oct | Bielsk Podlaski 18:17 | 0 min | — |
| Fri 16 Oct | Bielsk Podlaski 18:17 | 0 min | — |
| Thu 15 Oct | Bielsk Podlaski 18:17 | 0 min | — |
| Wed 14 Oct | Bielsk Podlaski 18:17 | 0 min | — |
| Tue 13 Oct | Bielsk Podlaski 18:17 | 0 min | — |
| Mon 12 Oct | Bielsk Podlaski 18:17 | 0 min | — |
| Sun 11 Oct | Bielsk Podlaski 18:17 | 0 min | — |
| Sat 10 Oct | Bielsk Podlaski 18:18 | 0 min | — |
| Fri 9 Oct | Bielsk Podlaski 18:17 | 0 min | — |
| Thu 8 Oct | Bielsk Podlaski 18:18 | 0 min | — |