A 8083 Helsinki – Leppävaara

View line A

Helsinki 10:23 → Leppävaara 10:39 Daily 0 h 16 min · 8 stops VR (Finland)

✓ Today’s run finished

Today, last fix heading to Pitäjänmäki at 11:09 0 min

  1. Helsinki10:23
  2. Pasila10:27
  3. Ilmala10:29
  4. Valimo10:33
  5. Pitäjänmäki10:34
  6. Mäkkylä10:36
  7. Leppävaara10:39

Next service: tomorrow 10:23 from Helsinki · Sat 7 Nov

Next departure 10:23 tomorrow · Helsinki
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 0 full · 27 partial · 2 no data
On-time · 90 days
99%
82/83 runs under 3 min
RT coverage: 52 full · 31 partial · 5 no data
Typical delay
0min
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 Leppävaara, 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 14 Sept Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 83 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:23on time on time
10:27≈ on time ≈ +1 min
10:29≈ on time ≈ +1 min
10:31 / 10:32≈ on time ≈ +1 min
10:33≈ on time ≈ +1 min
10:34 / 10:35≈ on time ≈ +1 min
10:36 / 10:37≈ on time ≈ +1 min
10:39on 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
Fri 6 NovPitäjänmäki 11:09Partial coverage0 min—
Thu 5 NovPitäjänmäki 11:09Partial coverage0 min—
Wed 4 NovPitäjänmäki 11:09Partial coverage0 min—
Tue 3 NovPitäjänmäki 11:09Partial coverage0 min—
Mon 2 NovPitäjänmäki 11:09Partial coverage+1 min—
Sun 1 NovPitäjänmäki 11:09Partial coverage0 min—
Sat 31 OctPitäjänmäki 11:11Partial coverage0 min—
Fri 30 OctPitäjänmäki 11:09Partial coverage0 min—
Thu 29 OctValimo 11:09Partial coverage0 min—
Tue 27 OctPitäjänmäki 11:09Partial coverage0 min—
Mon 26 OctPitäjänmäki 11:09Partial coverage0 min—
Sun 25 OctPitäjänmäki 11:09Partial coverage0 min—
Sat 24 OctPitäjänmäki 11:09Partial coverage0 min—
Fri 23 OctPitäjänmäki 11:09Partial coverage0 min—
Thu 22 OctPitäjänmäki 11:09Partial coverage0 min—
Wed 21 OctPitäjänmäki 11:10Partial coverage+1 min—
Tue 20 OctPitäjänmäki 11:09Partial coverage+1 min—
Mon 19 OctValimo 11:10Partial coverage+1 min—
Sun 18 OctPitäjänmäki 11:11Partial coverage0 min—
Sat 17 OctPitäjänmäki 11:09Partial coverage0 min—
Fri 16 OctPitäjänmäki 11:09Partial coverage0 min—
Thu 15 OctPitäjänmäki 11:09Partial coverage0 min—
Wed 14 OctPitäjänmäki 11:09Partial coverage0 min—
Tue 13 OctPitäjänmäki 11:10Partial coverage0 min—
Mon 12 OctPitäjänmäki 11:09Partial coverage+1 min—
Sun 11 Oct— 11:09No data—
Sat 10 Oct— 11:09No data—
Fri 9 OctPitäjänmäki 11:09Partial coverage+1 min—
Thu 8 OctPitäjänmäki 11:09Partial coverage0 min—
Wed 7 OctPitäjänmäki 11:09Partial coverage0 min—