Z 9839 Helsinki – Lahti

View line Z

Helsinki 12:45 → Lahti 13:50 Mon, Tue, Wed, Thu, Fri, Sat 1 h 05 min · 8 stops VR (Finland)

✓ Today’s run finished

Today it reached Lahti at 14:00 +10 min

  1. Helsinki12:45
  2. Pasila12:49
  3. Tikkurila12:58
  4. Haarajoki13:14
  5. Mäntsälä13:24
  6. Henna13:35
  7. Lahti13:50
On-time · 30 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
95%
84/88 runs under 3 min
RT coverage: 88 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Lahti, 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 7 Nov Max en route +10 min · last fix heading to Lahti +10 min
  • Tue 13 Oct Max en route +5 min · last fix heading to Lahti +5 min
  • Sat 29 Aug Max en route +4 min · last fix heading to — +4 min
  • Mon 5 Oct Max en route +4 min · last fix heading to Lahti +4 min

Distribution · 90 days

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

  • Early 5% · 4
  • On time 91% · 80
  • 3–10 min 3% · 3
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 88 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
12:45on time +1 min
12:49 / 12:50≈ on time ≈ +1 min
12:58 / 12:59≈ on time ≈ +1 min
13:07 / 13:08≈ on time ≈ +1 min
13:14 / 13:15≈ on time ≈ +1 min
13:24 / 13:25≈ on time ≈ +1 min
13:35 / 13:36≈ on time ≈ +2 min
13:50on time +2 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
Sat 7 NovLahti 14:29+10 min+10 min
Fri 6 NovLahti 14:190 min—
Thu 5 NovLahti 14:190 min—
Wed 4 NovLahti 14:190 min—
Tue 3 NovLahti 14:22+2 min+2 min
Mon 2 NovLahti 14:22+2 min+2 min
Sun 1 NovLahti 14:200 min—
Sat 31 OctLahti 14:21+1 min—
Fri 30 OctLahti 14:21+1 min+1 min
Thu 29 OctLahti 14:19−1 min—
Wed 28 OctLahti 14:200 min—
Tue 27 OctLahti 14:190 min—
Mon 26 OctLahti 14:200 min—
Sun 25 OctLahti 14:200 min—
Sat 24 OctLahti 14:200 min—
Fri 23 OctLahti 14:21+1 min—
Thu 22 OctLahti 14:23+2 min+2 min
Wed 21 OctLahti 14:20−1 min—
Tue 20 OctLahti 14:20+1 min—
Mon 19 OctLahti 14:21+1 min—
Sun 18 OctLahti 14:200 min—
Sat 17 OctLahti 14:22−1 min—
Fri 16 OctLahti 14:190 min—
Thu 15 OctLahti 14:18−1 min—
Wed 14 OctLahti 14:21+1 min—
Tue 13 OctLahti 14:25+5 min+5 min
Mon 12 OctLahti 14:200 min—
Sat 10 Oct— 14:22No data—
Fri 9 OctLahti 14:21+2 min+2 min
Thu 8 OctLahti 14:21+1 min+1 min