G 9957 Riihimäki – Lahti

View line G

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

✓ Today’s run finished

Today it reached Lahti at 18:56 0 min

  1. Riihimäki18:13
  2. Hikiä18:19
  3. Oitti18:24
  4. Lappila18:32
  5. Järvelä18:37
  6. Herrala18:45
  7. Lahti18:56

Next service: tomorrow 18:13 from Riihimäki · Sun 8 Nov

Next departure 18:13 tomorrow · Riihimäki
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 3 no data
On-time · 90 days
95%
82/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
+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

Worst days

  • Fri 25 Sept Max en route +8 min · last fix heading to — +8 min
  • Fri 4 Sept Max en route +7 min · last fix heading to — +6 min
  • Sun 23 Aug Max en route +3 min · last fix heading to — +3 min
  • Fri 16 Oct Max en route +3 min · last fix heading to Lahti +3 min

Distribution · 90 days

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

  • Early 7% · 6
  • On time 88% · 76
  • 3–10 min 5% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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