AR 50982 Toruń Główny – Sierpc

View line AR

Toruń Główny 08:54 → Sierpc 10:31 Daily 1 h 37 min · 17 stops Arriva

✓ Today’s run finished

Today, last fix heading to Sierpc at 10:32 No data

  1. Toruń Główny08:54
  2. Grębocin09:06
  3. Dobrzejewice09:18
  4. Ograszka09:37
  5. Karnkowo09:57
  6. Czermno10:10
  7. Sierpc10:31

Next service: tomorrow 08:54 from Toruń Główny · Sat 7 Nov

Next departure 08:54 tomorrow · Toruń Główny
On-time · 30 days
100%
3/3 runs under 3 min
RT coverage: 3 full · 0 partial · 27 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 5 full · 0 partial · 62 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+1min
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=3
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • — S n=0
  • 100% S n=2

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
08:54on time +1 min
08:57 / 08:58≈ on time ≈ +1 min
09:01≈ on time ≈ +1 min
09:06 / 09:07≈ on time ≈ +1 min
09:12≈ on time ≈ +1 min
09:18 / 09:19≈ on time ≈ +1 min
09:24≈ on time ≈ +1 min
09:31≈ on time ≈ +1 min
09:37 / 09:38≈ on time ≈ +1 min
09:44≈ +1 min ≈ +1 min
09:51 / 09:52≈ +1 min ≈ +1 min
09:57 / 09:58≈ +1 min ≈ +1 min
10:04 / 10:05≈ +1 min ≈ +1 min
10:10 / 10:11≈ +1 min ≈ +1 min
10:16≈ +1 min ≈ +1 min
10:23≈ +1 min ≈ +1 min
10:31+1 min +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
Fri 6 NovSierpc 10:32No data—
Thu 5 NovSierpc 10:32No data—
Wed 4 NovSierpc 10:32No data—
Tue 3 NovSierpc 10:32No data—
Mon 2 NovSierpc 10:33+1 min+1 min
Sun 1 NovSierpc 10:33No data—
Sat 31 OctSierpc 10:32No data—
Fri 30 OctSierpc 10:32No data—
Thu 29 OctSierpc 10:32No data—
Wed 28 OctSierpc 10:32No data—
Tue 27 OctSierpc 10:32No data—
Mon 26 OctSierpc 10:33+1 min+1 min
Sun 25 OctSierpc 10:32No data—
Sat 24 OctSierpc 10:35No data—
Fri 23 OctSierpc 10:35No data—
Thu 22 OctSierpc 10:35No data—
Wed 21 OctSierpc 10:35No data—
Tue 20 OctSierpc 10:35No data—
Mon 19 OctSierpc 10:35No data—
Sun 18 OctSierpc 10:35No data—
Sat 17 OctSierpc 10:35No data—
Fri 16 OctSierpc 10:35No data—
Thu 15 OctSierpc 10:35No data—
Wed 14 OctSierpc 10:36No data—
Tue 13 OctSierpc 10:35No data—
Mon 12 OctSierpc 10:350 min—
Sun 11 OctSierpc 10:35No data—
Sat 10 OctSierpc 10:35No data—
Fri 9 OctSierpc 10:36No data—
Thu 8 OctSierpc 10:35No data—