Train VR 463 Tampere – Pori

Tampere 10:11 → Pori 11:48 Mon, Tue, Wed, Thu, Fri 1 h 37 min · 8 stops VR (Finland)

✓ Today’s run finished

Today it reached Pori at 11:50 +2 min

  1. Tampere10:11
  2. Tesoma10:19
  3. Nokia10:26
  4. Vammala11:01
  5. Kokemäki11:23
  6. Harjavalta11:31
  7. Pori11:48

Next service: Monday 10:11 from Tampere · Mon 9 Nov

Next departure 10:11 Monday · Tampere
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 5 full · 0 partial · 0 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 15 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 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

  • Mon 2 Nov Max en route +6 min · last fix heading to Pori +4 min

Distribution · 90 days

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

  • Early 7% · 1
  • On time 87% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=3
  • 100% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 15 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 10
10:11on time +1 min
10:19 / 10:20≈ on time ≈ +1 min
10:26 / 10:27≈ on time ≈ +1 min
10:44 / 10:45≈ on time ≈ +1 min
11:01 / 11:02≈ on time ≈ +1 min
11:23 / 11:24≈ on time ≈ +2 min
11:31 / 11:32≈ on time ≈ +2 min
11:48+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
Fri 6 NovPori 12:24+2 min+2 min
Thu 5 NovPori 12:290 min+1 min
Wed 4 NovPori 12:180 min—
Tue 3 NovPori 12:240 min—
Mon 2 NovPori 12:22+4 min+6 min
Fri 21 Aug— 12:23+1 min—
Thu 20 Aug— 12:19+1 min—
Wed 19 Aug— 12:24+2 min+2 min
Tue 18 Aug— 12:16−1 min—
Mon 17 Aug— 12:21−1 min—
Fri 14 Aug— 12:20+1 min+1 min
Thu 13 Aug— 12:19+1 min—
Wed 12 Aug— 12:16−1 min—
Tue 11 Aug— 12:20+1 min—
Mon 10 Aug— 12:180 min—