R31 239 Oslo S – Gjøvik stasjon

View line R31

Oslo S 00:04 → Gjøvik stasjon 02:09 Daily 2 h 05 min · 22 stops Vy

✓ Today’s run finished

Today, last fix heading to — at 01:30 0 min

  1. Oslo S00:04
  2. Kjelsås stasjon00:17
  3. Nittedal stasjon00:33
  4. Harestua stasjon00:54
  5. Lunner stasjon01:11
  6. Eina stasjon01:45
  7. Gjøvik stasjon02:09

Next service: tomorrow 00:04 from Oslo S · Tue 10 Nov

Next departure 00:04 tomorrow · Oslo S
On-time · 30 days
100%
26/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
On-time · 90 days
100%
77/77 runs under 3 min
RT coverage: 77 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 Gjøvik 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

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

  • Early 0% · 0
  • On time 100% · 77
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=11
  • 100% W n=10
  • 100% T n=13
  • 100% F n=13
  • 100% S n=11
  • 100% S n=10

Stops and timetable

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

Last 90 days, 77 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:04on time on time
00:08 / 00:09≈ on time ≈ on time
00:11 / 00:12≈ on time ≈ on time
00:14 / 00:15≈ on time ≈ on time
00:17 / 00:19≈ on time ≈ on time
00:25 / 00:26≈ on time ≈ on time
00:28 / 00:29≈ on time ≈ on time
00:33 / 00:34≈ on time ≈ on time
00:37 / 00:38≈ on time ≈ on time
00:40 / 00:41≈ on time ≈ on time
00:43 / 00:44≈ on time ≈ on time
00:54 / 00:55≈ on time ≈ on time
01:01 / 01:02≈ on time ≈ on time
01:06 / 01:07≈ on time ≈ on time
01:11≈ on time ≈ on time
01:16 / 01:17≈ on time ≈ on time
01:22 / 01:23≈ on time ≈ on time
01:30≈ on time ≈ on time
01:45 / 01:46≈ on time ≈ on time
01:52 / 01:53≈ on time ≈ on time
01:57 / 01:58≈ on time ≈ on time
02:09on 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— 01:300 min—
Sun 8 Nov— 01:290 min—
Sat 7 Nov— 01:290 min—
Fri 6 Nov— 01:290 min—
Thu 5 Nov— 01:290 min—
Wed 4 Nov— 01:290 min—
Tue 3 Nov— 01:290 min—
Sun 1 Nov— 02:290 min—
Sat 31 Oct— 02:350 min—
Fri 30 Oct— 02:340 min—
Thu 29 Oct— 02:300 min—
Tue 27 Oct— 02:340 min—
Mon 26 Oct— 02:350 min—
Sun 25 Oct— 02:350 min—
Sat 24 Oct— 02:090 min—
Fri 23 Oct— 02:340 min—
Thu 22 Oct— 02:250 min—
Wed 21 Oct— 02:250 min—
Tue 20 Oct— 02:340 min—
Sun 18 Oct— 02:350 min—
Sat 17 Oct— 02:300 min—
Fri 16 Oct— 01:450 min—
Thu 15 Oct— 01:260 min—
Wed 14 Oct— 03:310 min—
Tue 13 Oct— 02:340 min—
Mon 12 Oct— 02:340 min—
Sat 10 Oct— 02:350 min—
Fri 9 Oct— 02:350 min—
Thu 8 Oct— 02:400 min—
Tue 6 Oct— 02:350 min—