G 9961 Riihimäki – Lahti

View line G

Riihimäki 19:13 → Lahti 19:56 Daily 0 h 43 min · 8 stops VR (Finland)

It has not run yet today

Last recorded run: Wednesday 4 November −1 min

Next service: today 19:13 from Riihimäki · Thu 5 Nov

Next departure 19:13 today · Riihimäki
On-time · 30 days
85%
22/26 runs under 3 min
RT coverage: 26 full · 0 partial · 3 no data
On-time · 90 days
92%
79/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
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Fri 23 Oct Max en route +9 min · last fix heading to Lahti +9 min
  • Sun 9 Aug Max en route +6 min · last fix heading to Lahti +6 min
  • Fri 21 Aug Max en route +5 min · last fix heading to — +5 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Lahti +4 min
  • Mon 26 Oct Max en route +4 min · last fix heading to Lahti +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 79
  • 3–10 min 8% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 87 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
19:13on time +1 min
19:19≈ on time ≈ +1 min
19:24≈ on time ≈ +1 min
19:28≈ on time ≈ +1 min
19:32 / 19:33≈ on time ≈ +2 min
19:37 / 19:38≈ on time ≈ +2 min
19:45 / 19:46≈ on time ≈ +2 min
19:56on time +3 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
Wed 4 NovLahti 20:24−1 min—
Tue 3 NovLahti 20:270 min—
Mon 2 NovLahti 20:27+1 min+1 min
Sun 1 NovLahti 20:29+4 min+4 min
Sat 31 OctLahti 20:290 min—
Fri 30 OctLahti 20:300 min—
Thu 29 OctLahti 20:270 min—
Wed 28 OctLahti 20:260 min—
Tue 27 OctLahti 20:260 min—
Mon 26 OctLahti 20:31+4 min+4 min
Sun 25 OctLahti 20:29+3 min+3 min
Sat 24 OctLahti 20:270 min—
Fri 23 OctLahti 20:34+9 min+9 min
Thu 22 OctLahti 20:28+1 min+2 min
Wed 21 OctLahti 20:250 min—
Tue 20 OctLahti 20:25−1 min—
Mon 19 OctLahti 20:27−1 min—
Sun 18 OctLahti 20:30+3 min+3 min
Sat 17 OctLahti 20:26−1 min—
Fri 16 OctLahti 20:29+1 min+1 min
Thu 15 OctLahti 20:29+2 min+2 min
Wed 14 OctLahti 20:28+1 min—
Tue 13 OctLahti 20:28−1 min—
Mon 12 OctLahti 20:29+3 min+3 min
Sun 11 Oct— 20:27No data—
Sat 10 Oct— 20:25No data—
Fri 9 Oct— 20:30No data—
Thu 8 OctLahti 20:280 min—
Wed 7 OctLahti 20:27−1 min—
Tue 6 OctLahti 20:290 min—