S33 17533 Basel SBB – Liestal

View line S33

Basel SBB 09:45 → Liestal 10:04 Daily 0 h 19 min · 5 stops SBB CFF FFS

Running now · updated 10:05

Position estimated from the timetable

Between Frenkendorf-Füllinsdorf and Liestal 0 min

Estimated arrival at Liestal 10:04 · 7 km/h

  1. Basel SBB09:45
  2. Muttenz09:51
  3. Pratteln09:55
  4. Frenkendorf-Füllinsdorf10:00
  5. Liestal10:04

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

On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 3 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 39 full · 0 partial · 3 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 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

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

  • Early 3% · 1
  • On time 97% · 38
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=6
  • 100% W n=6
  • 100% T n=3
  • 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, 39 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
09:45on time on timePassed
09:51≈ on time ≈ on timePassed
09:55 / 09:56≈ on time ≈ on timePassed
10:00≈ on time ≈ on timePassed
10:04on time on timeNext

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 10:050 min—
Fri 13 NovLiestal 10:040 min—
Thu 12 NovLiestal 10:04No data—
Wed 11 NovLiestal 10:040 min—
Tue 10 NovLiestal 10:040 min—
Mon 9 NovLiestal 10:040 min—
Sun 8 NovLiestal 10:040 min—
Sat 7 NovLiestal 10:040 min—
Fri 6 NovLiestal 10:040 min—
Thu 5 NovLiestal 10:04No data—
Wed 4 NovLiestal 10:040 min—
Tue 3 NovLiestal 10:040 min—
Mon 2 NovLiestal 10:04+1 min—
Sun 1 NovLiestal 10:040 min—
Sat 31 OctLiestal 10:050 min—
Fri 30 OctLiestal 10:050 min—
Thu 29 OctLiestal 10:05No data—
Wed 28 OctLiestal 10:050 min—
Tue 27 OctLiestal 10:04−1 min—
Mon 26 OctLiestal 11:010 min—
Sun 25 OctLiestal 10:050 min—
Sat 24 OctLiestal 10:04−1 min—
Fri 23 OctLiestal 10:050 min—
Thu 22 OctLiestal 10:05−1 min—
Wed 21 OctLiestal 10:050 min—
Tue 20 OctLiestal 10:060 min—
Mon 19 OctLiestal 10:040 min—
Sun 18 OctLiestal 10:050 min—
Sat 17 OctLiestal 10:050 min—
Fri 16 OctLiestal 10:04−1 min—