Z 9885 Helsinki – Lahti

View line Z

Helsinki 01:10 → Lahti 02:15 Sat, Sun 1 h 05 min · 8 stops VR (Finland)

✓ Today’s run finished

Today it reached Lahti at 02:16 +1 min

  1. Helsinki01:10
  2. Pasila01:14
  3. Tikkurila01:23
  4. Haarajoki01:39
  5. Mäntsälä01:49
  6. Henna02:00
  7. Lahti02:15

Next service: tomorrow 01:10 from Helsinki · Sun 8 Nov

Next departure 01:10 tomorrow · Helsinki
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 7 full · 0 partial · 2 no data
On-time · 90 days
100%
7/7 runs under 3 min
RT coverage: 7 full · 0 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

Distribution · 90 days

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

  • Early 14% · 1
  • On time 86% · 6
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 7 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
01:10on time on time
01:14 / 01:15≈ on time ≈ on time
01:23 / 01:24≈ on time ≈ on time
01:32 / 01:33≈ on time ≈ on time
01:39 / 01:40≈ on time ≈ on time
01:49 / 01:50≈ on time ≈ on time
02:00 / 02:01≈ on time ≈ on time
02:15on time +1 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 02:44+1 min—
Sun 1 NovLahti 19:49−1 min—
Sat 31 OctLahti 02:44−1 min—
Sun 25 OctLahti 02:43−2 min—
Sat 24 OctLahti 02:46+1 min—
Sun 18 OctLahti 02:500 min—
Sat 17 OctLahti 02:440 min—
Sun 11 Oct— 02:45No data—
Sat 10 Oct— 02:49No data—
Sun 4 OctLahti 02:46No data—
Sat 3 Oct— 02:43No data—
Sun 27 Sept— 02:44No data—
Sat 26 SeptHaarajoki 01:38Partial coverageNo data—
Sun 20 Sept— 02:45No data—
Sat 19 Sept— 02:46No data—
Sun 13 Sept— 02:46No data—
Sat 12 Sept— 02:43No data—
Sun 6 Sept— 02:43No data—
Sat 5 Sept— 02:46No data—
Sun 30 Aug— 02:46No data—
Sat 29 Aug— 02:44No data—
Sun 23 Aug— 02:44No data—
Sat 22 Aug— 02:47No data—
Sun 16 Aug— 02:46No data—
Sat 15 Aug— 02:49No data—