H 1630 Hanko → Helsinki

View line H

Hanko 21:18 → Helsinki 23:25 Sat, Sun 2 h 07 min · 18 stops VR (Finland)

VR 1630 Hanko–Helsinki: final delay under 3 min on 9 of its 10 runs with data in the last 30 days (90%). Median final delay: 0 min. Running now, on time. Expected at Helsinki: 23:25. TrainsRadar data as of 22 Nov 2026, 22:13 (GMT+2).

Running now · updated 22:12

Between Dragsvik and Karjaa 0 min

Estimated arrival at Helsinki 23:25

  1. Hanko21:18
  2. Lappohja21:31
  3. Dragsvik21:47
  4. Karjaa21:58
  5. Siuntio22:39
  6. Masala22:54
  7. Helsinki23:25

Today it is running no worse than usual: typical arrival delay is 0 min; 90% of the last 10 runs arrived on time.

On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 2 full · 8 partial · 0 no data
On-time · 90 days
69%
11/16 runs under 3 min
RT coverage: 7 full · 9 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

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

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

Worst days

  • Sat 17 Oct Max en route +12 min · last fix heading to Helsinki +12 min
  • Sat 12 Sept Max en route +11 min · last fix heading to — +10 min
  • Sat 29 Aug Max en route +5 min · last fix heading to — +5 min
  • Sun 30 Aug Max en route +3 min · last fix heading to — +3 min
  • Sat 24 Oct Max en route +3 min · last fix heading to Helsinki +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 69% · 11
  • 3–10 min 19% · 3
  • 10–30 min 13% · 2
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 56% S n=9
  • 86% S n=7

Stops and timetable

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

Last 90 days, 16 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
21:18on time +4 minPassed
21:20≈ +1 min ≈ +8 minPassed
21:26 / 21:27≈ +1 min ≈ +8 minPassed
21:31 / 21:32≈ +1 min ≈ +9 minPassed
21:35 / 21:36≈ +1 min ≈ +9 minPassed
21:44 / 21:45≈ +1 min ≈ +9 minPassed
21:47 / 21:48≈ +1 min ≈ +9 minPassed
21:58 / 22:18≈ +1 min ≈ +9 minNext
22:28 / 22:29≈ +2 min ≈ +10 min
22:39 / 22:40≈ +2 min ≈ +10 min
22:48 / 22:49≈ +2 min ≈ +10 min
22:54 / 22:55≈ +3 min ≈ +10 min
22:59 / 23:00≈ +3 min ≈ +11 min
23:03 / 23:04≈ +3 min ≈ +11 min
23:12≈ +3 min ≈ +11 min
23:16≈ +3 min ≈ +11 min
23:19 / 23:20≈ +3 min ≈ +11 min
23:25+3 min +11 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
Sun 22 NovKarjaa 22:08Partial coverage0 min—
Sat 21 NovPasila 23:54Partial coverage0 min—
Sun 15 NovPasila 23:54Partial coverage0 min—
Sat 14 NovPasila 23:54Partial coverage0 min—
Sun 8 NovPasila 23:54Partial coverage−1 min—
Sat 7 NovHelsinki 23:59+2 min+2 min
Sun 1 NovPasila 23:54Partial coverage0 min—
Sat 31 OctPasila 23:56Partial coverage0 min—
Sun 25 OctPasila 23:57Partial coverage0 min—
Sat 24 OctHelsinki 23:59+3 min+3 min
Sun 18 OctPasila 23:55Partial coverage0 min—
Sat 17 OctHelsinki 00:07+12 min+12 min
Sun 11 Oct— 23:55No data—
Sat 10 Oct— 23:56No data—
Sat 26 Sept— 23:54+1 min—
Sat 12 Sept— 00:04+10 min+11 min
Sun 30 Aug— 23:59+3 min+3 min
Sat 29 Aug— 00:00+5 min+5 min