M 1753 Tampere – Nokia

View line M

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

✓ Today’s run finished

Today it reached Nokia at 17:55 0 min

  1. Tampere17:40
  2. Tesoma17:48
  3. Nokia17:55

Next service: Monday 17:40 from Tampere · Mon 9 Nov

Next departure 17:40 Monday · Tampere
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
100%
64/64 runs under 3 min
RT coverage: 64 full · 0 partial · 0 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 Nokia, 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

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

  • Early 0% · 0
  • On time 100% · 64
  • 3–10 min 0% · 0
  • 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
  • 100% T n=13
  • 100% F n=13
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 64 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
17:40on time +1 min
17:48 / 17:49≈ on time ≈ +1 min
17:55on 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 NovNokia 18:240 min—
Thu 5 NovNokia 18:24+1 min—
Wed 4 NovNokia 18:240 min—
Tue 3 NovNokia 18:28+3 min+3 min
Mon 2 NovNokia 18:240 min—
Fri 30 OctNokia 18:26+2 min+2 min
Thu 29 OctNokia 18:270 min—
Wed 28 OctNokia 18:250 min—
Tue 27 OctNokia 18:250 min—
Mon 26 OctNokia 18:280 min—
Fri 23 OctNokia 18:250 min—
Thu 22 OctNokia 18:290 min—
Wed 21 OctNokia 18:240 min—
Tue 20 OctNokia 18:250 min—
Mon 19 OctNokia 18:240 min—
Fri 16 OctNokia 18:26+1 min+1 min
Thu 15 OctNokia 18:240 min—
Wed 14 OctNokia 18:240 min—
Mon 12 OctNokia 18:250 min—
Fri 9 OctNokia 18:270 min—
Thu 8 OctNokia 18:230 min—
Wed 7 OctNokia 18:29+1 min—
Tue 6 OctNokia 18:27+1 min—
Mon 5 OctNokia 18:26+1 min+1 min
Fri 2 Oct— 18:250 min—
Thu 1 Oct— 18:27+1 min—
Wed 30 Sept— 18:290 min—
Tue 29 Sept— 18:240 min—
Mon 28 Sept— 18:280 min—
Fri 25 Sept— 18:25+1 min—