REG 55234 Toruń Wschodni – Mogilno

View line REG

Toruń Wschodni 18:07 → Mogilno 19:26 Mon, Tue, Wed, Thu, Fri, Sun 1 h 19 min · 12 stops PKP

It has not run yet today

Last recorded run: Wednesday 4 November −3 min

Next service: today 18:07 from Toruń Wschodni · Thu 5 Nov

Next departure 18:07 today · Toruń Wschodni
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Mogilno, 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 +11 min · last fix heading to Mogilno +11 min

Distribution · 90 days

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

  • Early 19% · 5
  • On time 77% · 20
  • 3–10 min 0% · 0
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=4
  • 100% T n=3
  • 100% F n=4
  • 100% S n=3
  • 75% S n=4

Stops and timetable

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

Last 90 days, 26 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
18:07on time on time
18:10≈ on time ≈ on time
18:14 / 18:16≈ on time ≈ on time
18:20 / 18:21≈ on time ≈ on time
18:31≈ on time ≈ on time
18:36≈ on time ≈ on time
18:40≈ on time ≈ on time
18:44 / 18:45≈ on time ≈ on time
18:50 / 18:58≈ on time ≈ on time
19:10≈ on time ≈ on time
19:15 / 19:16≈ on time ≈ on time
19:26on 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
Wed 4 NovMogilno 19:24−3 min—
Tue 3 NovMogilno 19:25−3 min—
Mon 2 NovMogilno 19:270 min—
Sun 1 NovMogilno 19:38+11 min+11 min
Sat 31 OctCiechocinek 10:470 min—
Fri 30 OctMogilno 19:25−2 min—
Thu 29 OctMogilno 19:270 min—
Wed 28 OctMogilno 19:23−4 min—
Tue 27 OctMogilno 19:25−2 min—
Mon 26 OctMogilno 19:280 min—
Sun 25 OctCiechocinek 10:47No data—
Sat 24 OctCiechocinek 10:48No data—
Fri 23 OctMogilno 19:06No data—
Thu 22 OctMogilno 19:06No data—
Wed 21 OctMogilno 19:05No data—
Tue 20 OctMogilno 19:05No data—
Mon 19 OctMogilno 19:05No data—
Sun 18 OctCiechocinek 10:480 min—
Sat 17 OctCiechocinek 10:480 min—
Fri 16 OctMogilno 19:05−1 min—
Thu 15 OctMogilno 19:050 min—
Wed 14 OctMogilno 19:050 min—
Tue 13 OctMogilno 19:050 min—
Mon 12 OctMogilno 19:050 min—
Sun 11 OctCiechocinek 10:480 min—
Sat 10 OctCiechocinek 10:480 min—
Fri 9 OctMogilno 19:050 min—
Thu 8 OctMogilno 19:050 min—
Wed 7 OctMogilno 19:050 min—
Tue 6 OctMogilno 19:050 min—