RE20 139 Oslo S – Halden stasjon

View line RE20

Oslo S 00:22 → Halden stasjon 02:01 Sat 1 h 39 min · 12 stops Vy

It does not run today

Last recorded run: Monday 9 November 0 min

On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 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
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Halden stasjon, 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=7
  • 100% T n=11
  • 100% W n=10
  • 100% T n=9
  • 100% F n=9
  • 100% S n=8
  • 100% S n=10

Stops and timetable

Timetable of the latest run from the operator’s GTFS (12 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
00:22on time on time
00:33 / 00:35≈ on time ≈ on time
00:39 / 00:40≈ on time ≈ on time
00:44 / 00:45≈ on time ≈ on time
00:51≈ on time ≈ on time
00:55≈ on time ≈ on time
01:02 / 01:03≈ on time ≈ on time
01:11≈ on time ≈ on time
01:16 / 01:17≈ on time ≈ on time
01:29 / 01:30≈ on time ≈ on time
01:41 / 01:42≈ on time ≈ on time
02:01on time on time

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
Mon 9 Nov— 02:120 min—
Sat 7 Nov— 02:390 min—
Thu 5 Nov— 02:290 min—
Wed 4 Nov— 02:340 min—
Tue 3 Nov— 02:290 min—
Mon 2 Nov— 02:390 min—
Sun 1 Nov— 02:390 min—
Fri 30 Oct— 02:370 min—
Wed 28 Oct— 02:390 min—
Tue 27 Oct— 02:440 min—
Sun 25 Oct— 02:390 min—
Fri 23 Oct— 02:490 min—
Thu 22 Oct— 02:350 min—
Tue 20 Oct— 02:400 min—
Sun 18 Oct— 02:550 min—
Sat 17 Oct— 02:350 min—
Fri 16 Oct— 02:450 min—
Wed 14 Oct— 02:300 min—
Tue 13 Oct— 02:400 min—
Sun 11 Oct— 02:340 min—
Thu 1 Oct— 02:350 min—
Wed 30 Sept— 02:350 min—
Tue 29 Sept— 01:590 min—
Mon 28 Sept— 02:390 min—
Sun 27 Sept— 01:590 min—
Sat 26 Sept— 01:590 min—
Wed 23 Sept— 02:350 min—
Tue 22 Sept— 01:590 min—
Sun 20 Sept— 02:350 min—
Sat 19 Sept— 02:340 min—