Train VR 83 Helsinki → Pieksämäki

Helsinki 08:00 → Pieksämäki 12:50 Sun 4 h 50 min · 13 stops VR (Finland)

VR 83 Helsinki–Pieksämäki: final delay under 3 min on 9 of its 9 runs with data in the last 30 days (100%). Median final delay: −3 min. Running now, on time. Expected at Pieksämäki: 12:50. TrainsRadar data as of 22 Nov 2026, 10:13 (GMT+2).

Running now · updated 10:13

Between Tampere and Orivesi 0 min

Estimated arrival at Pieksämäki 12:50 · 117 km/h

  1. Helsinki08:00
  2. Tikkurila08:14
  3. Hämeenlinna09:09
  4. Lempäälä09:40
  5. Tampere09:53
  6. Orivesi10:31
  7. Pieksämäki12:50

Today it is running worse than usual: typical arrival delay is −3 min; 100% of the last 9 runs arrived on time.

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%
25/25 runs under 3 min
RT coverage: 24 full · 1 partial · 1 no data
Typical delay
−5min
Median at arrival, 90 days
30 days: −3 min
P90
−2min
9 in 10 runs arrive with less than this
30 days: −1 min

Last 30 days

Arrival delay at Pieksämäki, 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

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

  • Early 96% · 24
  • On time 4% · 1
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=13
  • — S n=0
  • 100% S n=12

Stops and timetable

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

Last 90 days, 25 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 10Today
08:00on time +1 minPassed
08:05 / 08:06≈ on time ≈ +1 minPassed
08:14 / 08:16≈ on time ≈ +1 minPassed
08:50 / 08:52≈ 1 min early ≈ on timePassed
09:09 / 09:11≈ 1 min early ≈ on timePassed
09:30 / 09:31≈ 1 min early ≈ on timePassed
09:40 / 09:41≈ 1 min early ≈ 1 min earlyPassed
09:53 / 10:06≈ 2 min early ≈ 1 min earlyPassed
10:31 / 10:36≈ 2 min early ≈ 1 min earlyNext
11:14 / 11:15≈ 3 min early ≈ 1 min early
11:42 / 11:45≈ 4 min early ≈ 2 min early
12:09 / 12:10≈ 4 min early ≈ 2 min early
12:505 min early 2 min early

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
Sun 22 NovOrivesi 10:09Partial coverage0 min—
Fri 20 NovPieksämäki 13:14−5 min—
Sun 15 NovPieksämäki 13:19−2 min+2 min
Fri 13 NovPieksämäki 13:17−3 min—
Sun 8 NovPieksämäki 13:13−7 min+5 min
Fri 6 NovPieksämäki 13:14−3 min+1 min
Sun 1 NovPieksämäki 13:17−3 min+3 min
Fri 30 OctPieksämäki 13:17−3 min—
Sun 25 OctPieksämäki 13:14−6 min—
Fri 23 OctPieksämäki 13:14−6 min—
Sun 18 OctPieksämäki 13:15−5 min+3 min
Fri 16 OctPieksämäki 13:19−1 min+4 min
Sun 11 Oct— 13:15No data—
Fri 9 OctPieksämäki 13:15−3 min+2 min
Sun 4 OctPieksämäki 13:16−4 min+2 min
Fri 2 Oct— 13:14−7 min+2 min
Sun 27 Sept— 13:15−5 min—
Fri 25 Sept— 13:13−7 min—
Sun 20 Sept— 13:17−2 min—
Fri 18 Sept— 13:14−6 min+1 min
Sun 13 Sept— 13:16−5 min—
Fri 11 Sept— 13:14−7 min—
Sun 6 Sept— 13:15−5 min—
Fri 4 Sept— 13:16−4 min—
Sun 30 Aug— 13:17−4 min+1 min
Fri 28 Aug— 13:15−5 min+1 min