Train VR 421 Tampere – Keuruu

Tampere 08:06 → Keuruu 09:47 Mon, Tue, Wed, Thu, Fri, Sat 1 h 41 min · 8 stops VR (Finland)

✓ Today’s run finished

Today it reached Keuruu at 09:49 +2 min

  1. Tampere08:06
  2. Orivesi08:31
  3. Orivesi keskusta08:35
  4. Vilppula09:06
  5. Kolho09:14
  6. Haapamäki09:25
  7. Keuruu09:47

Next service: tomorrow 08:06 from Tampere · Tue 17 Nov

Next departure 08:06 tomorrow · Tampere
On-time · 30 days
80%
20/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
On-time · 90 days
71%
50/70 runs under 3 min
RT coverage: 70 full · 0 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Mon 7 Sept Max en route +22 min · last fix heading to — +22 min
  • Sat 5 Sept Max en route +15 min · last fix heading to — +12 min
  • Thu 8 Oct Max en route +12 min · last fix heading to Keuruu +11 min
  • Mon 31 Aug Max en route +11 min · last fix heading to — +10 min
  • Wed 19 Aug Max en route +10 min · last fix heading to — +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 71% · 50
  • 3–10 min 23% · 16
  • 10–30 min 6% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 78% M n=9
  • 83% T n=12
  • 67% W n=12
  • 58% T n=12
  • 77% F n=13
  • 67% S n=12
  • — S n=0

Stops and timetable

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

Last 90 days, 70 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:06on time +2 min
08:31 / 08:32≈ on time ≈ +3 min
08:35 / 08:36≈ on time ≈ +3 min
08:46 / 08:47≈ on time ≈ +4 min
09:06 / 09:07≈ +1 min ≈ +5 min
09:14 / 09:15≈ +1 min ≈ +6 min
09:25 / 09:33≈ +1 min ≈ +6 min
09:47on time +7 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 16 NovKeuruu 10:18+2 min+6 min
Sat 14 NovKeuruu 10:200 min+1 min
Fri 13 NovKeuruu 10:170 min+1 min
Thu 12 NovKeuruu 10:140 min—
Wed 11 NovKeuruu 10:24+2 min+3 min
Tue 10 NovKeuruu 10:16+1 min+3 min
Mon 9 NovKeuruu 10:170 min+2 min
Sat 7 NovKeuruu 10:18+2 min+3 min
Fri 6 NovKeuruu 10:140 min—
Thu 5 NovKeuruu 10:140 min+1 min
Wed 4 NovKeuruu 10:19+4 min+5 min
Tue 3 NovKeuruu 10:180 min+1 min
Mon 2 NovKeuruu 10:140 min—
Sat 31 OctKeuruu 10:23+5 min+11 min
Fri 30 OctKeuruu 10:17+1 min+1 min
Thu 29 OctKeuruu 10:20+4 min+5 min
Wed 28 OctKeuruu 10:17+2 min+2 min
Tue 27 OctKeuruu 10:21+5 min+9 min
Mon 26 OctKeuruu 10:170 min+1 min
Sat 24 OctKeuruu 10:150 min+1 min
Fri 23 OctKeuruu 10:170 min+1 min
Thu 22 OctKeuruu 10:22+6 min+8 min
Wed 21 OctKeuruu 10:19+1 min+7 min
Tue 20 OctKeuruu 10:160 min+3 min
Mon 19 OctKeuruu 10:150 min+2 min
Sat 17 OctKeuruu 10:170 min+1 min
Fri 16 OctKeuruu 10:17+1 min+2 min
Thu 15 OctKeuruu 10:160 min+2 min
Wed 14 OctKeuruu 10:18+2 min+8 min
Tue 13 OctKeuruu 10:180 min+3 min