REG 19060 Łomża – Białystok
Alerts for train 19060
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 Białystok at 07:27 +7 min
- Łomża05:39
- Koziki05:46
- Śniadowo05:53
- Kulesze Kościelne06:36
- Sokoły06:48
- Białystok Zielone Wzgórza07:16
- Białystok07:20
Next service: tomorrow 05:39 from Łomża · Sun 8 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 30 Sept Max en route +39 min · last fix heading to Sokoły +39 min
- Thu 17 Sept Max en route +25 min · last fix heading to Łapy +25 min
- Wed 14 Oct Max en route +20 min · last fix heading to Białystok +20 min
- Thu 15 Oct Max en route +14 min · last fix heading to Białystok +14 min
- Wed 16 Sept Max en route +9 min · last fix heading to Białystok Zielone Wzgórza +9 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 64% · 18
- 3–10 min 21% · 6
- 10–30 min 11% · 3
- 30+ min 4% · 1
On-time by weekday
- 80% M n=5
- 75% T n=4
- 50% W n=6
- 25% T n=4
- 67% F n=3
- 75% S n=4
- 100% S n=2
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 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 |
|---|---|---|---|
| 05:39 | on time | +16 min | |
| 05:41 / 05:42 | ≈ on time | ≈ +16 min | |
| 05:46 | ≈ on time | ≈ +16 min | |
| 05:53 / 06:04 | ≈ on time | ≈ +16 min | |
| 06:07 | ≈ on time | ≈ +16 min | |
| 06:36 | ≈ on time | ≈ +16 min | |
| 06:48 | ≈ on time | ≈ +16 min | |
| 07:00 / 07:01 | ≈ on time | ≈ +16 min | |
| 07:16 | ≈ on time | ≈ +16 min | |
| 07:20 | on time | +16 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 7 Nov | Białystok 07:28 | +7 min | +7 min |
| Fri 6 Nov | Białystok 07:29 | +7 min | +7 min |
| Thu 5 Nov | Białystok 07:19 | No data | — |
| Wed 4 Nov | Białystok 07:19 | 0 min | — |
| Tue 3 Nov | Białystok 07:19 | 0 min | — |
| Mon 2 Nov | Białystok 07:19 | 0 min | — |
| Sun 1 Nov | Białystok 07:22 | No data | — |
| Sat 31 Oct | Białystok 07:21 | 0 min | — |
| Fri 30 Oct | Białystok 07:21 | 0 min | — |
| Thu 29 Oct | Białystok 07:28 | +7 min | +7 min |
| Wed 28 Oct | Białystok 07:21 | 0 min | — |
| Tue 27 Oct | Białystok 07:21 | 0 min | — |
| Mon 26 Oct | Białystok 07:21 | 0 min | — |
| Sun 25 Oct | Białystok 07:21 | No data | — |
| Sat 24 Oct | Białystok 07:21 | No data | — |
| Fri 23 Oct | Białystok 07:21 | No data | — |
| Thu 22 Oct | Białystok 07:21 | No data | — |
| Wed 21 Oct | Białystok 07:21 | No data | — |
| Tue 20 Oct | Białystok 07:21 | No data | — |
| Mon 19 Oct | Białystok 07:21 | 0 min | — |
| Sun 18 Oct | Białystok 07:21 | 0 min | — |
| Sat 17 Oct | Białystok 07:21 | 0 min | — |
| Fri 16 Oct | Białystok 07:21 | No data | — |
| Thu 15 Oct | Białystok 07:35 | +14 min | +14 min |
| Wed 14 Oct | Białystok 07:41 | +20 min | +20 min |
| Tue 13 Oct | Białystok 07:25 | +4 min | +4 min |
| Mon 12 Oct | Białystok 07:26 | +4 min | +4 min |
| Sun 11 Oct | Białystok 07:21 | No data | — |
| Sat 10 Oct | Białystok 07:21 | 0 min | — |
| Fri 9 Oct | Białystok 07:22 | 0 min | — |