REG 10214 Kuźnica Białostocka – Białystok
Alerts for train 10214
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.
It has not run yet today
Last recorded run: Saturday 14 November 0 min
Next service: today 07:17 from Kuźnica Białostocka · Sun 15 Nov
Last 30 days
Arrival delay at Białystok, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 28 Oct Max en route +12 min · last fix heading to Białystok +12 min
- Wed 9 Sept Max en route +8 min · last fix heading to Wasilków +8 min
- Thu 10 Sept Max en route +6 min · last fix heading to Wasilków +6 min
Distribution · 90 days
38 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 92% · 35
- 3–10 min 5% · 2
- 10–30 min 3% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=6
- 100% T n=5
- 67% W n=6
- 83% T n=6
- 100% F n=5
- 100% S n=5
- 100% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 38 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:17 | on time | +3 min | |
| 07:21 / 07:22 | ≈ on time | ≈ +3 min | |
| 07:26 / 07:27 | ≈ on time | ≈ +3 min | |
| 07:33 | ≈ on time | ≈ +3 min | |
| 07:38 | ≈ on time | ≈ +2 min | |
| 07:43 | ≈ on time | ≈ +2 min | |
| 07:47 | ≈ on time | ≈ +2 min | |
| 07:51 | ≈ on time | ≈ +2 min | |
| 07:54 / 07:55 | ≈ on time | ≈ +2 min | |
| 07:58 / 07:59 | ≈ on time | ≈ +1 min | |
| 08:03 / 08:04 | ≈ on time | ≈ +1 min | |
| 08:10 | on time | +1 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 |
|---|---|---|---|
| Sat 14 Nov | Białystok 08:09 | 0 min | — |
| Fri 13 Nov | Białystok 08:12 | +1 min | +1 min |
| Thu 12 Nov | Białystok 08:12 | +1 min | +1 min |
| Wed 11 Nov | Białystok 08:09 | 0 min | — |
| Tue 10 Nov | Białystok 08:09 | 0 min | — |
| Mon 9 Nov | Białystok 08:09 | 0 min | — |
| Sun 8 Nov | Białystok 08:09 | 0 min | — |
| Sat 7 Nov | Białystok 08:09 | 0 min | — |
| Fri 6 Nov | Białystok 08:09 | 0 min | — |
| Thu 5 Nov | Białystok 08:09 | 0 min | — |
| Wed 4 Nov | Białystok 08:09 | 0 min | — |
| Tue 3 Nov | Białystok 08:09 | 0 min | — |
| Mon 2 Nov | Białystok 08:09 | 0 min | — |
| Sun 1 Nov | Białystok 08:12 | No data | — |
| Sat 31 Oct | Białystok 08:12 | 0 min | — |
| Fri 30 Oct | Białystok 08:11 | 0 min | — |
| Thu 29 Oct | Białystok 08:11 | 0 min | — |
| Wed 28 Oct | Białystok 08:23 | +12 min | +12 min |
| Tue 27 Oct | Białystok 08:11 | 0 min | — |
| Mon 26 Oct | Białystok 08:11 | 0 min | — |
| Sun 25 Oct | Białystok 08:11 | No data | — |
| Sat 24 Oct | Białystok 08:11 | No data | — |
| Fri 23 Oct | Białystok 08:11 | No data | — |
| Thu 22 Oct | Białystok 08:11 | No data | — |
| Wed 21 Oct | Białystok 08:11 | No data | — |
| Tue 20 Oct | Białystok 08:11 | No data | — |
| Mon 19 Oct | Białystok 08:12 | +1 min | +1 min |
| Sun 18 Oct | Białystok 08:12 | +1 min | +1 min |
| Sat 17 Oct | Białystok 08:12 | +1 min | +1 min |
| Fri 16 Oct | Białystok 08:11 | 0 min | — |