G 9917 Riihimäki – Lahti

View line G

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

✓ Today’s run finished

Today it reached Lahti at 08:57 +1 min

  1. Riihimäki08:13
  2. Hikiä08:19
  3. Oitti08:24
  4. Lappila08:32
  5. Järvelä08:37
  6. Herrala08:45
  7. Lahti08:56

Next service: tomorrow 08:13 from Riihimäki · Fri 6 Nov

Next departure 08:13 tomorrow · Riihimäki
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
93%
81/87 runs under 3 min
RT coverage: 87 full · 0 partial · 3 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

  • Mon 7 Sept Max en route +6 min · last fix heading to — +6 min
  • Tue 15 Sept Max en route +6 min · last fix heading to — +6 min
  • Wed 7 Oct Max en route +5 min · last fix heading to Lahti +5 min
  • Thu 1 Oct Max en route +4 min · last fix heading to — +4 min
  • Sun 9 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 1% · 1
  • On time 92% · 80
  • 3–10 min 7% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=13
  • 85% T n=13
  • 92% W n=13
  • 92% T n=12
  • 100% F n=12
  • 100% S n=12
  • 92% 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
08:13on time +1 min
08:19≈ on time ≈ +1 min
08:24≈ on time ≈ +1 min
08:28≈ on time ≈ +1 min
08:32 / 08:33≈ on time ≈ +1 min
08:37 / 08:38≈ on time ≈ +2 min
08:45 / 08:46≈ on time ≈ +2 min
08:56on 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
Thu 5 NovLahti 09:24+1 min—
Wed 4 NovLahti 09:240 min—
Tue 3 NovLahti 09:250 min—
Mon 2 NovLahti 09:240 min—
Sun 1 NovLahti 09:250 min—
Sat 31 OctLahti 09:260 min—
Fri 30 OctLahti 09:26+1 min—
Thu 29 OctLahti 09:27+1 min+1 min
Wed 28 OctLahti 09:31+1 min—
Tue 27 OctLahti 09:280 min—
Mon 26 OctLahti 09:250 min—
Sun 25 OctLahti 09:260 min—
Sat 24 OctLahti 09:250 min—
Fri 23 OctLahti 09:250 min—
Thu 22 OctLahti 09:250 min—
Wed 21 OctLahti 09:250 min—
Tue 20 OctLahti 09:260 min—
Mon 19 OctLahti 09:290 min—
Sun 18 OctLahti 09:27+1 min+1 min
Sat 17 OctLahti 09:28+2 min+2 min
Fri 16 OctLahti 09:29+1 min—
Thu 15 OctLahti 09:260 min—
Wed 14 OctLahti 09:27+1 min+1 min
Tue 13 OctLahti 09:28+1 min—
Mon 12 Oct— 09:28+1 min—
Sun 11 Oct— 09:29No data—
Sat 10 Oct— 09:27No data—
Fri 9 OctLahti 09:250 min—
Thu 8 OctLahti 09:270 min—
Wed 7 OctLahti 09:32+5 min+5 min