K 9127 Helsinki – Kerava

View line K

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

✓ Today’s run finished

Today it reached Kerava at 10:26 +1 min

  1. Helsinki09:51
  2. Käpylä09:57
  3. Malmi10:04
  4. Puistola10:08
  5. Hiekkaharju10:12
  6. Korso10:19
  7. Kerava10:25

Next service: tomorrow 09:51 from Helsinki · Fri 6 Nov

Next departure 09:51 tomorrow · Helsinki
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 8 full · 1 partial · 0 no data
On-time · 90 days
100%
48/48 runs under 3 min
RT coverage: 47 full · 1 partial · 1 no data
Typical delay
+1min
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 Kerava, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 48
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=10
  • 100% W n=10
  • 100% T n=9
  • 100% F n=8
  • 100% 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, 48 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:51on time on time
09:54 / 09:55≈ on time ≈ on time
09:57 / 09:58≈ on time ≈ on time
09:59 / 10:00≈ on time ≈ +1 min
10:02≈ on time ≈ +1 min
10:04≈ on time ≈ +1 min
10:06≈ on time ≈ +1 min
10:08≈ on time ≈ +1 min
10:10 / 10:11≈ on time ≈ +1 min
10:12 / 10:13≈ on time ≈ +1 min
10:15≈ on time ≈ +1 min
10:16 / 10:17≈ on time ≈ +1 min
10:19≈ on time ≈ +1 min
10:21 / 10:22≈ on time ≈ +1 min
10:25+1 min +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 NovKerava 10:54+1 min—
Wed 4 NovKerava 10:540 min—
Tue 3 NovKerava 10:540 min—
Mon 2 NovKerava 10:540 min—
Fri 30 OctKerava 10:55+1 min—
Thu 29 OctKerava 10:55+1 min—
Wed 28 OctKerava 10:55+1 min—
Tue 27 OctKerava 10:550 min—
Mon 26 OctKorso 10:54Partial coverage0 min—
Fri 2 Oct— 10:550 min—
Thu 1 Oct— 10:550 min—
Wed 30 Sept— 10:55+1 min—
Tue 29 Sept— 10:56+1 min+1 min
Mon 28 Sept— 10:55+1 min—
Fri 25 Sept— 10:55+1 min—
Thu 24 Sept— 10:55No data—
Wed 23 Sept— 10:56+2 min+2 min
Tue 22 Sept— 10:550 min—
Mon 21 Sept— 10:55+1 min—
Fri 18 Sept— 10:55+1 min—
Thu 17 Sept— 10:550 min—
Wed 16 Sept— 10:55+1 min—
Tue 15 Sept— 10:550 min+1 min
Mon 14 Sept— 10:540 min—
Thu 10 Sept— 10:55+1 min—
Wed 9 Sept— 10:550 min—
Tue 8 Sept— 10:300 min—
Mon 7 Sept— 10:550 min—
Fri 4 Sept— 10:55+1 min—
Thu 3 Sept— 10:550 min—