REG 10361 Czyżew – Białystok
Alerts for train 10361
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 13:05 0 min
- Czyżew12:03
- Szepietowo12:16
- Racibory12:27
- Łapy12:39
- Bojary12:45
- Niewodnica12:54
- Białystok13:05
Next service: Monday 12:03 from Czyżew · Mon 9 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
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 100% · 28
- 3–10 min 0% · 0
- 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
- 100% T n=6
- 100% F n=5
- 100% S n=5
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (18 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 |
|---|---|---|---|
| 12:03 | on time | +1 min | |
| 12:08 | ≈ on time | ≈ +1 min | |
| 12:11 | ≈ on time | ≈ +1 min | |
| 12:16 | ≈ on time | ≈ +1 min | |
| 12:20 / 12:21 | ≈ on time | ≈ +1 min | |
| 12:23 / 12:24 | ≈ on time | ≈ +1 min | |
| 12:27 / 12:28 | ≈ on time | ≈ +1 min | |
| 12:32 | ≈ on time | ≈ +1 min | |
| 12:36 | ≈ on time | ≈ +1 min | |
| 12:39 / 12:40 | ≈ on time | ≈ +1 min | |
| 12:42 | ≈ on time | ≈ +1 min | |
| 12:45 / 12:46 | ≈ on time | ≈ +1 min | |
| 12:48 / 12:49 | ≈ on time | ≈ +1 min | |
| 12:52 | ≈ on time | ≈ +1 min | |
| 12:54 / 12:55 | ≈ on time | ≈ +1 min | |
| 12:58 | ≈ on time | ≈ +1 min | |
| 13:01 | ≈ on time | ≈ +1 min | |
| 13:05 | 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 7 Nov | Białystok 13:04 | 0 min | — |
| Fri 6 Nov | Białystok 13:04 | 0 min | — |
| Thu 5 Nov | Białystok 13:04 | 0 min | — |
| Wed 4 Nov | Białystok 13:04 | 0 min | — |
| Tue 3 Nov | Białystok 13:05 | 0 min | — |
| Mon 2 Nov | Białystok 13:04 | No data | — |
| Sat 31 Oct | Białystok 13:06 | 0 min | — |
| Fri 30 Oct | Białystok 13:06 | 0 min | — |
| Thu 29 Oct | Białystok 13:06 | 0 min | — |
| Wed 28 Oct | Białystok 13:06 | 0 min | — |
| Tue 27 Oct | Białystok 13:06 | 0 min | — |
| Mon 26 Oct | Białystok 13:06 | 0 min | — |
| Sat 24 Oct | Białystok 13:06 | No data | — |
| Fri 23 Oct | Białystok 13:06 | No data | — |
| Thu 22 Oct | Białystok 13:06 | No data | — |
| Wed 21 Oct | Białystok 13:06 | No data | — |
| Tue 20 Oct | Białystok 13:07 | No data | — |
| Mon 19 Oct | Białystok 13:07 | No data | — |
| Sat 17 Oct | Białystok 13:06 | 0 min | — |
| Fri 16 Oct | Białystok 13:06 | 0 min | — |
| Thu 15 Oct | Białystok 13:06 | 0 min | — |
| Wed 14 Oct | Białystok 13:07 | 0 min | — |
| Tue 13 Oct | Białystok 13:06 | 0 min | — |
| Mon 12 Oct | Białystok 13:06 | 0 min | — |
| Sat 10 Oct | Białystok 13:07 | +1 min | +1 min |
| Fri 9 Oct | Białystok 13:06 | 0 min | — |
| Thu 8 Oct | Białystok 13:06 | 0 min | — |
| Wed 7 Oct | Białystok 13:06 | 0 min | — |
| Tue 6 Oct | Białystok 13:06 | 0 min | — |
| Mon 5 Oct | Białystok 13:06 | 0 min | — |