REG 57250 Toruń Wschodni – Gniezno

View line REG

Toruń Wschodni 04:42 → Gniezno 06:10 Mon, Tue, Wed, Thu, Fri 1 h 28 min · 16 stops PolRegio

✓ Today’s run finished

Today it reached Gniezno at 06:10 0 min

  1. Toruń Wschodni04:42
  2. Toruń Kluczyki04:55
  3. Gniewkowo05:08
  4. Inowrocław05:21
  5. Kołodziejewo05:39
  6. Trzemeszno05:56
  7. Gniezno06:10
On-time · 30 days
74%
14/19 runs under 3 min
RT coverage: 19 full · 0 partial · 4 no data
On-time · 90 days
81%
22/27 runs under 3 min
RT coverage: 27 full · 0 partial · 7 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +6 min

Last 30 days

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

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

Worst days

  • Fri 6 Nov Max en route +13 min · last fix heading to Gniezno +13 min
  • Sun 1 Nov Max en route +8 min · last fix heading to Gniezno +8 min
  • Thu 15 Oct Max en route +5 min · last fix heading to Gniezno +5 min
  • Tue 10 Nov Max en route +3 min · last fix heading to Gniezno +3 min
  • Thu 29 Oct Max en route +3 min · last fix heading to Gniezno +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 22
  • 3–10 min 15% · 4
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 80% T n=5
  • 100% W n=5
  • 60% T n=5
  • 80% F n=5
  • — S n=0
  • 0% S n=1

Stops and timetable

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

Last 90 days, 27 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
04:42on time +4 min
04:45≈ on time ≈ +4 min
04:49 / 04:51≈ on time ≈ +4 min
04:55≈ on time ≈ +4 min
05:04≈ on time ≈ +4 min
05:08 / 05:09≈ on time ≈ +4 min
05:12≈ on time ≈ +4 min
05:16≈ on time ≈ +4 min
05:21 / 05:22≈ on time ≈ +4 min
05:34 / 05:35≈ on time ≈ +4 min
05:39 / 05:40≈ on time ≈ +4 min
05:45 / 05:46≈ on time ≈ +4 min
05:50 / 05:51≈ on time ≈ +4 min
05:56 / 05:57≈ on time ≈ +4 min
06:02≈ on time ≈ +4 min
06:10on time +4 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 13 NovGniezno 06:090 min—
Thu 12 NovGniezno 06:090 min—
Wed 11 NovGniezno 06:13+2 min+2 min
Tue 10 NovGniezno 06:14+3 min+3 min
Mon 9 NovGniezno 06:13+2 min+2 min
Fri 6 NovGniezno 06:24+13 min+13 min
Thu 5 NovGniezno 06:090 min—
Wed 4 NovGniezno 06:12+1 min+1 min
Tue 3 NovGniezno 06:090 min—
Mon 2 NovGniezno 06:090 min—
Sun 1 NovGniezno 06:19+8 min+8 min
Fri 30 OctGniezno 06:110 min—
Thu 29 OctGniezno 06:14+3 min+3 min
Wed 28 OctGniezno 06:110 min—
Tue 27 OctGniezno 06:110 min—
Mon 26 OctGniezno 06:110 min—
Fri 23 OctGniezno 06:11No data—
Thu 22 OctGniezno 06:11No data—
Wed 21 OctGniezno 06:11No data—
Tue 20 OctGniezno 06:11No data—
Mon 19 OctGniezno 06:12+1 min+1 min
Fri 16 OctGniezno 06:120 min—
Thu 15 OctGniezno 06:16+5 min+5 min
Wed 14 OctGniezno 06:110 min—
Tue 13 OctGniezno 06:110 min—
Mon 12 OctGniezno 06:120 min—
Fri 9 OctGniezno 06:110 min—
Thu 8 OctGniezno 06:110 min—
Wed 7 OctGniezno 06:110 min—
Tue 6 OctGniezno 06:110 min—