R13 1679 Drammen stasjon – Eidsvoll stasjon

View line R13

Drammen stasjon 00:05 → Eidsvoll stasjon 01:41 Daily 1 h 36 min · 19 stops Vy

✓ Today’s run finished

Today, last fix heading to — at 02:09 0 min

  1. Drammen stasjon00:05
  2. Asker stasjon00:18
  3. Skøyen stasjon00:33
  4. Lillestrøm stasjon00:54
  5. Lindeberg stasjon01:07
  6. Nordby stasjon01:20
  7. Eidsvoll stasjon01:41

Next service: tomorrow 00:05 from Drammen stasjon · Wed 11 Nov

Next departure 00:05 tomorrow · Drammen stasjon
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 no data
On-time · 90 days
100%
71/71 runs under 3 min
RT coverage: 71 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 Eidsvoll 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

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

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

On-time by weekday

  • 100% M n=11
  • 100% T n=11
  • 100% W n=10
  • 100% T n=12
  • 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 (19 stops).

Last 90 days, 71 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:05on time on time
00:08≈ on time ≈ on time
00:11≈ on time ≈ on time
00:18 / 00:19≈ on time ≈ on time
00:24 / 00:25≈ on time ≈ on time
00:30 / 00:31≈ on time ≈ on time
00:33 / 00:34≈ on time ≈ on time
00:37 / 00:38≈ on time ≈ on time
00:41 / 00:44≈ on time ≈ on time
00:54 / 00:55≈ on time ≈ on time
01:00≈ on time ≈ on time
01:04≈ on time ≈ on time
01:07≈ on time ≈ on time
01:10 / 01:11≈ on time ≈ on time
01:17 / 01:18≈ on time ≈ on time
01:20≈ on time ≈ on time
01:24≈ on time ≈ on time
01:30 / 01:31≈ on time ≈ on time
01:41on 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
Tue 10 Nov— 02:090 min—
Mon 9 Nov— 02:040 min—
Sun 8 Nov— 02:090 min—
Sat 7 Nov— 02:090 min—
Thu 5 Nov— 02:190 min—
Tue 3 Nov— 02:340 min—
Mon 2 Nov— 02:140 min—
Sun 1 Nov— 02:100 min—
Sat 31 Oct— 03:000 min—
Thu 29 Oct— 02:150 min—
Wed 28 Oct— 02:250 min—
Tue 27 Oct— 02:140 min—
Mon 26 Oct— 02:250 min—
Sun 25 Oct— 02:150 min—
Sat 24 Oct— 02:040 min—
Thu 22 Oct— 02:150 min—
Wed 21 Oct— 02:200 min—
Tue 20 Oct— 02:150 min—
Mon 19 Oct— 02:250 min—
Sun 18 Oct— 02:100 min—
Fri 16 Oct— 02:150 min—
Wed 14 Oct— 02:140 min—
Tue 13 Oct— 02:140 min—
Mon 12 Oct— 02:100 min—
Sun 11 Oct— 02:140 min—
Thu 8 Oct— 02:150 min—
Wed 7 Oct— 02:040 min—
Tue 6 Oct— 02:100 min—
Mon 5 Oct— 02:130 min—
Fri 2 Oct— 02:240 min—