U 8461 Helsinki – Kirkkonummi

View line U

Helsinki 10:42 → Kirkkonummi 11:24 Daily 0 h 42 min · 15 stops VR (Finland)

✓ Today’s run finished

Today, last fix heading to Tolsa at 11:52 −1 min

  1. Helsinki10:42
  2. Huopalahti10:49
  3. Kera10:58
  4. Koivuhovi11:02
  5. Espoo11:06
  6. Tolsa11:21
  7. Kirkkonummi11:24

Next service: tomorrow 10:42 from Helsinki · Thu 19 Nov

Next departure 10:42 tomorrow · Helsinki
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 1 full · 29 partial · 0 no data
On-time · 90 days
100%
80/80 runs under 3 min
RT coverage: 39 full · 41 partial · 2 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Kirkkonummi, 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

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

  • Early 5% · 4
  • On time 95% · 76
  • 3–10 min 0% · 0
  • 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=12
  • 100% F n=13
  • 100% S n=9
  • 100% S n=7

Stops and timetable

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

Last 90 days, 80 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:42on time +1 min
10:45 / 10:46≈ on time ≈ +1 min
10:49≈ on time ≈ +1 min
10:53 / 10:54≈ on time ≈ +1 min
10:56≈ on time ≈ +1 min
10:58≈ on time ≈ +1 min
11:00≈ on time ≈ +1 min
11:02≈ on time ≈ +1 min
11:04≈ on time ≈ +1 min
11:06 / 11:07≈ on time ≈ +1 min
11:10 / 11:11≈ on time ≈ +1 min
11:15 / 11:16≈ on time ≈ +1 min
11:18≈ on time ≈ +1 min
11:21≈ on time ≈ +1 min
11:24on 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
Wed 18 NovTolsa 11:52Partial coverage−1 min—
Tue 17 NovTolsa 11:53Partial coverage0 min—
Mon 16 NovTolsa 11:53Partial coverage−1 min—
Sun 15 NovTolsa 11:53Partial coverage−1 min—
Sat 14 NovTolsa 11:54Partial coverage0 min—
Fri 13 NovTolsa 11:53Partial coverage−1 min—
Thu 12 NovTolsa 11:53Partial coverage0 min—
Wed 11 NovTolsa 11:53Partial coverage−1 min—
Tue 10 Nov— 11:530 min—
Mon 9 NovTolsa 11:53Partial coverage−1 min—
Sun 8 NovTolsa 11:53Partial coverage−1 min—
Sat 7 NovTolsa 11:53Partial coverage−1 min—
Fri 6 NovTolsa 18:24Partial coverage−1 min—
Thu 5 NovTolsa 11:53Partial coverage−1 min—
Wed 4 NovTolsa 11:53Partial coverage−1 min—
Tue 3 NovTolsa 11:53Partial coverage0 min—
Mon 2 NovTolsa 11:53Partial coverage−1 min—
Sun 1 NovTolsa 11:53Partial coverage−1 min—
Sat 31 OctTolsa 11:58Partial coverage−1 min—
Fri 30 OctTolsa 11:53Partial coverage0 min—
Thu 29 OctTolsa 11:53Partial coverage−1 min—
Wed 28 OctTolsa 11:53Partial coverage−1 min—
Tue 27 OctTolsa 11:53Partial coverage−1 min—
Mon 26 OctTolsa 11:53Partial coverage−1 min—
Sun 25 OctTolsa 11:54Partial coverage0 min—
Sat 24 OctTolsa 11:53Partial coverage−1 min—
Fri 23 OctTolsa 11:53Partial coverage−1 min—
Thu 22 OctTolsa 11:53Partial coverage0 min—
Wed 21 OctTolsa 11:53Partial coverage−1 min—
Tue 20 OctTolsa 11:54Partial coverage0 min—