RE20 134 Halden stasjon – Oslo S

View line RE20

Halden stasjon 20:11 → Oslo S 21:44 Mon, Tue, Wed, Thu, Fri 1 h 33 min · 8 stops Vy

It has not run yet today

Last recorded run: Wednesday 18 November +2 min

Next service: today 20:11 from Halden stasjon · Thu 19 Nov

Next departure 20:11 today · Halden stasjon
On-time · 30 days
61%
17/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
63%
41/65 runs under 3 min
RT coverage: 65 full · 0 partial · 0 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+13min
9 in 10 runs arrive with less than this
30 days: +18 min

Last 30 days

Arrival delay at Oslo S, in minutes. One bar per run.

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

Worst days

  • Mon 12 Oct Max en route +35 min · last fix heading to Oslo S +31 min
  • Wed 21 Oct Max en route +30 min · last fix heading to Oslo S +28 min
  • Thu 12 Nov Max en route +28 min · last fix heading to Oslo S +26 min
  • Sat 14 Nov Max en route +24 min · last fix heading to Oslo S +24 min
  • Thu 17 Sept Max en route +38 min · last fix heading to — +24 min

Distribution · 90 days

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

  • Early 20% · 13
  • On time 43% · 28
  • 3–10 min 22% · 14
  • 10–30 min 14% · 9
  • 30+ min 2% · 1

On-time by weekday

  • 45% M n=11
  • 71% T n=7
  • 63% W n=8
  • 30% T n=10
  • 78% F n=9
  • 89% S n=9
  • 73% S n=11

Stops and timetable

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

Last 90 days, 65 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:11+3 min +11 min
20:29 / 20:31≈ +3 min ≈ +11 min
20:42 / 20:44≈ +2 min ≈ +11 min
20:55 / 20:58≈ +2 min ≈ +12 min
21:04≈ +2 min ≈ +13 min
21:11 / 21:12≈ +2 min ≈ +13 min
21:31 / 21:32≈ +2 min ≈ +13 min
21:44+2 min +13 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 18 NovOslo S 22:09+2 min+9 min
Tue 17 NovOslo S 22:24−2 min+3 min
Mon 16 NovOslo S 21:49+4 min+4 min
Sun 15 NovOslo S 22:04−2 min+3 min
Sat 14 NovOslo S 22:29+24 min+24 min
Fri 13 NovOslo S 22:14+7 min+12 min
Thu 12 NovOslo S 22:34+26 min+28 min
Wed 11 NovOslo S 22:040 min+4 min
Mon 9 NovOslo S 22:14+9 min+15 min
Sun 8 NovOslo S 22:09−1 min+8 min
Sat 7 NovOslo S 22:09+2 min+8 min
Fri 6 NovOslo S 22:09+3 min+6 min
Thu 5 NovOslo S 22:14+8 min+13 min
Wed 4 NovOslo S 22:24+16 min+20 min
Tue 3 NovOslo S 22:04−2 min+3 min
Mon 2 NovOslo S 22:09+3 min+10 min
Sun 1 NovOslo S 21:34+3 min+3 min
Sat 31 OctOslo S 22:10+2 min+4 min
Fri 30 OctOslo S 22:050 min+3 min
Thu 29 Oct— 22:050 min—
Wed 28 OctOslo S 22:05−1 min+2 min
Tue 27 OctOslo S 22:090 min+6 min
Mon 26 OctOslo S 22:05−1 min+8 min
Sun 25 OctOslo S 22:14+5 min+12 min
Sat 24 OctOslo S 22:100 min+7 min
Fri 23 OctOslo S 22:09+1 min+7 min
Thu 22 OctOslo S 22:10+3 min+12 min
Wed 21 OctOslo S 22:35+28 min+30 min
Tue 20 OctOslo S 22:05−2 min+4 min
Mon 19 OctOslo S 22:20+10 min+16 min