S33 17567 Basel SBB – Liestal

View line S33

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

✓ Today’s run finished

Today it reached Liestal at 18:34 0 min

  1. Basel SBB18:15
  2. Muttenz18:21
  3. Pratteln18:25
  4. Frenkendorf-Füllinsdorf18:30
  5. Liestal18:34

Next service: tomorrow 18:15 from Basel SBB · Sat 7 Nov

Next departure 18:15 tomorrow · Basel SBB
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
36/36 runs under 3 min
RT coverage: 36 full · 0 partial · 1 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

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

  • Early 19% · 7
  • On time 81% · 29
  • 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=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=6
  • 100% S n=4
  • 100% S n=6

Stops and timetable

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

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