U 8465 Helsinki – Kirkkonummi

View line U

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

It has not run yet today

Last recorded run: Wednesday 18 November +3 min

Next service: today 11:42 from Helsinki · Thu 19 Nov

Next departure 11:42 today · Helsinki
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 0 full · 29 partial · 0 no data
On-time · 90 days
97%
77/79 runs under 3 min
RT coverage: 38 full · 41 partial · 2 no data
Typical delay
0min
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

Worst days

  • Thu 3 Sept Max en route +8 min · last fix heading to — +8 min
  • Wed 18 Nov Max en route +3 min · last fix heading to Tolsa +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 77
  • 3–10 min 3% · 2
  • 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
  • 92% T n=12
  • 100% F n=12
  • 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, 79 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
11:42on time +1 min
11:45 / 11:46≈ on time ≈ +1 min
11:49≈ on time ≈ +1 min
11:53 / 11:54≈ on time ≈ +1 min
11:56≈ on time ≈ +1 min
11:58≈ on time ≈ +1 min
12:00≈ on time ≈ +1 min
12:02≈ on time ≈ +1 min
12:04≈ on time ≈ +1 min
12:06 / 12:07≈ on time ≈ +1 min
12:10 / 12:11≈ on time ≈ +1 min
12:15 / 12:16≈ on time ≈ +1 min
12:18≈ on time ≈ +2 min
12:21≈ on time ≈ +2 min
12:24on 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 18 NovTolsa 12:54Partial coverage+3 min+3 min
Tue 17 NovTolsa 12:53Partial coverage0 min—
Mon 16 NovTolsa 12:53Partial coverage−1 min—
Sun 15 NovTolsa 12:53Partial coverage−1 min—
Sat 14 NovTolsa 12:53Partial coverage−1 min—
Fri 13 NovTolsa 12:53Partial coverage0 min—
Thu 12 NovTolsa 12:54Partial coverage0 min—
Wed 11 NovTolsa 12:53Partial coverage−1 min—
Tue 10 NovTolsa 12:53Partial coverage−1 min—
Mon 9 NovTolsa 12:53Partial coverage0 min—
Sun 8 NovTolsa 12:53Partial coverage−1 min—
Sat 7 NovTolsa 12:53Partial coverage−1 min—
Fri 6 NovTolsa 18:24Partial coverage0 min—
Thu 5 NovTolsa 12:53Partial coverage−1 min—
Wed 4 NovTolsa 12:52Partial coverage−1 min—
Tue 3 NovTolsa 12:53Partial coverage−1 min—
Mon 2 NovTolsa 12:53Partial coverage−1 min—
Sun 1 NovTolsa 12:53Partial coverage−1 min—
Sat 31 OctTolsa 12:57Partial coverage−1 min—
Fri 30 OctTolsa 12:53Partial coverage0 min—
Thu 29 OctTolsa 12:53Partial coverage−1 min—
Wed 28 OctTolsa 12:53Partial coverage−1 min—
Tue 27 OctTolsa 12:53Partial coverage−1 min—
Mon 26 OctTolsa 12:53Partial coverage−1 min—
Sun 25 OctTolsa 12:53Partial coverage−1 min—
Sat 24 OctTolsa 12:53Partial coverage0 min—
Fri 23 OctTolsa 12:53Partial coverage0 min—
Thu 22 OctTolsa 12:53Partial coverage0 min—
Wed 21 OctTolsa 12:53Partial coverage−1 min—
Tue 20 OctTolsa 12:54Partial coverage0 min—