S33 17543 Basel SBB – Liestal

View line S33

Basel SBB 12:15 → Liestal 12:34 Daily 0 h 19 min · 5 stops SBB CFF FFS

✓ Today’s run finished

Today, last fix heading to Liestal at 12:34 No data

  1. Basel SBB12:15
  2. Muttenz12:21
  3. Pratteln12:25
  4. Frenkendorf-Füllinsdorf12:30
  5. Liestal12:34

Next service: tomorrow 12:15 from Basel SBB · Tue 17 Nov

Next departure 12:15 tomorrow · Basel SBB
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 8 no data
On-time · 90 days
100%
32/32 runs under 3 min
RT coverage: 32 full · 0 partial · 10 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 38% · 12
  • On time 63% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=6
  • 100% W n=6
  • 100% T n=1
  • 100% F n=6
  • 100% S n=5
  • 100% S n=6

Stops and timetable

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

Last 90 days, 32 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
12:15on time on time
12:21≈ on time ≈ on time
12:25 / 12:26≈ on time ≈ on time
12:30≈ 1 min early ≈ on time
12:341 min early 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 16 NovLiestal 12:34No data—
Fri 13 NovLiestal 12:340 min—
Thu 12 NovLiestal 12:34No data—
Wed 11 NovLiestal 12:34−1 min—
Tue 10 NovLiestal 12:35−1 min—
Mon 9 NovLiestal 12:34No data—
Sun 8 NovLiestal 12:34−1 min—
Sat 7 NovLiestal 12:33−1 min—
Fri 6 NovLiestal 12:340 min—
Thu 5 NovLiestal 12:34No data—
Wed 4 NovLiestal 12:34−1 min—
Tue 3 NovLiestal 12:340 min—
Mon 2 NovLiestal 12:340 min—
Sun 1 NovLiestal 12:34−1 min—
Sat 31 OctLiestal 12:34−1 min—
Fri 30 OctLiestal 12:34−1 min—
Thu 29 OctLiestal 12:35No data—
Wed 28 OctLiestal 12:34−1 min—
Tue 27 OctLiestal 12:34−1 min—
Mon 26 OctLiestal 12:35No data—
Sun 25 OctLiestal 12:33−1 min—
Sat 24 OctLiestal 12:350 min—
Fri 23 OctLiestal 12:33−1 min—
Thu 22 OctLiestal 12:35No data—
Wed 21 OctLiestal 12:350 min—
Tue 20 OctLiestal 12:35−1 min—
Mon 19 OctLiestal 12:35No data—
Sun 18 OctLiestal 12:350 min—
Sat 17 OctLiestal 12:350 min—
Fri 16 OctLiestal 12:38+2 min+3 min