REG 33295 Leżajsk – Przeworsk

View line REG

Leżajsk 14:56 → Przeworsk 15:22 Mon, Tue, Wed, Thu, Fri 0 h 26 min · 6 stops PolRegio

✓ Today’s run finished

Today it reached Przeworsk at 15:22 0 min

  1. Leżajsk14:56
  2. Wierzawice15:00
  3. Grodzisko Dolne15:07
  4. Tryńcza15:12
  5. Gniewczyna15:16
  6. Przeworsk15:22

Next service: tomorrow 14:56 from Leżajsk · Fri 20 Nov

Next departure 14:56 tomorrow · Leżajsk
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 16 full · 0 partial · 5 no data
On-time · 90 days
91%
29/32 runs under 3 min
RT coverage: 32 full · 0 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

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

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

Worst days

  • Tue 3 Nov Max en route +5 min · last fix heading to Przeworsk +5 min
  • Wed 4 Nov Max en route +4 min · last fix heading to Przeworsk +4 min
  • Fri 11 Sept Max en route +4 min · last fix heading to Przeworsk +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 29
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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
14:56on time +1 min
15:00≈ on time ≈ +1 min
15:07≈ on time ≈ +1 min
15:12≈ on time ≈ +1 min
15:16 / 15:17≈ on time ≈ +1 min
15:22on time +1 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 1 August 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
Thu 19 NovPrzeworsk 15:240 min—
Wed 18 NovPrzeworsk 15:240 min—
Tue 17 NovPrzeworsk 15:240 min—
Mon 16 NovPrzeworsk 15:240 min—
Fri 13 NovPrzeworsk 15:240 min—
Thu 12 NovPrzeworsk 15:24No data—
Tue 10 NovPrzeworsk 15:240 min—
Mon 9 NovPrzeworsk 15:240 min—
Fri 6 NovPrzeworsk 15:240 min—
Thu 5 NovPrzeworsk 15:24No data—
Wed 4 NovPrzeworsk 15:28+4 min+4 min
Tue 3 NovPrzeworsk 15:29+5 min+5 min
Mon 2 NovPrzeworsk 15:240 min—
Fri 30 OctPrzeworsk 15:110 min—
Thu 29 OctPrzeworsk 15:110 min—
Wed 28 OctPrzeworsk 15:110 min—
Tue 27 OctPrzeworsk 15:120 min—
Mon 26 OctPrzeworsk 15:13+1 min+1 min
Fri 23 OctPrzeworsk 15:23No data—
Thu 22 OctPrzeworsk 15:23No data—
Wed 21 OctPrzeworsk 15:24No data—
Tue 20 OctPrzeworsk 15:23No data—
Mon 19 OctPrzeworsk 15:24No data—
Fri 16 OctPrzeworsk 15:23No data—
Thu 15 OctPrzeworsk 15:230 min—
Wed 14 OctPrzeworsk 15:230 min—
Tue 13 OctPrzeworsk 15:240 min—
Mon 12 OctPrzeworsk 15:240 min—
Fri 9 OctPrzeworsk 15:23No data—
Thu 8 OctPrzeworsk 15:230 min—