IC 51102 Olsztyn Główny – Białystok
Alerts for train 51102
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line IC.
It has not run yet today
Last recorded run: Sunday 15 November 0 min
Next service: today 19:08 from Olsztyn Główny · Mon 16 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
- Fri 6 Nov Max en route +57 min · last fix heading to Białystok +57 min
- Sat 14 Nov Max en route +24 min · last fix heading to Białystok +24 min
- Fri 13 Nov Max en route +24 min · last fix heading to Białystok +24 min
- Thu 12 Nov Max en route +24 min · last fix heading to Białystok +24 min
- Fri 18 Sept Max en route +27 min · last fix heading to Łapy +21 min
Distribution · 90 days
47 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 62% · 29
- 3–10 min 21% · 10
- 10–30 min 15% · 7
- 30+ min 2% · 1
On-time by weekday
- 60% M n=5
- 83% T n=6
- 83% W n=6
- 50% T n=6
- 38% F n=8
- 56% S n=9
- 71% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 47 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 |
|---|---|---|---|
| 19:08 | on time | +10 min | |
| 19:48 / 19:56 | ≈ on time | ≈ +11 min | |
| 20:13 / 20:14 | ≈ on time | ≈ +12 min | |
| 20:28 / 20:30 | ≈ on time | ≈ +13 min | |
| 21:05 / 21:14 | ≈ on time | ≈ +14 min | |
| 21:31 | ≈ on time | ≈ +15 min | |
| 21:43 / 21:51 | ≈ on time | ≈ +15 min | |
| 22:53 / 22:54 | ≈ on time | ≈ +19 min | |
| 23:06 / 23:07 | ≈ on time | ≈ +20 min | |
| 23:11 | on time | +20 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 15 Nov | Białystok 23:12 | 0 min | — |
| Sat 14 Nov | Białystok 23:34 | +24 min | +24 min |
| Fri 13 Nov | Białystok 23:34 | +24 min | +24 min |
| Thu 12 Nov | Białystok 23:34 | +24 min | +24 min |
| Wed 11 Nov | Białystok 23:13 | +1 min | +1 min |
| Tue 10 Nov | Białystok 23:15 | +4 min | +4 min |
| Mon 9 Nov | Białystok 23:12 | 0 min | — |
| Sun 8 Nov | Białystok 23:12 | 0 min | — |
| Sat 7 Nov | Białystok 23:12 | 0 min | — |
| Fri 6 Nov | Białystok 00:09 | +57 min | +57 min |
| Thu 5 Nov | Białystok 23:17 | +5 min | +5 min |
| Wed 4 Nov | Białystok 23:12 | 0 min | — |
| Tue 3 Nov | Białystok 23:13 | 0 min | — |
| Mon 2 Nov | Białystok 23:18 | +6 min | +6 min |
| Sun 1 Nov | Białystok 23:17 | +5 min | +5 min |
| Sat 31 Oct | Białystok 23:13 | 0 min | — |
| Fri 30 Oct | Białystok 23:12 | 0 min | — |
| Thu 29 Oct | Białystok 23:12 | 0 min | — |
| Wed 28 Oct | Białystok 23:12 | 0 min | — |
| Tue 27 Oct | Białystok 23:14 | +2 min | +2 min |
| Mon 26 Oct | Białystok 23:18 | +5 min | +5 min |
| Sun 25 Oct | Białystok 23:12 | No data | — |
| Sat 24 Oct | Białystok 23:13 | No data | — |
| Fri 23 Oct | Białystok 23:13 | No data | — |
| Thu 22 Oct | Białystok 23:12 | No data | — |
| Wed 21 Oct | Białystok 23:12 | No data | — |
| Tue 20 Oct | Białystok 23:12 | No data | — |
| Mon 19 Oct | Białystok 23:12 | No data | — |
| Sun 18 Oct | Białystok 23:13 | 0 min | — |
| Sat 17 Oct | Białystok 23:12 | 0 min | — |