AR 50986 Toruń Główny → Sierpc

View line AR

Toruń Główny 10:59 → Sierpc 12:40 Mon, Tue, Wed, Thu, Fri 1 h 41 min · 17 stops Arriva

AR 50986/7 Toruń Główny–Sierpc: final delay under 3 min on 4 of its 4 runs with data in the last 30 days (100%). TrainsRadar data as of 22 Nov 2026, 10:10 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 10:59 from Toruń Główny · Mon 23 Nov

Next departure 10:59 tomorrow · Toruń Główny
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 4 full · 0 partial · 16 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 5 full · 0 partial · 48 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Sierpc, 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

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

  • Early 0% · 0
  • On time 100% · 5
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=1
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 5 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
10:59on time on time
11:02 / 11:03≈ on time ≈ on time
11:06≈ on time ≈ on time
11:12≈ on time ≈ on time
11:17≈ on time ≈ on time
11:23 / 11:24≈ on time ≈ on time
11:29 / 11:30≈ on time ≈ on time
11:36 / 11:42≈ on time ≈ on time
11:48 / 11:49≈ on time ≈ on time
11:55≈ on time ≈ on time
12:01 / 12:02≈ on time ≈ on time
12:08≈ on time ≈ on time
12:14≈ on time ≈ on time
12:20≈ on time ≈ on time
12:25 / 12:26≈ on time ≈ on time
12:32≈ on time ≈ on time
12:40on time 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 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
Fri 20 NovSierpc 12:400 min—
Thu 19 NovSierpc 12:39No data—
Wed 18 NovSierpc 12:39No data—
Tue 17 NovSierpc 12:39No data—
Mon 16 NovSierpc 12:42No data—
Fri 13 NovSierpc 12:39No data—
Thu 12 NovSierpc 12:39No data—
Tue 10 NovSierpc 12:39No data—
Mon 9 NovSierpc 12:420 min—
Fri 6 NovSierpc 12:39No data—
Thu 5 NovSierpc 12:39No data—
Wed 4 NovSierpc 12:39No data—
Tue 3 NovSierpc 12:40No data—
Mon 2 NovSierpc 12:390 min—
Sun 1 NovSierpc 12:41No data—
Fri 30 OctSierpc 12:41No data—
Thu 29 OctSierpc 12:41No data—
Wed 28 OctSierpc 12:41No data—
Tue 27 OctSierpc 12:41No data—
Mon 26 OctSierpc 12:410 min—
Fri 23 OctSierpc 12:41No data—
Thu 22 OctSierpc 12:41No data—
Wed 21 OctSierpc 12:41No data—
Tue 20 OctSierpc 12:42No data—
Mon 19 OctSierpc 12:41No data—
Fri 16 OctSierpc 12:41No data—
Thu 15 OctSierpc 12:41No data—
Wed 14 OctSierpc 12:42No data—
Tue 13 OctSierpc 12:41No data—
Mon 12 OctSierpc 12:410 min+2 min