REG 55246 Inowrocław – Mogilno

View line REG

Inowrocław 16:50 → Mogilno 17:11 Mon, Tue, Wed, Thu, Fri 0 h 21 min · 4 stops PolRegio

✓ Today’s run finished

Today it reached Mogilno at 17:11 −1 min

  1. Inowrocław16:50
  2. Janikowo16:59
  3. Kołodziejewo17:04
  4. Mogilno17:11

Next service: Monday 16:50 from Inowrocław · Mon 23 Nov

Next departure 16:50 Monday · Inowrocław
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 3 no data
On-time · 90 days
97%
35/36 runs under 3 min
RT coverage: 36 full · 0 partial · 16 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: +1 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 +7 min · last fix heading to Mogilno +7 min

Distribution · 90 days

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

  • Early 11% · 4
  • On time 86% · 31
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=8
  • — S n=0
  • 0% S n=1

Stops and timetable

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

Last 90 days, 36 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
16:50on time on time
16:59≈ on time ≈ on time
17:04≈ on time ≈ on time
17:11on 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 NovMogilno 17:09−1 min—
Thu 19 NovMogilno 17:09−1 min—
Wed 18 NovMogilno 17:120 min—
Tue 17 NovMogilno 17:120 min—
Mon 16 NovMogilno 17:130 min—
Fri 13 NovMogilno 17:10−1 min—
Thu 12 NovMogilno 17:120 min—
Wed 11 NovMogilno 17:12No data—
Tue 10 NovMogilno 17:120 min—
Mon 9 NovMogilno 17:120 min—
Fri 6 NovMogilno 17:120 min—
Thu 5 NovMogilno 17:120 min—
Wed 4 NovMogilno 17:120 min—
Tue 3 NovMogilno 17:130 min—
Mon 2 NovMogilno 17:120 min—
Sun 1 NovMogilno 17:19+7 min+7 min
Fri 30 OctMogilno 17:120 min—
Thu 29 OctMogilno 17:120 min—
Wed 28 OctMogilno 17:15+3 min+3 min
Tue 27 OctMogilno 17:13+1 min+1 min
Mon 26 OctMogilno 17:130 min—
Fri 23 OctMogilno 17:09No data—
Thu 22 OctMogilno 17:09No data—
Wed 21 OctMogilno 17:09No data—
Tue 20 OctMogilno 17:08No data—
Mon 19 OctMogilno 17:08No data—
Fri 16 OctMogilno 17:080 min—
Thu 15 OctMogilno 17:09+1 min—
Wed 14 OctMogilno 17:080 min—
Tue 13 OctMogilno 17:090 min—