Train VR 461 Tampere – Pori

Tampere 08:08 → Pori 09:40 Mon, Tue, Wed, Thu, Fri, Sat 1 h 32 min · 8 stops VR (Finland)

Running now · updated 09:19

Between Kokemäki and Harjavalta +1 min

Estimated arrival at Pori 09:41 09:40 · 111 km/h

  1. Tampere08:08
  2. Tesoma08:16
  3. Nokia08:23
  4. Vammala08:53
  5. Kokemäki09:15
  6. Harjavalta09:24
  7. Pori09:40

Today it is running worse than usual: typical arrival delay is +1 min; 88% of the last 25 runs arrived on time.

On-time · 30 days
88%
22/25 runs under 3 min
RT coverage: 24 full · 1 partial · 1 no data
On-time · 90 days
93%
70/75 runs under 3 min
RT coverage: 74 full · 1 partial · 2 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

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

  • Sat 5 Sept Max en route +10 min · last fix heading to — +9 min
  • Sat 31 Oct Max en route +8 min · last fix heading to Pori +8 min
  • Thu 15 Oct Max en route +9 min · last fix heading to Pori +8 min
  • Fri 4 Sept Max en route +5 min · last fix heading to — +3 min
  • Thu 8 Oct Max en route +3 min · last fix heading to Pori +3 min

Distribution · 90 days

75 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 1% · 1
  • On time 92% · 69
  • 3–10 min 7% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=13
  • 100% T n=13
  • 100% W n=13
  • 83% T n=12
  • 92% F n=12
  • 83% S n=12
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 stops).

Last 90 days, 75 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.

StopSched.Usually 9 days in 10Today
08:08on time on timePassed
08:16 / 08:17≈ on time ≈ on timePassed
08:23 / 08:24≈ on time ≈ +1 minPassed
08:42 / 08:43≈ on time ≈ +1 minPassed
08:53 / 08:54≈ on time ≈ +1 minPassed
09:15 / 09:16≈ on time ≈ +1 minPassed
09:24 / 09:25≈ on time ≈ +1 minNext
09:40+1 min +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 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

DateLast stopFinalMax
Thu 5 NovKokemäki 09:14Partial coverage+1 min+1 min
Wed 4 NovPori 10:09+1 min+1 min
Tue 3 NovPori 10:09+1 min—
Mon 2 NovPori 10:090 min—
Sat 31 OctPori 10:18+8 min+8 min
Fri 30 OctPori 10:11+1 min+1 min
Thu 29 OctPori 10:10+1 min+1 min
Wed 28 OctPori 10:100 min—
Tue 27 OctPori 10:10+1 min—
Mon 26 OctPori 10:090 min—
Sat 24 OctPori 10:090 min—
Fri 23 OctPori 10:090 min—
Thu 22 OctPori 10:090 min—
Wed 21 OctPori 10:100 min—
Tue 20 OctPori 10:090 min—
Mon 19 OctPori 10:100 min—
Sat 17 OctPori 10:100 min—
Fri 16 OctPori 10:12+2 min+2 min
Thu 15 OctPori 10:17+8 min+9 min
Wed 14 OctPori 10:11+1 min—
Tue 13 OctPori 10:11+2 min+2 min
Mon 12 OctPori 10:11+2 min+2 min
Sat 10 Oct— 10:11No data—
Fri 9 OctPori 10:11+1 min+2 min
Thu 8 OctPori 10:12+3 min+3 min
Wed 7 OctPori 10:11+2 min+2 min
Tue 6 OctPori 10:11+1 min+1 min
Mon 5 OctPori 10:10+1 min+1 min
Sat 3 Oct— 10:10+1 min+1 min
Fri 2 Oct— 10:11+1 min—