Train VR 945 Helsinki – Turku

Helsinki 08:35 → Turku 10:39 Daily 2 h 04 min · 7 stops VR (Finland)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 08:35 from Helsinki · Sat 7 Nov

Next departure 08:35 today · Helsinki
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 24 full · 2 partial · 2 no data
On-time · 90 days
99%
83/84 runs under 3 min
RT coverage: 82 full · 2 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sat 17 Oct Max en route +7 min · last fix heading to Turku +7 min

Distribution · 90 days

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

  • Early 1% · 1
  • On time 98% · 82
  • 3–10 min 1% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 85 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:35on time +1 min
08:40 / 08:41≈ on time ≈ +1 min
08:47 / 08:48≈ on time ≈ +1 min
09:35 / 09:37≈ on time ≈ on time
10:06 / 10:07≈ on time ≈ on time
10:33 / 10:34≈ on time ≈ on time
10:39on time on time

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:080 min—
Thu 5 NovTurku 11:09−1 min—
Wed 4 NovTurku 11:04−1 min—
Tue 3 NovTurku 11:090 min—
Mon 2 NovTurku 11:080 min—
Sun 1 NovTurku 11:08−1 min—
Sat 31 OctTurku 11:090 min—
Fri 30 OctTurku 11:090 min—
Thu 29 OctTurku 11:100 min—
Tue 27 OctKupittaa 11:09Partial coverage+1 min+1 min
Mon 26 OctTurku 11:090 min—
Sun 25 OctTurku 11:07−1 min—
Sat 24 OctTurku 11:110 min—
Fri 23 OctTurku 11:07−1 min+1 min
Thu 22 OctTurku 11:10−1 min—
Wed 21 OctTurku 11:080 min—
Tue 20 OctTurku 11:100 min—
Mon 19 OctTurku 11:08−1 min—
Sun 18 OctTurku 11:09−1 min—
Sat 17 OctTurku 11:16+7 min+7 min
Fri 16 OctTurku 11:080 min—
Thu 15 OctTurku 11:07−1 min—
Wed 14 OctKupittaa 11:12Partial coverage+1 min+2 min
Tue 13 OctTurku 11:070 min+1 min
Mon 12 OctTurku 11:08−1 min—
Sun 11 Oct— 11:08No data—
Sat 10 Oct— 11:11No data—
Fri 9 OctTurku 11:080 min—
Thu 8 OctTurku 11:080 min—
Wed 7 OctTurku 11:08−1 min+1 min