Train VR 427 Tampere – Keuruu

Tampere 16:16 → Keuruu 17:57 Daily 1 h 41 min · 8 stops VR (Finland)

✓ Today’s run finished

Today it reached Keuruu at 17:57 0 min

  1. Tampere16:16
  2. Orivesi16:41
  3. Orivesi keskusta16:45
  4. Vilppula17:16
  5. Kolho17:24
  6. Haapamäki17:35
  7. Keuruu17:57

Next service: tomorrow 16:16 from Tampere · Thu 19 Nov

Next departure 16:16 tomorrow · Tampere
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
90%
78/87 runs under 3 min
RT coverage: 87 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Keuruu, 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 25 Sept Max en route +21 min · last fix heading to — +19 min
  • Fri 9 Oct Max en route +20 min · last fix heading to Keuruu +17 min
  • Thu 1 Oct Max en route +20 min · last fix heading to — +16 min
  • Fri 28 Aug Max en route +15 min · last fix heading to — +15 min
  • Wed 16 Sept Max en route +15 min · last fix heading to — +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 78
  • 3–10 min 5% · 4
  • 10–30 min 6% · 5
  • 30+ min 0% · 0

On-time by weekday

  • 85% M n=13
  • 100% T n=13
  • 92% W n=13
  • 92% T n=12
  • 69% F n=13
  • 91% S n=11
  • 100% S n=12

Stops and timetable

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

Last 90 days, 87 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
16:16on time +1 min
16:41 / 16:42≈ on time ≈ +2 min
16:45 / 16:46≈ on time ≈ +2 min
16:56 / 16:57≈ on time ≈ +2 min
17:16 / 17:17≈ on time ≈ +2 min
17:24 / 17:25≈ on time ≈ +2 min
17:35 / 17:43≈ on time ≈ +3 min
17:57on time +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
Wed 18 NovKeuruu 18:250 min—
Tue 17 NovKeuruu 18:240 min—
Mon 16 NovKeuruu 18:29+3 min+5 min
Sun 15 NovKeuruu 18:270 min+1 min
Sat 14 NovKeuruu 18:240 min—
Fri 13 NovKeuruu 18:240 min+1 min
Thu 12 NovKeuruu 18:240 min—
Wed 11 NovKeuruu 18:270 min+1 min
Tue 10 NovKeuruu 18:240 min+1 min
Mon 9 NovKeuruu 18:240 min—
Sun 8 NovKeuruu 18:240 min+1 min
Sat 7 NovKeuruu 18:240 min+1 min
Fri 6 NovKeuruu 18:240 min—
Thu 5 NovKeuruu 18:240 min+1 min
Wed 4 NovKeuruu 18:240 min—
Tue 3 NovKeuruu 18:280 min+1 min
Mon 2 NovKeuruu 18:280 min—
Sun 1 NovKeuruu 18:29+1 min+2 min
Sat 31 OctKeuruu 18:330 min+3 min
Fri 30 OctKeuruu 18:33+3 min+4 min
Thu 29 OctKeuruu 18:270 min+2 min
Wed 28 OctKeuruu 18:27+1 min+3 min
Tue 27 OctKeuruu 18:260 min—
Mon 26 OctKeuruu 18:250 min+1 min
Sun 25 OctKeuruu 18:27+1 min+5 min
Sat 24 OctKeuruu 18:250 min—
Fri 23 OctKeuruu 18:300 min+1 min
Thu 22 OctKeuruu 18:260 min+2 min
Wed 21 OctKeuruu 18:270 min+2 min
Tue 20 OctKeuruu 18:270 min+1 min