RE20 114 Halden stasjon – Oslo S

View line RE20

Halden stasjon 10:11 → Oslo S 11:45 Sun 1 h 34 min · 8 stops Vy

Running now · updated 11:57

Heading to Oslo S 0 min

Estimated arrival at Oslo S 11:45

  1. Halden stasjon10:11
  2. Sarpsborg stasjon10:30
  3. Fredrikstad stasjon10:43
  4. Rygge stasjon11:05
  5. Moss stasjon11:12
  6. Ski stasjon11:32
  7. Oslo S11:45

Today it is running no worse than usual: typical arrival delay is +1 min; 64% of the last 28 runs arrived on time.

On-time · 30 days
64%
18/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
69%
34/49 runs under 3 min
RT coverage: 49 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +13 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

  • Sat 17 Oct Max en route +27 min · last fix heading to Oslo S +22 min
  • Tue 27 Oct Max en route +22 min · last fix heading to Oslo S +22 min
  • Fri 23 Oct Max en route +23 min · last fix heading to Oslo S +22 min
  • Wed 21 Oct Max en route +12 min · last fix heading to Oslo S +9 min
  • Sun 27 Sept Max en route +15 min · last fix heading to — +9 min

Distribution · 90 days

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

  • Early 18% · 9
  • On time 51% · 25
  • 3–10 min 24% · 12
  • 10–30 min 6% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 50% T n=4
  • 57% W n=7
  • 90% T n=10
  • 25% F n=4
  • 57% S n=7
  • 80% S n=10

Stops and timetable

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

Last 90 days, 49 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
10:11+1 min +8 min
10:30 / 10:31≈ +2 min ≈ +8 min
10:43 / 10:45≈ +2 min ≈ +8 min
10:56 / 10:59≈ +2 min ≈ +8 min
11:05≈ +1 min ≈ +8 min
11:12 / 11:13≈ +1 min ≈ +8 min
11:32 / 11:33≈ +1 min ≈ +8 min
11:45+1 min +8 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 8 NovOslo S 11:540 min+3 min
Sat 7 NovOslo S 12:09+4 min+9 min
Fri 6 NovOslo S 12:14+5 min+14 min
Thu 5 NovOslo S 12:090 min+8 min
Wed 4 NovOslo S 12:090 min+5 min
Tue 3 NovOslo S 12:09+1 min+6 min
Mon 2 NovOslo S 12:04+1 min+1 min
Sun 1 NovOslo S 12:05+1 min+3 min
Sat 31 OctOslo S 12:04−1 min+1 min
Fri 30 OctOslo S 12:100 min+3 min
Thu 29 OctOslo S 12:25−1 min+2 min
Wed 28 OctOslo S 12:05+1 min+2 min
Tue 27 OctOslo S 12:30+22 min+22 min
Mon 26 OctOslo S 12:05−1 min+4 min
Sun 25 OctOslo S 12:100 min+4 min
Sat 24 OctOslo S 12:04−1 min+7 min
Fri 23 OctOslo S 12:30+22 min+23 min
Thu 22 OctOslo S 12:06−1 min+6 min
Wed 21 OctOslo S 12:40+9 min+12 min
Tue 20 OctOslo S 12:16+8 min+12 min
Mon 19 OctOslo S 12:050 min+8 min
Sun 18 OctOslo S 12:09+1 min+4 min
Sat 17 OctOslo S 12:34+22 min+27 min
Fri 16 OctOslo S 12:11+4 min+6 min
Thu 15 OctOslo S 12:05−2 min+39 min
Wed 14 OctOslo S 16:15+5 min+11 min
Mon 12 OctOslo S 12:05−1 min+4 min
Sun 11 OctOslo S 12:14+6 min+9 min
Thu 8 OctOslo S 12:40+8 min+11 min
Wed 7 OctOslo S 12:16+8 min+10 min