PKM3 77688 Wągrowiec – Wolsztyn
Alerts for train 77688
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line PKM3.
Running now · updated 22:07
Between Tłoki and Adamowo 0 min
Estimated arrival at Wolsztyn 22:14 · 129 km/h
- Wągrowiec19:33
- Łopuchowo19:57
- Czerwonak Osiedle20:23
- Poznań Dębiec20:56
- Tłoki22:06
- Adamowo22:09
- Wolsztyn22:14
Today it is running no worse than usual: typical arrival delay is 0 min; 75% of the last 16 runs arrived on time.
Last 30 days
Arrival delay at Wolsztyn, 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 2 Oct Max en route +13 min · last fix heading to Rostarzewo +13 min
- Thu 29 Oct Max en route +5 min · last fix heading to Wolsztyn +5 min
- Mon 12 Oct Max en route +4 min · last fix heading to Wolsztyn +4 min
- Mon 5 Oct Max en route +5 min · last fix heading to Wolsztyn +4 min
- Sun 18 Oct Max en route +3 min · last fix heading to Wolsztyn +3 min
Distribution · 90 days
24 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 71% · 17
- 3–10 min 25% · 6
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 60% M n=5
- 75% T n=4
- 100% W n=3
- 67% T n=3
- 75% F n=4
- 75% S n=4
- 0% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (37 stops).
Last 90 days, 24 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 |
|---|---|---|---|---|
| 19:33 | on time | +3 min | Passed | |
| 19:39 | ≈ on time | ≈ +3 min | Passed | |
| 19:43 / 19:44 | ≈ on time | ≈ +3 min | Passed | |
| 19:47 / 19:48 | ≈ on time | ≈ +3 min | Passed | |
| 19:52 | ≈ on time | ≈ +3 min | Passed | |
| 19:55 / 19:56 | ≈ on time | ≈ +3 min | Passed | |
| 19:57 / 19:58 | ≈ on time | ≈ +3 min | Passed | |
| 20:02 / 20:03 | ≈ on time | ≈ +3 min | Passed | |
| 20:04 / 20:11 | ≈ on time | ≈ +3 min | Passed | |
| 20:12 / 20:13 | ≈ on time | ≈ +3 min | Passed | |
| 20:16 | ≈ on time | ≈ +3 min | Passed | |
| 20:19 / 20:20 | ≈ on time | ≈ +3 min | Passed | |
| 20:23 | ≈ on time | ≈ +3 min | Passed | |
| 20:25 / 20:26 | ≈ on time | ≈ +3 min | Passed | |
| 20:29 / 20:30 | ≈ on time | ≈ +3 min | Passed | |
| 20:33 / 20:34 | ≈ on time | ≈ +3 min | Passed | |
| 20:37 / 20:38 | ≈ on time | ≈ +3 min | Passed | |
| 20:42 / 20:52 | ≈ on time | ≈ +3 min | Passed | |
| 20:56 / 20:57 | ≈ on time | ≈ +3 min | Passed | |
| 20:59 / 21:00 | ≈ on time | ≈ +3 min | Passed | |
| 21:04 / 21:05 | ≈ on time | ≈ +3 min | Passed | |
| 21:09 | ≈ on time | ≈ +3 min | Passed | |
| 21:12 / 21:13 | ≈ on time | ≈ +3 min | Passed | |
| 21:17 / 21:18 | ≈ on time | ≈ +3 min | Passed | |
| 21:23 / 21:24 | ≈ on time | ≈ +3 min | Passed | |
| 21:29 | ≈ on time | ≈ +3 min | Passed | |
| 21:32 / 21:33 | ≈ on time | ≈ +3 min | Passed | |
| 21:36 | ≈ on time | ≈ +3 min | Passed | |
| 21:39 / 21:40 | ≈ on time | ≈ +3 min | Passed | |
| 21:44 / 21:45 | ≈ on time | ≈ +3 min | Passed | |
| 21:51 | ≈ on time | ≈ +3 min | Passed | |
| 21:55 | ≈ on time | ≈ +4 min | Passed | |
| 21:58 / 21:59 | ≈ on time | ≈ +4 min | Passed | |
| 22:02 / 22:03 | ≈ on time | ≈ +4 min | Passed | |
| 22:06 / 22:07 | ≈ on time | ≈ +4 min | Passed | |
| 22:09 | ≈ on time | ≈ +4 min | ||
| 22:14 | on time | +4 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 |
|---|---|---|---|
| Tue 10 Nov | Tłoki 22:04Partial coverage | 0 min | — |
| Mon 9 Nov | Wolsztyn 22:14 | 0 min | — |
| Sun 8 Nov | Wolsztyn 22:14 | No data | — |
| Sat 7 Nov | Wolsztyn 22:14 | No data | — |
| Fri 6 Nov | Wolsztyn 22:14 | No data | — |
| Thu 5 Nov | Wolsztyn 22:14 | No data | — |
| Wed 4 Nov | Wolsztyn 22:14 | No data | — |
| Tue 3 Nov | Wolsztyn 22:14 | No data | — |
| Mon 2 Nov | Wolsztyn 22:17 | +2 min | +2 min |
| Sun 1 Nov | Wolsztyn 22:14 | No data | — |
| Sat 31 Oct | Wolsztyn 22:16 | 0 min | — |
| Fri 30 Oct | Wolsztyn 22:15 | 0 min | — |
| Thu 29 Oct | Wolsztyn 22:20 | +5 min | +5 min |
| Wed 28 Oct | Wolsztyn 22:15 | 0 min | — |
| Tue 27 Oct | Wolsztyn 22:15 | 0 min | — |
| Mon 26 Oct | Wolsztyn 22:16 | 0 min | — |
| Sun 25 Oct | Wolsztyn 22:16 | No data | — |
| Sat 24 Oct | Wolsztyn 22:16 | No data | — |
| Fri 23 Oct | Wolsztyn 22:16 | No data | — |
| Thu 22 Oct | Wolsztyn 22:15 | No data | — |
| Wed 21 Oct | Wolsztyn 22:15 | No data | — |
| Tue 20 Oct | Wolsztyn 22:15 | No data | — |
| Mon 19 Oct | Wolsztyn 22:15 | No data | — |
| Sun 18 Oct | Wolsztyn 22:18 | +3 min | +3 min |
| Sat 17 Oct | Wolsztyn 22:18 | +3 min | +3 min |
| Fri 16 Oct | Wolsztyn 22:15 | 0 min | — |
| Thu 15 Oct | Wolsztyn 22:16 | 0 min | — |
| Wed 14 Oct | Wolsztyn 22:15 | 0 min | — |
| Tue 13 Oct | Wolsztyn 22:16 | +1 min | +1 min |
| Mon 12 Oct | Wolsztyn 22:19 | +4 min | +4 min |