REG 10390 Białystok – Łapy
Alerts for train 10390
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 Łapy at 14:00 0 min
- Białystok13:35
- Białystok Zielone Wzgórza13:38
- Niewodnica13:44
- Trypucie13:47
- Baciuty13:50
- Uhowo13:57
- Łapy14:00
Next service: tomorrow 13:35 from Białystok · Mon 9 Nov
Last 30 days
Arrival delay at Łapy, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 1 Nov Max en route +6 min · last fix heading to Łapy +6 min
- Fri 25 Sept Max en route +5 min · last fix heading to Uhowo +5 min
- Wed 4 Nov Max en route +3 min · last fix heading to Łapy +3 min
- Mon 2 Nov Max en route +3 min · last fix heading to Łapy +3 min
- Thu 17 Sept Max en route +3 min · last fix heading to Łapy +3 min
Distribution · 90 days
30 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 83% · 25
- 3–10 min 17% · 5
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 100% T n=6
- 75% W n=4
- 80% T n=5
- 83% F n=6
- — S n=0
- 83% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 30 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:35 | on time | +3 min | |
| 13:38 | ≈ on time | ≈ +3 min | |
| 13:41 | ≈ on time | ≈ +3 min | |
| 13:44 / 13:45 | ≈ on time | ≈ +3 min | |
| 13:47 | ≈ on time | ≈ +3 min | |
| 13:50 / 13:51 | ≈ on time | ≈ +3 min | |
| 13:53 / 13:54 | ≈ on time | ≈ +3 min | |
| 13:57 | ≈ on time | ≈ +3 min | |
| 14:00 | 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 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 |
|---|---|---|---|
| Sun 8 Nov | Łapy 13:59 | 0 min | — |
| Fri 6 Nov | Łapy 13:59 | 0 min | — |
| Thu 5 Nov | Łapy 13:59 | 0 min | — |
| Wed 4 Nov | Łapy 14:04 | +3 min | +3 min |
| Tue 3 Nov | Łapy 13:59 | 0 min | — |
| Mon 2 Nov | Łapy 14:04 | +3 min | +3 min |
| Sun 1 Nov | Łapy 14:07 | +6 min | +6 min |
| Fri 30 Oct | Łapy 14:03 | +2 min | +2 min |
| Thu 29 Oct | Łapy 14:01 | 0 min | — |
| Wed 28 Oct | Łapy 14:01 | 0 min | — |
| Tue 27 Oct | Łapy 14:01 | 0 min | — |
| Mon 26 Oct | Łapy 14:02 | 0 min | — |
| Sun 25 Oct | Łapy 14:01 | No data | — |
| Fri 23 Oct | Łapy 14:01 | No data | — |
| Thu 22 Oct | Łapy 14:01 | No data | — |
| Wed 21 Oct | Łapy 14:02 | No data | — |
| Tue 20 Oct | Łapy 14:02 | No data | — |
| Mon 19 Oct | Łapy 14:01 | No data | — |
| Sun 18 Oct | Łapy 14:01 | 0 min | — |
| Fri 16 Oct | Łapy 14:01 | 0 min | — |
| Thu 15 Oct | Łapy 14:01 | 0 min | — |
| Wed 14 Oct | Łapy 14:01 | 0 min | — |
| Tue 13 Oct | Łapy 14:01 | 0 min | — |
| Mon 12 Oct | Łapy 14:01 | 0 min | — |
| Sun 11 Oct | Łapy 14:01 | 0 min | — |
| Fri 9 Oct | Łapy 14:01 | 0 min | — |
| Thu 8 Oct | Łapy 14:01 | 0 min | — |
| Wed 7 Oct | Łapy 14:01 | No data | — |
| Tue 6 Oct | Łapy 14:01 | 0 min | — |
| Mon 5 Oct | Łapy 14:01 | No data | — |