REG 87600 Kostrzyn – Rzepin
Alerts for train 87600
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 Rzepin at 05:51 +1 min
- Kostrzyn05:21
- Ługi Górzyckie05:27
- Górzyca05:30
- Radów05:38
- Kowalów05:41
- Drzeńsko05:44
- Rzepin05:50
Next service: Monday 05:21 from Kostrzyn · Mon 16 Nov
Last 30 days
Arrival delay at Rzepin, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Tue 1 Sept Max en route +40 min · last fix heading to Kostrzyn +40 min
- Fri 9 Oct Max en route +6 min · last fix heading to Rzepin +6 min
- Sat 7 Nov Max en route +3 min · last fix heading to Rzepin +3 min
Distribution · 90 days
34 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 31
- 3–10 min 6% · 2
- 10–30 min 0% · 0
- 30+ min 3% · 1
On-time by weekday
- 100% M n=7
- 83% T n=6
- 100% W n=5
- 100% T n=5
- 80% F n=5
- 83% S n=6
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 34 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:21 | on time | +2 min | |
| 05:27 | ≈ on time | ≈ +2 min | |
| 05:30 | ≈ on time | ≈ +2 min | |
| 05:34 | ≈ on time | ≈ +2 min | |
| 05:38 | ≈ on time | ≈ +2 min | |
| 05:41 / 05:42 | ≈ on time | ≈ +2 min | |
| 05:44 | ≈ on time | ≈ +2 min | |
| 05:50 | on time | +2 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 | Rzepin 05:52 | +1 min | +1 min |
| Fri 13 Nov | Rzepin 05:52 | +1 min | +1 min |
| Thu 12 Nov | Rzepin 05:49 | 0 min | +1 min |
| Tue 10 Nov | Rzepin 05:52 | 0 min | — |
| Mon 9 Nov | Rzepin 05:49 | 0 min | — |
| Sat 7 Nov | Rzepin 05:54 | +3 min | +3 min |
| Fri 6 Nov | Rzepin 05:49 | 0 min | — |
| Thu 5 Nov | Rzepin 05:49 | 0 min | — |
| Wed 4 Nov | Rzepin 05:49 | 0 min | — |
| Tue 3 Nov | Rzepin 05:49 | 0 min | — |
| Mon 2 Nov | Rzepin 05:49 | 0 min | — |
| Sat 31 Oct | Rzepin 05:53 | +2 min | +2 min |
| Fri 30 Oct | Rzepin 05:53 | +2 min | +2 min |
| Thu 29 Oct | Rzepin 05:51 | 0 min | — |
| Wed 28 Oct | Rzepin 05:51 | 0 min | — |
| Tue 27 Oct | Rzepin 05:51 | 0 min | — |
| Mon 26 Oct | Rzepin 05:51 | 0 min | — |
| Sat 24 Oct | Rzepin 05:49 | No data | — |
| Fri 23 Oct | Rzepin 05:49 | No data | — |
| Thu 22 Oct | Rzepin 05:49 | No data | — |
| Wed 21 Oct | Rzepin 05:49 | No data | — |
| Tue 20 Oct | Rzepin 05:49 | No data | — |
| Mon 19 Oct | Rzepin 05:49 | 0 min | — |
| Sat 17 Oct | Rzepin 05:49 | 0 min | — |
| Fri 16 Oct | Rzepin 05:50 | 0 min | — |
| Thu 15 Oct | Rzepin 05:49 | 0 min | — |
| Wed 14 Oct | Rzepin 05:49 | 0 min | — |
| Tue 13 Oct | Rzepin 05:49 | 0 min | — |
| Mon 12 Oct | Rzepin 05:50 | 0 min | — |
| Sat 10 Oct | Rzepin 05:49 | 0 min | — |