Train VR 477 Tampere – Pori

Tampere 06:00 → Pori 07:47 Mon, Tue, Wed, Thu, Fri 1 h 47 min · 8 stops VR (Finland)

It does not run today

Last recorded run: Friday 6 November +2 min

Next service: tomorrow 06:00 from Tampere · Mon 9 Nov

Next departure 06:00 tomorrow · Tampere
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
95%
59/62 runs under 3 min
RT coverage: 61 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

  • Thu 8 Oct Max en route +6 min · last fix heading to Pori +6 min
  • Wed 4 Nov Max en route +6 min · last fix heading to Pori +6 min
  • Tue 20 Oct Max en route +4 min · last fix heading to Pori +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 59
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 92% T n=13
  • 92% 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
06:00on time +1 min
06:08 / 06:09≈ on time ≈ +1 min
06:15 / 06:16≈ on time ≈ +1 min
06:38 / 06:39≈ on time ≈ +1 min
06:49 / 06:58≈ on time ≈ +1 min
07:19 / 07:20≈ +1 min ≈ +2 min
07:28 / 07:32≈ +1 min ≈ +2 min
07:47+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 08:19+2 min+2 min
Thu 5 NovPori 08:18+1 min+1 min
Wed 4 NovPori 08:23+6 min+6 min
Tue 3 NovPori 08:19+1 min+1 min
Mon 2 NovPori 08:19+2 min+2 min
Fri 30 OctPori 08:27+2 min+3 min
Thu 29 OctPori 08:31+3 min+3 min
Wed 28 OctPori 08:18+1 min+1 min
Tue 27 OctPori 08:170 min+1 min
Mon 26 OctPori 08:29+1 min+3 min
Fri 23 OctPori 08:27+1 min+2 min
Thu 22 OctPori 08:17+1 min+1 min
Wed 21 OctPori 08:17+1 min—
Tue 20 OctPori 08:22+4 min+4 min
Mon 19 OctPori 08:170 min+1 min
Fri 16 OctPori 08:23+1 min+3 min
Thu 15 OctPori 08:17−1 min—
Wed 14 OctPori 08:17+1 min+1 min
Tue 13 OctPori 08:19+2 min+2 min
Mon 12 Oct— 08:19No data—
Fri 9 OctPori 08:19+2 min+2 min
Thu 8 OctPori 08:23+6 min+6 min
Wed 7 OctPori 08:22+2 min+2 min
Tue 6 OctPori 08:18+1 min+2 min
Mon 5 OctPori 08:17+1 min+1 min
Fri 2 Oct— 08:24+2 min+2 min
Thu 1 Oct— 08:17+1 min+8 min
Wed 30 Sept— 08:18+1 min+1 min
Tue 29 Sept— 08:19+1 min+1 min
Mon 28 Sept— 08:29+2 min+2 min