O 1661 Lahti – Kouvola

View line O

Lahti 10:08 → Kouvola 10:51 Mon, Tue, Wed, Thu, Fri, Sat 0 h 43 min · 7 stops VR (Finland)

✓ Today’s run finished

Today it reached Kouvola at 10:51 0 min

  1. Lahti10:08
  2. Villähde10:15
  3. Nastola10:20
  4. Uusikylä10:23
  5. Kausala10:35
  6. Koria10:45
  7. Kouvola10:51

Next service: Monday 10:08 from Lahti · Mon 9 Nov

Next departure 10:08 Monday · Lahti
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 1 no data
On-time · 90 days
99%
74/75 runs under 3 min
RT coverage: 75 full · 0 partial · 2 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 Kouvola, 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 +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 99% · 74
  • 3–10 min 1% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=13
  • 100% T n=13
  • 100% W n=12
  • 100% T n=12
  • 100% F n=13
  • 100% S n=12
  • — S n=0

Stops and timetable

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

Last 90 days, 75 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
10:08on time on time
10:15 / 10:16≈ on time ≈ on time
10:20≈ on time ≈ on time
10:23 / 10:24≈ on time ≈ on time
10:35 / 10:36≈ on time ≈ +1 min
10:45 / 10:46≈ on time ≈ +1 min
10:51on 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 NovKouvola 11:190 min—
Fri 6 NovKouvola 11:190 min—
Thu 5 NovKouvola 11:190 min—
Wed 4 NovKouvola 11:190 min—
Tue 3 NovKouvola 11:190 min—
Mon 2 NovKouvola 12:090 min—
Sat 31 OctKouvola 11:210 min—
Fri 30 OctKouvola 11:200 min—
Thu 29 OctKouvola 11:23+1 min+1 min
Tue 27 OctKouvola 11:200 min—
Mon 26 OctKouvola 11:21+1 min+1 min
Sat 24 OctKouvola 11:210 min—
Fri 23 OctKouvola 11:200 min—
Thu 22 OctKouvola 11:200 min—
Wed 21 OctKouvola 11:200 min—
Tue 20 OctKouvola 11:21+1 min—
Mon 19 OctKouvola 11:200 min—
Sat 17 OctKouvola 11:21+1 min+1 min
Fri 16 OctKouvola 11:22+1 min+1 min
Thu 15 OctKouvola 11:210 min—
Wed 14 OctKouvola 11:21+1 min+1 min
Tue 13 OctKouvola 11:210 min—
Mon 12 OctKouvola 11:22+1 min+1 min
Sat 10 Oct— 11:21No data—
Fri 9 OctKouvola 11:22+1 min—
Thu 8 OctKouvola 11:24+2 min+2 min
Wed 7 OctKouvola 11:230 min—
Tue 6 OctKouvola 11:200 min—
Mon 5 OctKouvola 11:200 min—
Sat 3 Oct— 12:180 min—