S33 17523 Basel SBB – Liestal

View line S33

Basel SBB 07:15 → Liestal 07:34 Mon, Tue, Wed, Thu, Fri 0 h 19 min · 5 stops SBB CFF FFS

Running now · updated 07:20

Position estimated from the timetable

Between Basel SBB and Muttenz 0 min

Estimated arrival at Liestal 07:34 · 48 km/h

  1. Basel SBB07:15
  2. Muttenz07:21
  3. Pratteln07:25
  4. Frenkendorf-Füllinsdorf07:30
  5. Liestal07:34

Today it is running no worse than usual: typical arrival delay is 0 min; 95% of the last 21 runs arrived on time.

On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Liestal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 21 Oct Max en route +6 min · last fix heading to Liestal +6 min

Distribution · 90 days

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

  • Early 12% · 4
  • On time 85% · 29
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 86% W n=7
  • 100% T n=6
  • 100% F n=6
  • — S n=0
  • 100% S n=1

Stops and timetable

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

Last 90 days, 34 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
07:15on time on timePassed
07:21≈ on time ≈ +1 minNext
07:25 / 07:26≈ on time ≈ +1 min
07:30≈ on time ≈ +1 min
07:34on time +2 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
Wed 18 NovLiestal 07:340 min—
Tue 17 NovLiestal 07:33−1 min—
Mon 16 NovLiestal 07:34−1 min—
Fri 13 NovLiestal 07:340 min—
Thu 12 NovLiestal 07:340 min—
Wed 11 NovLiestal 07:38+3 min+3 min
Tue 10 NovLiestal 07:340 min—
Mon 9 NovLiestal 07:340 min—
Fri 6 NovLiestal 07:340 min—
Thu 5 NovLiestal 07:34−1 min—
Wed 4 NovLiestal 07:34−1 min—
Tue 3 NovLiestal 07:340 min—
Mon 2 NovLiestal 07:340 min—
Fri 30 OctLiestal 07:340 min—
Thu 29 OctLiestal 07:350 min—
Wed 28 OctLiestal 07:350 min—
Tue 27 OctLiestal 07:350 min—
Mon 26 OctLiestal 07:35−1 min—
Fri 23 OctLiestal 07:350 min—
Thu 22 OctLiestal 07:36+1 min+1 min
Wed 21 OctLiestal 07:42+6 min+6 min
Tue 20 OctLiestal 07:35−1 min—
Mon 19 OctLiestal 07:34−1 min—
Fri 16 OctLiestal 07:350 min—
Thu 15 OctLiestal 07:350 min—
Wed 14 OctLiestal 07:350 min—
Tue 13 OctLiestal 07:34−1 min—
Mon 12 OctLiestal 07:37+3 min+3 min
Fri 9 OctLiestal 07:350 min—
Thu 8 OctLiestal 07:350 min—