G 9945 Riihimäki – Lahti

View line G

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

✓ Today’s run finished

Today it reached Lahti at 15:56 0 min

  1. Riihimäki15:13
  2. Hikiä15:19
  3. Oitti15:24
  4. Lappila15:32
  5. Järvelä15:37
  6. Herrala15:45
  7. Lahti15:56

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

Next departure 15:13 tomorrow · Riihimäki
On-time · 30 days
89%
25/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
80%
70/88 runs under 3 min
RT coverage: 88 full · 0 partial · 2 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
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

  • Mon 17 Aug Max en route +15 min · last fix heading to — +15 min
  • Tue 13 Oct Max en route +9 min · last fix heading to Lahti +9 min
  • Tue 11 Aug Max en route +8 min · last fix heading to — +8 min
  • Sun 18 Oct Max en route +13 min · last fix heading to Lahti +8 min
  • Fri 14 Aug Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 70
  • 3–10 min 19% · 17
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 85% M n=13
  • 77% T n=13
  • 77% W n=13
  • 85% T n=13
  • 75% F n=12
  • 83% S n=12
  • 75% S n=12

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