REG 85200 Słupsk – Elbląg
Alerts for train 85200
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.
Running now · updated 07:00
Position estimated from the timetable
Between Pruszcz Gdański and Cieplewo −1 min
Estimated arrival at Elbląg 08:34 · 63 km/h
- Słupsk04:35
- Leśnice05:14
- Gościcino Wejherowskie05:54
- Gdańsk Oliwa06:38
- Pruszcz Gdański06:59
- Cieplewo07:03
- Elbląg08:34
Today it is running no worse than usual: typical arrival delay is 0 min; 91% of the last 22 runs arrived on time.
Last 30 days
Arrival delay at Elbląg, 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 +33 min · last fix heading to Elbląg +33 min
- Sun 1 Nov Max en route +9 min · last fix heading to Elbląg +9 min
- Mon 28 Sept Max en route +5 min · last fix heading to Elbląg +5 min
- Sun 27 Sept Max en route +5 min · last fix heading to Elbląg +5 min
- Fri 25 Sept Max en route +5 min · last fix heading to Elbląg +5 min
Distribution · 90 days
50 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 2% · 1
- On time 70% · 35
- 3–10 min 26% · 13
- 10–30 min 0% · 0
- 30+ min 2% · 1
On-time by weekday
- 71% M n=7
- 75% T n=8
- 78% W n=9
- 75% T n=8
- 63% F n=8
- 80% S n=5
- 60% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (44 stops).
Last 90 days, 50 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 | Today |
|---|---|---|---|---|
| 04:35 | +1 min | +5 min | Passed | |
| 04:41 / 04:42 | ≈ +1 min | ≈ +5 min | Passed | |
| 04:48 / 04:49 | ≈ +1 min | ≈ +5 min | Passed | |
| 04:54 / 04:55 | ≈ +1 min | ≈ +5 min | Passed | |
| 04:58 | ≈ +1 min | ≈ +5 min | Passed | |
| 05:03 | ≈ +1 min | ≈ +5 min | Passed | |
| 05:12 | ≈ +1 min | ≈ +5 min | Passed | |
| 05:14 / 05:15 | ≈ +1 min | ≈ +5 min | Passed | |
| 05:21 / 05:23 | ≈ +1 min | ≈ +5 min | Passed | |
| 05:26 | ≈ +1 min | ≈ +5 min | Passed | |
| 05:31 | ≈ +1 min | ≈ +5 min | Passed | |
| 05:36 | ≈ +1 min | ≈ +5 min | Passed | |
| 05:39 / 05:40 | ≈ +1 min | ≈ +5 min | Passed | |
| 05:43 / 05:50 | ≈ +1 min | ≈ +5 min | Passed | |
| 05:54 / 05:55 | ≈ +1 min | ≈ +5 min | Passed | |
| 05:59 / 06:01 | ≈ +1 min | ≈ +5 min | Passed | |
| 06:08 / 06:09 | ≈ +1 min | ≈ +5 min | Passed | |
| 06:12 / 06:13 | ≈ +1 min | ≈ +5 min | Passed | |
| 06:18 / 06:19 | ≈ +1 min | ≈ +5 min | Passed | |
| 06:24 / 06:26 | ≈ +1 min | ≈ +5 min | Passed | |
| 06:30 / 06:31 | ≈ +1 min | ≈ +5 min | Passed | |
| 06:34 / 06:35 | ≈ +1 min | ≈ +5 min | Passed | |
| 06:38 / 06:39 | ≈ +1 min | ≈ +5 min | Passed | |
| 06:42 / 06:43 | ≈ +1 min | ≈ +5 min | Passed | |
| 06:48 / 06:50 | ≈ +1 min | ≈ +5 min | Passed | |
| 06:53 | ≈ +1 min | ≈ +5 min | Passed | |
| 06:55 / 06:56 | ≈ +1 min | ≈ +5 min | Passed | |
| 06:59 / 07:00 | ≈ +1 min | ≈ +5 min | Passed | |
| 07:03 | ≈ +1 min | ≈ +5 min | ||
| 07:06 | ≈ +1 min | ≈ +5 min | ||
| 07:09 | ≈ +1 min | ≈ +5 min | ||
| 07:11 / 07:12 | ≈ +1 min | ≈ +5 min | ||
| 07:14 / 07:15 | ≈ +1 min | ≈ +5 min | ||
| 07:20 / 07:21 | ≈ +1 min | ≈ +5 min | ||
| 07:24 / 07:25 | ≈ +1 min | ≈ +5 min | ||
| 07:31 / 07:32 | ≈ +1 min | ≈ +5 min | ||
| 07:34 / 07:35 | ≈ +1 min | ≈ +5 min | ||
| 07:38 | ≈ +1 min | ≈ +5 min | ||
| 07:41 / 08:07 | ≈ +1 min | ≈ +5 min | ||
| 08:12 | ≈ +1 min | ≈ +5 min | ||
| 08:17 / 08:18 | ≈ +1 min | ≈ +5 min | ||
| 08:21 | ≈ +1 min | ≈ +5 min | ||
| 08:25 | ≈ +1 min | ≈ +5 min | ||
| 08:34 | +1 min | +5 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 |
|---|---|---|---|
| Wed 11 Nov | Cieplewo 06:59Partial coverage | −1 min | — |
| Tue 10 Nov | Elbląg 08:37 | +2 min | +2 min |
| Mon 9 Nov | Elbląg 08:34 | +1 min | +1 min |
| Sun 8 Nov | Elbląg 08:35 | 0 min | — |
| Sat 7 Nov | Elbląg 08:34 | +1 min | +1 min |
| Fri 6 Nov | Elbląg 09:08 | +33 min | +33 min |
| Thu 5 Nov | Elbląg 08:34 | 0 min | — |
| Wed 4 Nov | Elbląg 08:33 | −2 min | — |
| Tue 3 Nov | Elbląg 08:34 | 0 min | — |
| Mon 2 Nov | Elbląg 08:34 | 0 min | +9 min |
| Sun 1 Nov | Elbląg 08:45 | +9 min | +9 min |
| Sat 31 Oct | Elbląg 08:37 | +2 min | +2 min |
| Fri 30 Oct | Elbląg 08:37 | +2 min | +2 min |
| Thu 29 Oct | Elbląg 08:35 | 0 min | — |
| Wed 28 Oct | Elbląg 08:35 | 0 min | — |
| Tue 27 Oct | Elbląg 08:35 | 0 min | — |
| Mon 26 Oct | Elbląg 08:35 | 0 min | — |
| Sun 25 Oct | Elbląg 08:35 | No data | — |
| Sat 24 Oct | Elbląg 08:37 | No data | — |
| Fri 23 Oct | Elbląg 08:37 | No data | — |
| Thu 22 Oct | Elbląg 08:37 | No data | — |
| Wed 21 Oct | Elbląg 08:37 | No data | — |
| Tue 20 Oct | Elbląg 08:37 | No data | — |
| Mon 19 Oct | Elbląg 08:36 | −1 min | — |
| Sun 18 Oct | Elbląg 08:38 | No data | — |
| Sat 17 Oct | Elbląg 08:37 | No data | — |
| Fri 16 Oct | Elbląg 08:37 | 0 min | — |
| Thu 15 Oct | Elbląg 08:36 | −1 min | — |
| Wed 14 Oct | Elbląg 08:36 | −1 min | — |
| Tue 13 Oct | Elbląg 08:37 | 0 min | — |