Z 9863 Helsinki – Lahti

View line Z

Helsinki 18:45 → Lahti 19:50 Daily 1 h 05 min · 8 stops VR (Finland)

Running now · updated 18:37

Heading to Lahti No data

Estimated arrival at Lahti 19:50 · 0 km/h

  1. Helsinki18:45
  2. Pasila18:49
  3. Tikkurila18:58
  4. Haarajoki19:14
  5. Mäntsälä19:24
  6. Henna19:35
  7. Lahti19:50
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
91%
78/86 runs under 3 min
RT coverage: 86 full · 0 partial · 4 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: +1 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

  • Sun 30 Aug Max en route +21 min · last fix heading to — +21 min
  • Sun 20 Sept Max en route +9 min · last fix heading to — +9 min
  • Tue 13 Oct Max en route +8 min · last fix heading to Lahti +8 min
  • Fri 23 Oct Max en route +5 min · last fix heading to Lahti +5 min
  • Mon 12 Oct Max en route +5 min · last fix heading to Lahti +5 min

Distribution · 90 days

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

  • Early 26% · 22
  • On time 65% · 56
  • 3–10 min 8% · 7
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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 10Today
18:45on time +1 min
18:49 / 18:50≈ on time ≈ +1 min
18:58 / 18:59≈ on time ≈ +1 min
19:07 / 19:08≈ on time ≈ +1 min
19:14 / 19:15≈ on time ≈ +1 min
19:24 / 19:25≈ on time ≈ +2 min
19:35 / 19:36≈ on time ≈ +2 min
19: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 14 Nov— 18:34No data—
Fri 13 NovLahti 20:19−1 min—
Thu 12 NovLahti 20:190 min—
Wed 11 NovLahti 20:190 min—
Tue 10 NovLahti 20:19−1 min—
Mon 9 NovLahti 20:190 min—
Sun 8 NovLahti 20:190 min—
Sat 7 NovLahti 20:19−2 min—
Fri 6 NovLahti 20:19+1 min+1 min
Thu 5 NovLahti 20:19+1 min—
Wed 4 NovLahti 20:180 min—
Tue 3 NovLahti 20:19+1 min+1 min
Mon 2 NovLahti 20:19+1 min—
Sun 1 NovLahti 20:19−1 min—
Sat 31 OctLahti 20:21+1 min+1 min
Fri 30 OctLahti 20:21−1 min—
Thu 29 OctLahti 20:19−1 min—
Wed 28 OctLahti 20:19−1 min—
Tue 27 OctLahti 20:210 min—
Mon 26 OctLahti 20:17−1 min—
Sun 25 OctLahti 20:20−1 min—
Sat 24 OctLahti 20:19−1 min—
Fri 23 OctLahti 20:25+5 min+5 min
Thu 22 OctLahti 20:200 min—
Wed 21 OctLahti 20:22+2 min+2 min
Tue 20 OctLahti 20:200 min—
Mon 19 OctLahti 20:17−2 min—
Sun 18 OctLahti 20:24+4 min+6 min
Sat 17 OctLahti 20:19−1 min—
Fri 16 OctLahti 20:18−2 min—