Train VR 910 Tampere – Turku

Tampere 09:10 → Turku 10:50 Mon, Tue, Wed, Thu, Fri, Sat 1 h 40 min · 5 stops VR (Finland)

✓ Today’s run finished

Today it reached Turku at 10:52 +2 min

  1. Tampere09:10
  2. Toijala09:32
  3. Humppila09:59
  4. Loimaa10:12
  5. Turku10:50

Next service: tomorrow 09:10 from Tampere · Sat 7 Nov

Next departure 09:10 tomorrow · Tampere
On-time · 30 days
89%
25/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
86%
74/86 runs under 3 min
RT coverage: 86 full · 0 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Turku, 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 6 Oct Max en route +36 min · last fix heading to Turku +35 min
  • Sat 31 Oct Max en route +33 min · last fix heading to Turku +33 min
  • Sun 23 Aug Max en route +20 min · last fix heading to — +20 min
  • Sat 22 Aug Max en route +14 min · last fix heading to — +11 min
  • Fri 18 Sept Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 6% · 5
  • On time 80% · 69
  • 3–10 min 9% · 8
  • 10–30 min 2% · 2
  • 30+ min 2% · 2

On-time by weekday

  • 100% M n=13
  • 85% T n=13
  • 92% W n=13
  • 92% T n=12
  • 83% F n=12
  • 73% S n=11
  • 75% S n=12

Stops and timetable

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

Last 90 days, 86 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
09:10+1 min +1 min
09:32 / 09:35≈ +1 min ≈ +1 min
09:59 / 10:00≈ +1 min ≈ +2 min
10:12 / 10:13≈ on time ≈ +3 min
10:50on time +4 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 NovTurku 11:19+2 min+3 min
Thu 5 NovTurku 11:22+4 min+4 min
Wed 4 NovTurku 11:19+1 min—
Tue 3 NovTurku 11:19+1 min—
Mon 2 NovTurku 11:190 min—
Sun 1 NovTurku 11:17−2 min—
Sat 31 OctTurku 11:52+33 min+33 min
Fri 30 OctTurku 12:240 min—
Thu 29 OctTurku 11:20+1 min+1 min
Wed 28 OctTurku 11:21+2 min+2 min
Tue 27 OctTurku 11:21+1 min—
Mon 26 OctTurku 11:22+2 min+4 min
Sun 25 OctTurku 11:21+1 min—
Sat 24 OctTurku 11:200 min—
Fri 23 OctTurku 11:19−1 min—
Thu 22 OctTurku 11:190 min—
Wed 21 OctTurku 11:200 min—
Tue 20 OctTurku 11:190 min—
Mon 19 OctTurku 11:190 min—
Sun 18 OctTurku 11:21−1 min—
Sat 17 OctTurku 11:190 min—
Fri 16 OctTurku 11:210 min—
Thu 15 OctTurku 11:21+1 min—
Wed 14 OctTurku 11:200 min—
Tue 13 OctTurku 11:200 min—
Mon 12 OctTurku 11:20+1 min—
Sun 11 Oct— 11:20No data—
Sat 10 Oct— 11:17No data—
Fri 9 OctTurku 11:27+7 min+8 min
Thu 8 OctTurku 11:20+1 min—