L1 2281 Lillestrøm stasjon – Drammen stasjon

View line L1

Lillestrøm stasjon 00:40 → Drammen stasjon 02:00 Mon, Tue, Wed, Thu, Fri 1 h 20 min · 29 stops Vy

✓ Today’s run finished

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

  1. Lillestrøm stasjon00:40
  2. Lørenskog stasjon00:50
  3. Nyland stasjon00:59
  4. Skøyen stasjon01:16
  5. Sandvika stasjon01:30
  6. Vakås stasjon01:41
  7. Drammen stasjon02:00

Next service: tomorrow 00:40 from Lillestrøm stasjon · Tue 10 Nov

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

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=4
  • 100% T n=4
  • 100% F n=2
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 24 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:40on time on time
00:43≈ on time ≈ on time
00:44 / 00:45≈ on time ≈ on time
00:47≈ on time ≈ on time
00:49≈ on time ≈ on time
00:50 / 00:51≈ on time ≈ on time
00:52 / 00:53≈ on time ≈ on time
00:54 / 00:55≈ on time ≈ on time
00:56 / 00:57≈ on time ≈ on time
00:59≈ on time ≈ on time
01:02≈ on time ≈ on time
01:05≈ on time ≈ on time
01:09 / 01:11≈ on time ≈ on time
01:12 / 01:13≈ on time ≈ on time
01:16 / 01:17≈ on time ≈ on time
01:20 / 01:21≈ on time ≈ on time
01:23 / 01:24≈ on time ≈ on time
01:25 / 01:26≈ on time ≈ on time
01:28≈ on time ≈ on time
01:30 / 01:31≈ on time ≈ on time
01:32 / 01:33≈ on time ≈ on time
01:35 / 01:36≈ on time ≈ on time
01:38 / 01:39≈ on time ≈ on time
01:41≈ on time ≈ on time
01:43≈ on time ≈ on time
01:45 / 01:46≈ on time ≈ on time
01:54≈ on time ≈ on time
01:57≈ on time ≈ on time
02:00on 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:300 min—
Fri 6 Nov— 02:390 min—
Thu 5 Nov— 02:340 min—
Wed 4 Nov— 02:340 min—
Sat 31 Oct— 02:340 min—
Fri 30 Oct— 02:320 min—
Thu 29 Oct— 02:350 min—
Mon 26 Oct— 02:390 min—
Sat 24 Oct— 01:590 min—
Wed 21 Oct— 01:500 min—
Mon 19 Oct— 01:500 min—
Tue 29 Sept— 02:400 min—
Sun 20 Sept— 02:250 min—
Tue 15 Sept— 02:270 min—
Mon 14 Sept— 02:250 min—
Mon 7 Sept— 02:240 min—
Thu 3 Sept— 03:050 min—
Wed 2 Sept— 01:590 min—
Tue 1 Sept— 02:400 min—
Sat 29 Aug— 02:540 min—
Thu 27 Aug— 02:350 min—
Tue 25 Aug— 02:450 min—
Sun 23 Aug— 02:390 min—
Wed 19 Aug— 02:550 min—