REG 11815 Łuków – Terespol

View line REG

Łuków 13:25 → Terespol 14:42 Sun 1 h 17 min · 20 stops PolRegio

It does not run today

Last recorded run: Sunday 8 November 0 min

Next service: Sunday 13:25 from Łuków · Sun 15 Nov

Next departure 13:25 Sunday · Łuków
On-time · 30 days
67%
2/3 runs under 3 min
RT coverage: 3 full · 0 partial · 1 no data
On-time · 90 days
78%
7/9 runs under 3 min
RT coverage: 9 full · 0 partial · 2 no data
Typical delay
+2min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

Last 30 days

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

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

Worst days

  • Sun 1 Nov Max en route +8 min · last fix heading to Terespol +4 min
  • Sun 11 Oct Max en route +6 min · last fix heading to Terespol +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 7
  • 3–10 min 22% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • — S n=0
  • 78% S n=9

Stops and timetable

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

Last 90 days, 9 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
13:25+1 min +3 min
13:27 / 13:28≈ +1 min ≈ +3 min
13:31 / 13:32≈ +1 min ≈ +3 min
13:35≈ +1 min ≈ +3 min
13:38 / 13:39≈ +1 min ≈ +3 min
13:43≈ +1 min ≈ +3 min
13:48 / 13:49≈ +1 min ≈ +3 min
13:52 / 13:53≈ +1 min ≈ +3 min
13:55 / 13:56≈ +1 min ≈ +3 min
13:59≈ +1 min ≈ +3 min
14:04 / 14:05≈ +2 min ≈ +3 min
14:08 / 14:09≈ +2 min ≈ +3 min
14:11≈ +2 min ≈ +3 min
14:15 / 14:16≈ +2 min ≈ +3 min
14:18≈ +2 min ≈ +3 min
14:22 / 14:23≈ +2 min ≈ +3 min
14:27≈ +2 min ≈ +3 min
14:32 / 14:33≈ +2 min ≈ +3 min
14:35≈ +2 min ≈ +3 min
14:42+2 min +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
Sun 8 NovTerespol 14:430 min+1 min
Sun 1 NovTerespol 14:47+4 min+8 min
Sun 25 OctTerespol 14:43No data—
Sun 18 OctTerespol 14:44+1 min+5 min
Sun 11 OctTerespol 14:46+3 min+6 min
Sun 4 OctTerespol 14:430 min+3 min
Sun 27 SeptTerespol 14:42+2 min+2 min
Sun 20 SeptTerespol 14:41+2 min+2 min
Sun 13 SeptTerespol 14:41+2 min+2 min
Sun 6 SeptTerespol 14:41+2 min+5 min
Sun 30 AugTerespol 14:41No data—