Train VR 476 Pori – Tampere

Pori 08:04 → Tampere 09:39 Mon, Tue, Wed, Thu, Fri 1 h 35 min · 8 stops VR (Finland)

✓ Today’s run finished

Today it reached Tampere at 09:39 −1 min

  1. Pori08:04
  2. Harjavalta08:19
  3. Kokemäki08:28
  4. Karkku09:03
  5. Nokia09:21
  6. Tesoma09:28
  7. Tampere09:39

Next service: tomorrow 08:04 from Pori · Tue 10 Nov

Next departure 08:04 tomorrow · Pori
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
95%
60/63 runs under 3 min
RT coverage: 63 full · 0 partial · 1 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Tampere, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 18 Aug Max en route +25 min · last fix heading to — +25 min
  • Mon 7 Sept Max en route +8 min · last fix heading to — +8 min
  • Thu 3 Sept Max en route +7 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 16% · 10
  • On time 79% · 50
  • 3–10 min 3% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 63 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
08:04on time +1 min
08:19 / 08:20≈ on time ≈ +1 min
08:28 / 08:29≈ on time ≈ +1 min
08:50 / 08:53≈ on time ≈ on time
09:03 / 09:04≈ on time ≈ on time
09:21 / 09:22≈ on time ≈ on time
09:28 / 09:29≈ on time ≈ +1 min
09:391 min early +1 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
Mon 9 NovTampere 10:09−1 min+2 min
Fri 6 NovTampere 10:08−1 min+1 min
Thu 5 NovTampere 10:07−1 min—
Wed 4 NovTampere 10:09+1 min—
Tue 3 NovTampere 10:09−1 min+1 min
Mon 2 NovTampere 10:09−1 min+2 min
Fri 30 OctTampere 10:08+1 min+1 min
Thu 29 OctTampere 11:090 min+1 min
Wed 28 OctTampere 10:090 min—
Tue 27 OctTampere 10:12+3 min+3 min
Mon 26 OctTampere 10:180 min+1 min
Fri 23 OctTampere 10:090 min+2 min
Thu 22 OctTampere 10:08−1 min—
Wed 21 OctTampere 10:07−1 min+2 min
Tue 20 OctTampere 10:08−1 min+2 min
Mon 19 OctTampere 10:100 min—
Fri 16 OctTampere 10:12+2 min+2 min
Thu 15 OctTampere 10:07−2 min—
Wed 14 OctTampere 10:07−1 min+1 min
Tue 13 OctTampere 10:08−1 min+1 min
Mon 12 OctTampere 10:090 min—
Fri 9 OctTampere 10:090 min+2 min
Thu 8 OctTampere 10:08−1 min+2 min
Wed 7 OctTampere 10:090 min+1 min
Tue 6 OctTampere 10:08−1 min+1 min
Mon 5 OctTampere 10:08−1 min+2 min
Fri 2 Oct— 10:090 min+1 min
Thu 1 Oct— 10:07−1 min+2 min
Wed 30 Sept— 10:080 min+2 min
Tue 29 Sept— 10:09−1 min+1 min