Train VR 165 Helsinki – Tampere

Helsinki 08:00 → Tampere 09:53 Mon, Tue, Wed, Thu, Fri 1 h 53 min · 8 stops VR (Finland)

✓ Today’s run finished

Today it reached Tampere at 09:53 0 min

  1. Helsinki08:00
  2. Pasila08:05
  3. Tikkurila08:14
  4. Hämeenlinna09:09
  5. Toijala09:30
  6. Lempäälä09:40
  7. Tampere09:53
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
89%
57/64 runs under 3 min
RT coverage: 64 full · 0 partial · 1 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Fri 9 Oct Max en route +10 min · last fix heading to Pori +9 min
  • Wed 4 Nov Max en route +6 min · last fix heading to Tampere +6 min
  • Mon 5 Oct Max en route +6 min · last fix heading to Pori +6 min
  • Fri 25 Sept Max en route +4 min · last fix heading to — +4 min
  • Wed 30 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 5% · 3
  • On time 84% · 54
  • 3–10 min 11% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=13
  • 100% T n=13
  • 83% W n=12
  • 100% T n=13
  • 69% 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, 64 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:00on time +1 min
08:05 / 08:06≈ on time ≈ +1 min
08:14 / 08:16≈ on time ≈ +1 min
08:50 / 08:52≈ on time ≈ +1 min
09:09 / 09:11≈ on time ≈ +2 min
09:30 / 09:31≈ on time ≈ +2 min
09:40 / 09:41≈ +1 min ≈ +3 min
09:53+1 min +3 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 20 NovTampere 10:190 min—
Thu 19 NovTampere 10:24+1 min—
Wed 18 NovTampere 10:24+1 min—
Tue 17 NovTampere 10:24+2 min+2 min
Mon 16 NovTampere 10:220 min—
Fri 13 NovTampere 10:24+2 min+2 min
Thu 12 NovTampere 10:24+1 min+1 min
Wed 11 NovTampere 10:190 min—
Tue 10 NovTampere 10:16+2 min+2 min
Mon 9 NovTampere 10:190 min—
Fri 6 NovTampere 10:24+1 min—
Thu 5 NovTampere 10:23+1 min+1 min
Wed 4 NovTampere 09:49+6 min+6 min
Tue 3 NovTampere 10:24+2 min+2 min
Mon 2 NovTampere 10:24+3 min+3 min
Fri 30 OctPori 12:19+1 min—
Thu 29 OctPori 12:20+1 min+4 min
Wed 28 OctPori 12:19+3 min+3 min
Tue 27 OctPori 12:27−1 min—
Mon 26 OctPori 12:18+1 min—
Fri 23 OctPori 12:22+3 min+3 min
Thu 22 OctPori 12:190 min+2 min
Wed 21 OctPori 12:200 min—
Tue 20 OctPori 12:180 min—
Mon 19 OctPori 12:16−1 min+1 min
Fri 16 OctPori 12:36+1 min—
Thu 15 OctPori 12:180 min—
Wed 14 OctPori 12:35−1 min—
Tue 13 OctPori 12:180 min—
Mon 12 OctPori 12:19+1 min+2 min