K 9114 Kerava – Helsinki

View line K

Kerava 09:52 → Helsinki 10:26 Mon, Tue, Wed, Thu, Fri 0 h 34 min · 15 stops VR (Finland)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 09:52 from Kerava · Thu 5 Nov

Next departure 09:52 today · Kerava
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 5 full · 3 partial · 0 no data
On-time · 90 days
94%
45/48 runs under 3 min
RT coverage: 45 full · 3 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Helsinki, 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 12 Aug Max en route +5 min · last fix heading to — +5 min
  • Thu 13 Aug Max en route +3 min · last fix heading to — +3 min
  • Sat 8 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=10
  • 100% T n=10
  • 89% W n=9
  • 88% T n=8
  • 100% F n=9
  • 0% S n=1
  • 100% S n=1

Stops and timetable

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

Last 90 days, 49 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
09:52on time +1 min
09:54≈ on time ≈ +1 min
09:57≈ on time ≈ +1 min
09:59≈ on time ≈ +1 min
10:00 / 10:01≈ on time ≈ +1 min
10:03 / 10:04≈ on time ≈ +1 min
10:05 / 10:06≈ on time ≈ +1 min
10:07 / 10:08≈ on time ≈ +1 min
10:09 / 10:10≈ on time ≈ +1 min
10:11 / 10:12≈ on time ≈ +2 min
10:13 / 10:14≈ on time ≈ +2 min
10:16≈ on time ≈ +2 min
10:18≈ on time ≈ +2 min
10:21≈ on time ≈ +2 min
10:26on 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
Wed 4 NovHelsinki 10:540 min—
Tue 3 NovHelsinki 10:540 min—
Mon 2 NovHelsinki 10:54−1 min—
Fri 30 OctPasila 10:55Partial coverage−1 min—
Thu 29 OctHelsinki 10:56+1 min+1 min
Wed 28 OctPasila 10:55Partial coverage−1 min—
Tue 27 OctPasila 10:55Partial coverage−1 min—
Mon 26 OctHelsinki 10:55−1 min—
Fri 2 Oct— 10:560 min—
Thu 1 Oct— 10:56+1 min—
Wed 30 Sept— 10:55−1 min—
Tue 29 Sept— 10:560 min—
Mon 28 Sept— 10:57+2 min+2 min
Fri 25 Sept— 10:56−1 min—
Thu 24 Sept— 10:56No data—
Wed 23 Sept— 10:56+1 min—
Tue 22 Sept— 10:55−1 min—
Mon 21 Sept— 10:55−1 min—
Fri 18 Sept— 10:57+1 min—
Thu 17 Sept— 10:57+1 min+1 min
Wed 16 Sept— 10:55−1 min—
Tue 15 Sept— 10:560 min—
Mon 14 Sept— 10:560 min—
Fri 11 Sept— 10:55−1 min—
Thu 10 Sept— 10:57+1 min—
Wed 9 Sept— 10:55−1 min—
Tue 8 Sept— 10:30+1 min—
Mon 7 Sept— 10:540 min—
Fri 4 Sept— 11:030 min—
Thu 3 Sept— 10:560 min—