T 9798 Riihimäki → Jokela

View line T

Riihimäki 02:45 → Jokela 03:01 Mon, Tue, Wed, Thu, Fri 0 h 16 min · 3 stops VR (Finland)

VR 9798 Riihimäki–Jokela: final delay under 3 min on 19 of its 20 runs with data in the last 30 days (95%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 22:04 (GMT+2).

It does not run today

Last recorded run: Friday 20 November +1 min

Next service: Monday 02:45 from Riihimäki · Mon 23 Nov

Next departure 02:45 Monday · Riihimäki
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
93%
52/56 runs under 3 min
RT coverage: 56 full · 0 partial · 1 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: +2 min

Last 30 days

Arrival delay at Jokela, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 25 Aug Max en route +6 min · last fix heading to Jokela +6 min
  • Mon 24 Aug Max en route +6 min · last fix heading to Jokela +6 min
  • Wed 26 Aug Max en route +5 min · last fix heading to Jokela +5 min
  • Thu 19 Nov Max en route +4 min · last fix heading to Jokela +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 52
  • 3–10 min 7% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 91% M n=11
  • 89% T n=9
  • 92% W n=12
  • 92% T n=12
  • 100% F n=12
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 56 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
02:45on time +1 min
02:53 / 02:54≈ on time ≈ +1 min
03:01on 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
Fri 20 NovJokela 03:32+1 min+1 min
Thu 19 NovJokela 03:34+4 min+4 min
Wed 18 NovJokela 03:290 min—
Tue 17 NovJokela 03:29−1 min—
Mon 16 NovJokela 03:290 min—
Fri 13 NovJokela 03:290 min—
Thu 12 NovJokela 03:320 min—
Wed 11 NovJokela 03:290 min—
Tue 10 NovJokela 03:290 min—
Mon 9 NovJokela 03:30−1 min—
Fri 6 NovJokela 18:29+1 min—
Thu 5 NovJokela 03:290 min—
Wed 4 NovJokela 03:290 min—
Mon 2 NovJokela 03:290 min—
Fri 30 OctJokela 03:310 min—
Thu 29 OctJokela 03:320 min—
Wed 28 OctJokela 03:33+2 min+2 min
Tue 27 OctJokela 03:310 min—
Mon 26 OctJokela 03:33+2 min+2 min
Fri 23 OctJokela 03:33+1 min—
Thu 22 OctJokela 03:31−1 min—
Wed 21 OctJokela 03:310 min—
Tue 20 OctJokela 03:310 min—
Mon 19 OctJokela 03:330 min—
Fri 16 OctJokela 03:310 min—
Thu 15 OctJokela 03:310 min—
Wed 14 OctJokela 03:310 min—
Tue 13 OctJokela 03:30−1 min—
Mon 12 Oct— 03:34No data—
Fri 9 OctJokela 03:30−1 min—