Train VR 471 Tampere – Pori
It has not run yet today
Last recorded run: Wednesday 4 November +1 min
Next service: today 18:11 from Tampere · Thu 5 Nov
Last 30 days
Arrival delay at Pori, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 16 Aug Max en route +18 min · last fix heading to — +18 min
- Mon 5 Oct Max en route +14 min · last fix heading to Vammala +13 min
- Sun 23 Aug Max en route +13 min · last fix heading to — +13 min
- Wed 14 Oct Max en route +12 min · last fix heading to Pori +12 min
- Sun 9 Aug Max en route +18 min · last fix heading to — +12 min
Distribution · 90 days
86 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 81% · 70
- 3–10 min 9% · 8
- 10–30 min 9% · 8
- 30+ min 0% · 0
On-time by weekday
- 85% M n=13
- 85% T n=13
- 69% W n=13
- 92% T n=12
- 91% F n=11
- 83% S n=12
- 67% S n=12
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 87 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 |
|---|---|---|---|
| 18:11 | on time | +2 min | |
| 18:19 / 18:20 | ≈ on time | ≈ +2 min | |
| 18:26 / 18:27 | ≈ on time | ≈ +2 min | |
| 18:44 / 18:45 | ≈ +1 min | ≈ +4 min | |
| 18:55 / 18:58 | ≈ +1 min | ≈ +5 min | |
| 19:19 / 19:20 | ≈ +1 min | ≈ +7 min | |
| 19:28 / 19:29 | ≈ +1 min | ≈ +7 min | |
| 19:44 | +1 min | +9 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 11 July 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 4 Nov | Pori 20:14 | +1 min | +1 min |
| Tue 3 Nov | Pori 20:14 | +1 min | +1 min |
| Mon 2 Nov | Pori 20:14 | +1 min | +2 min |
| Sun 1 Nov | Pori 20:14 | +1 min | +2 min |
| Sat 31 Oct | Pori 20:15 | +2 min | +2 min |
| Fri 30 Oct | Pori 20:16 | +2 min | +2 min |
| Thu 29 Oct | Pori 20:17 | +3 min | +3 min |
| Wed 28 Oct | Pori 20:22 | +9 min | +9 min |
| Tue 27 Oct | Pori 20:13 | 0 min | — |
| Mon 26 Oct | Pori 20:16 | +2 min | +2 min |
| Sun 25 Oct | Pori 20:15 | +1 min | +1 min |
| Sat 24 Oct | Pori 20:14 | 0 min | — |
| Fri 23 Oct | Pori 20:18 | +6 min | +7 min |
| Thu 22 Oct | Pori 20:14 | +1 min | +2 min |
| Wed 21 Oct | Pori 20:15 | +2 min | +3 min |
| Tue 20 Oct | Pori 20:19 | +6 min | +6 min |
| Mon 19 Oct | Pori 20:13 | 0 min | — |
| Sun 18 Oct | Pori 20:14 | 0 min | +3 min |
| Sat 17 Oct | Pori 20:25 | +12 min | +16 min |
| Fri 16 Oct | Pori 20:14 | 0 min | — |
| Thu 15 Oct | Pori 20:16 | +2 min | +3 min |
| Wed 14 Oct | Pori 20:29 | +12 min | +12 min |
| Tue 13 Oct | Pori 20:21 | +8 min | +11 min |
| Mon 12 Oct | Pori 20:15 | +1 min | +1 min |
| Sun 11 Oct | — 20:26 | No data | — |
| Sat 10 Oct | — 20:16 | No data | — |
| Fri 9 Oct | Pori 20:15 | 0 min | — |
| Thu 8 Oct | Pori 20:15 | +1 min | +1 min |
| Wed 7 Oct | Pori 20:15 | +1 min | +1 min |
| Tue 6 Oct | Pori 20:16 | +1 min | +3 min |