M 1762 Nokia – Tampere

View line M

Nokia 20:05 → Tampere 20:20 Mon, Tue, Wed, Thu, Fri 0 h 15 min · 3 stops VR (Finland)

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 20:05 from Nokia · Thu 5 Nov

Next departure 20:05 today · Nokia
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 18 full · 0 partial · 1 no data
On-time · 90 days
97%
58/60 runs under 3 min
RT coverage: 60 full · 0 partial · 1 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: +2 min

Last 30 days

Arrival delay at Tampere, 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 22 Oct Max en route +6 min · last fix heading to Tampere +6 min
  • Thu 17 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 58
  • 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=12
  • 100% W n=13
  • 82% T n=11
  • 100% F n=11
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 60 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
20:05on time +1 min
20:11 / 20:12≈ on time ≈ +1 min
20:20on 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
Wed 4 NovTampere 20:49+1 min—
Tue 3 NovTampere 20:52+2 min+2 min
Mon 2 NovTampere 20:49+2 min+2 min
Fri 30 OctTampere 20:52+1 min+1 min
Thu 29 OctTampere 20:50+1 min—
Wed 28 OctTampere 20:53+3 min+3 min
Tue 27 OctTampere 20:50+1 min+1 min
Mon 26 OctTampere 20:500 min—
Fri 23 OctTampere 20:500 min—
Thu 22 OctTampere 20:55+6 min+6 min
Wed 21 OctTampere 20:500 min—
Tue 20 OctTampere 20:500 min—
Mon 19 OctTampere 20:500 min—
Fri 16 OctTampere 20:490 min—
Thu 15 OctTampere 20:500 min—
Wed 14 OctTampere 20:500 min—
Mon 12 OctTampere 20:510 min—
Fri 9 Oct— 20:50No data—
Wed 7 OctTampere 20:50+1 min—
Tue 6 OctTampere 20:510 min—
Mon 5 OctTampere 20:500 min—
Fri 2 Oct— 22:02+1 min—
Thu 1 Oct— 20:500 min—
Wed 30 Sept— 20:500 min—
Tue 29 Sept— 20:500 min—
Mon 28 Sept— 20:500 min—
Fri 25 Sept— 20:51+1 min+1 min
Thu 24 Sept— 20:50+1 min—
Wed 23 Sept— 20:500 min—
Tue 22 Sept— 20:500 min—