O 1671 Lahti – Kotkan satama

View line O

Lahti 15:30 → Kotkan satama 17:02 Mon, Tue, Wed, Thu, Fri 1 h 32 min · 15 stops VR (Finland)

Running now · updated 17:06

Heading to Kotkan satama +2 min

Estimated arrival at Kotkan satama 17:04 17:02 · 0 km/h

  1. Lahti15:30
  2. Nastola15:42
  3. Koria16:07
  4. Myllykoski16:24
  5. Tavastila16:43
  6. Paimenportti16:56
  7. Kotkan satama17:02

Today it is running worse than usual: typical arrival delay is 0 min; 100% of the last 22 runs arrived on time.

On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 1 full · 21 partial · 0 no data
On-time · 90 days
98%
63/64 runs under 3 min
RT coverage: 41 full · 23 partial · 0 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: +2 min

Last 30 days

Arrival delay at Kotkan satama, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 9 Sept Max en route +7 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 63
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 64 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 10Today
15:30on time on time
15:37 / 15:38≈ on time ≈ +1 min
15:42≈ on time ≈ +1 min
15:45 / 15:46≈ on time ≈ +1 min
15:57 / 15:58≈ on time ≈ +1 min
16:07 / 16:08≈ on time ≈ +1 min
16:13 / 16:15≈ on time ≈ +1 min
16:24 / 16:25≈ on time ≈ +1 min
16:32 / 16:33≈ on time ≈ +1 min
16:43 / 16:44≈ on time ≈ +1 min
16:47 / 16:48≈ on time ≈ +1 min
16:51 / 16:52≈ on time ≈ +1 min
16:56≈ on time ≈ +1 min
16:59 / 17:00≈ on time ≈ +1 min
17:02on 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
Thu 5 NovKotka 17:05Partial coverage+2 min+2 min
Wed 4 NovKotka 17:29Partial coverage−1 min—
Tue 3 NovKotka 17:29Partial coverage0 min—
Mon 2 NovKotka 17:29Partial coverage0 min—
Fri 30 OctKotka 17:32Partial coverage−1 min—
Thu 29 OctKotka 17:31Partial coverage−1 min—
Wed 28 OctKotka 17:34Partial coverage+2 min+2 min
Tue 27 OctKotka 17:38Partial coverage0 min—
Mon 26 OctKotka 17:32Partial coverage0 min—
Fri 23 OctKotka 17:32Partial coverage0 min—
Thu 22 OctKotka 17:36Partial coverage0 min—
Wed 21 OctKotka 17:32Partial coverage−1 min—
Tue 20 OctKotka 17:32Partial coverage−1 min—
Mon 19 OctKotka 17:34Partial coverage0 min—
Fri 16 OctKotka 17:33Partial coverage+1 min+1 min
Thu 15 OctKotka 17:31Partial coverage0 min—
Wed 14 OctKotka 17:32Partial coverage0 min—
Tue 13 OctKotka 17:35Partial coverage0 min—
Mon 12 OctKotka 17:31Partial coverage0 min—
Fri 9 OctKotkan satama 17:34+3 min+3 min
Thu 8 OctKotka 17:32Partial coverage0 min—
Wed 7 OctKotka 17:31Partial coverage0 min—
Tue 6 OctKotka 17:31Partial coverage−1 min—
Mon 5 OctKotka 17:28Partial coverage0 min—
Fri 2 Oct— 17:310 min—
Thu 1 Oct— 17:31−1 min—
Wed 30 Sept— 17:320 min—
Tue 29 Sept— 17:310 min—
Mon 28 Sept— 17:320 min—
Fri 25 Sept— 17:330 min—