Train VR 761 Joensuu – Nurmes

Joensuu 11:54 → Nurmes 14:00 Daily 2 h 06 min · 9 stops VR (Finland)

✓ Today’s run finished

Today it reached Nurmes at 14:00 0 min

  1. Joensuu11:54
  2. Eno12:18
  3. Vuonislahti12:52
  4. Lieksa13:13
  5. Kylänlahti13:25
  6. Kohtavaara13:50
  7. Nurmes14:00

Next service: tomorrow 11:54 from Joensuu · Sat 7 Nov

Next departure 11:54 tomorrow · Joensuu
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
93%
80/86 runs under 3 min
RT coverage: 85 full · 1 partial · 3 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: +1 min

Last 30 days

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

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

Worst days

  • Sun 4 Oct Max en route +23 min · last fix heading to Kohtavaara +15 min
  • Wed 14 Oct Max en route +14 min · last fix heading to Nurmes +14 min
  • Sun 30 Aug Max en route +8 min · last fix heading to — +8 min
  • Mon 7 Sept Max en route +11 min · last fix heading to — +8 min
  • Tue 6 Oct Max en route +3 min · last fix heading to Nurmes +3 min

Distribution · 90 days

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

  • Early 12% · 10
  • On time 81% · 70
  • 3–10 min 5% · 4
  • 10–30 min 2% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 86 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
11:54on time +1 min
12:18 / 12:19≈ on time ≈ +2 min
12:29 / 12:30≈ on time ≈ +2 min
12:52 / 12:53≈ on time ≈ +2 min
13:13 / 13:15≈ on time ≈ +2 min
13:25 / 13:26≈ on time ≈ +2 min
13:42 / 13:43≈ on time ≈ +2 min
13:50 / 13:51≈ on time ≈ +2 min
14:00on 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 6 NovNurmes 14:290 min—
Thu 5 NovNurmes 14:290 min—
Wed 4 NovNurmes 14:29−1 min+1 min
Tue 3 NovNurmes 14:28−1 min—
Mon 2 NovNurmes 14:290 min—
Sun 1 NovNurmes 14:300 min—
Sat 31 OctNurmes 14:33+3 min+3 min
Fri 30 OctNurmes 14:30−1 min—
Thu 29 OctNurmes 14:58−1 min—
Wed 28 OctNurmes 14:30−1 min—
Tue 27 OctNurmes 14:510 min—
Mon 26 OctNurmes 14:29−1 min—
Sun 25 OctNurmes 14:300 min—
Sat 24 OctNurmes 14:34+1 min—
Fri 23 OctNurmes 14:550 min—
Thu 22 OctNurmes 14:300 min—
Wed 21 OctNurmes 14:300 min—
Tue 20 OctNurmes 14:29−1 min—
Mon 19 OctNurmes 14:300 min—
Sun 18 OctNurmes 14:300 min—
Sat 17 OctNurmes 14:300 min—
Fri 16 OctNurmes 14:33+2 min+2 min
Thu 15 OctNurmes 14:310 min—
Wed 14 OctNurmes 14:44+14 min+14 min
Tue 13 OctNurmes 14:290 min—
Mon 12 OctNurmes 14:300 min—
Sun 11 Oct— 14:30No data—
Sat 10 Oct— 14:32No data—
Fri 9 OctNurmes 14:290 min—
Thu 8 OctNurmes 14:30−1 min—