REG 33765 Rzeszów Główny – Przeworsk

View line REG

Rzeszów Główny 16:30 → Przeworsk 17:07 Mon, Tue, Wed, Thu, Fri 0 h 37 min · 11 stops PolRegio

Running now · updated 16:39

Position estimated from the timetable

Between Rzeszów Załęże and Strażów 0 min

Estimated arrival at Przeworsk 17:07 · 68 km/h

  1. Rzeszów Główny16:30
  2. Rzeszów Załęże16:35
  3. Strażów16:39
  4. Łańcut16:47
  5. Kosina16:53
  6. Rogóżno koło Łańcuta16:57
  7. Przeworsk17:07

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

On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 15 full · 1 partial · 5 no data
On-time · 90 days
76%
22/29 runs under 3 min
RT coverage: 28 full · 1 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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 +6 min · last fix heading to Przeworsk +6 min
  • Mon 2 Nov Max en route +6 min · last fix heading to Przeworsk +6 min
  • Mon 12 Oct Max en route +3 min · last fix heading to Przeworsk +3 min
  • Fri 25 Sept Max en route +3 min · last fix heading to Przeworsk +3 min
  • Thu 24 Sept Max en route +3 min · last fix heading to Przeworsk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 22
  • 3–10 min 24% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 83% T n=6
  • 67% W n=6
  • 83% 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 (11 stops).

Last 90 days, 29 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
16:30on time +3 minPassed
16:32 / 16:33≈ on time ≈ +3 minPassed
16:35 / 16:36≈ on time ≈ +3 minPassed
16:39 / 16:40≈ on time ≈ +3 minNext
16:44≈ on time ≈ +3 min
16:47≈ on time ≈ +3 min
16:50 / 16:51≈ on time ≈ +3 min
16:53 / 16:54≈ on time ≈ +3 min
16:57≈ on time ≈ +3 min
17:02≈ on time ≈ +3 min
17:07on time +3 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 12 NovRzeszów Załęże 16:34Partial coverage0 min—
Tue 10 NovPrzeworsk 17:09+1 min+1 min
Mon 9 NovPrzeworsk 17:080 min—
Fri 6 NovPrzeworsk 17:080 min—
Thu 5 NovPrzeworsk 17:080 min—
Wed 4 NovPrzeworsk 17:080 min—
Tue 3 NovPrzeworsk 17:15+6 min+6 min
Mon 2 NovPrzeworsk 17:14+6 min+6 min
Fri 30 OctPrzeworsk 17:080 min—
Thu 29 OctPrzeworsk 17:080 min—
Wed 28 OctPrzeworsk 17:080 min—
Tue 27 OctPrzeworsk 17:080 min—
Mon 26 OctPrzeworsk 17:090 min—
Fri 23 OctPrzeworsk 17:09No data—
Thu 22 OctPrzeworsk 17:09No data—
Wed 21 OctPrzeworsk 17:09No data—
Tue 20 OctPrzeworsk 17:08No data—
Mon 19 OctPrzeworsk 17:08No data—
Fri 16 OctPrzeworsk 17:080 min—
Thu 15 OctPrzeworsk 17:080 min—
Wed 14 OctPrzeworsk 17:080 min—
Tue 13 OctPrzeworsk 17:11+2 min+2 min
Mon 12 OctPrzeworsk 17:11+3 min+3 min
Fri 9 OctPrzeworsk 17:080 min—
Thu 8 OctPrzeworsk 17:080 min—
Wed 7 OctPrzeworsk 17:080 min—
Tue 6 OctPrzeworsk 17:080 min—
Mon 5 OctPrzeworsk 17:080 min—
Fri 2 OctPrzeworsk 17:06No data—
Thu 1 OctPrzeworsk 17:06No data—