U 8491 Helsinki → Kirkkonummi

View line U

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

VR 8491 Helsinki–Kirkkonummi: final delay under 3 min on 29 of its 29 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 05:56 (GMT+2).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 18:12 from Helsinki · Sun 22 Nov

Next departure 18:12 today · Helsinki
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 0 full · 29 partial · 0 no data
On-time · 90 days
99%
75/76 runs under 3 min
RT coverage: 32 full · 44 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Mon 7 Sept Max en route +19 min · last fix heading to — +19 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 99% · 75
  • 3–10 min 0% · 0
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=12
  • 100% T n=13
  • 100% W n=12
  • 100% T n=13
  • 100% F n=11
  • 100% S n=9
  • 100% S n=6

Stops and timetable

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

Last 90 days, 76 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
18:12on time +1 min
18:15 / 18:16≈ on time ≈ +1 min
18:19≈ on time ≈ +1 min
18:23 / 18:24≈ +1 min ≈ +1 min
18:26≈ +1 min ≈ +1 min
18:28≈ +1 min ≈ +1 min
18:30≈ +1 min ≈ +1 min
18:32≈ +1 min ≈ +1 min
18:34≈ +1 min ≈ +1 min
18:36 / 18:37≈ +1 min ≈ +1 min
18:40 / 18:41≈ +1 min ≈ +1 min
18:45 / 18:46≈ +1 min ≈ +2 min
18:48≈ +1 min ≈ +2 min
18:51≈ +1 min ≈ +2 min
18:54+1 min +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
Sat 21 NovTolsa 19:23Partial coverage0 min—
Fri 20 NovTolsa 19:24Partial coverage0 min—
Thu 19 NovTolsa 19:24Partial coverage+1 min+1 min
Wed 18 NovTolsa 19:25Partial coverage+1 min—
Tue 17 NovTolsa 19:24Partial coverage0 min—
Mon 16 NovTolsa 19:24Partial coverage+1 min—
Sun 15 NovTolsa 19:24Partial coverage0 min—
Sat 14 NovTolsa 19:23Partial coverage0 min—
Fri 13 NovTolsa 19:24Partial coverage0 min—
Thu 12 NovTolsa 19:24Partial coverage0 min—
Wed 11 NovTolsa 19:24Partial coverage0 min—
Tue 10 NovTolsa 19:24Partial coverage0 min—
Mon 9 NovTolsa 19:24Partial coverage0 min—
Sun 8 NovTolsa 19:24Partial coverage0 min—
Sat 7 NovTolsa 19:24Partial coverage0 min—
Fri 6 NovTolsa 19:24Partial coverage0 min—
Thu 5 NovTolsa 19:24Partial coverage0 min—
Wed 4 NovTolsa 19:23Partial coverage0 min—
Tue 3 NovTolsa 19:24Partial coverage0 min—
Mon 2 NovTolsa 19:23Partial coverage0 min—
Sun 1 NovTolsa 19:24Partial coverage0 min—
Sat 31 OctTolsa 19:23Partial coverage0 min—
Fri 30 OctTolsa 19:23Partial coverage0 min—
Thu 29 OctTolsa 19:24Partial coverage0 min—
Wed 28 OctTolsa 19:24Partial coverage0 min—
Tue 27 OctTolsa 19:24Partial coverage0 min—
Mon 26 OctTolsa 19:24Partial coverage0 min—
Sun 25 OctTolsa 19:24Partial coverage0 min—
Sat 24 OctTolsa 19:24Partial coverage−1 min—
Fri 23 OctTolsa 19:24Partial coverage0 min—