SDAH-NH LOCAL (31425) Historical Delay Report

The SDAH-NH LOCAL (31425) is highly reliable. Based on 7-day historical logs, it maintains an excellent punctuality record, typically arriving at NAIHATI JN just 0 minutes late. The only notable slowdown usually occurs near TITAGARH.

7-Day Average Delay Statistics

Station
SEALDAHSDAH
Sch. Arrival-Actual ArrivalSourceAvg. DelayOn Time
Station
BIDHAN NAGARBNXR
Sch. Arrival13:14Actual Arrival13:14Avg. DelayOn Time
Station
DUM DUMDDJ
Sch. Arrival13:18Actual Arrival13:21Avg. DelayOn Time / +3m
Station
BELGHARIABLH
Sch. Arrival13:23Actual Arrival13:26Avg. DelayOn Time / +3m
Station
AGARPARAAGP
Sch. Arrival13:26Actual Arrival13:26Avg. DelayOn Time
Station
SODPURSEP
Sch. Arrival13:29Actual Arrival13:34Avg. DelayOn Time / +5m
Station
KHARDAHAKDH
Sch. Arrival13:33Actual Arrival13:33Avg. DelayOn Time
Station
TITAGARHTGH
Sch. Arrival13:36Actual Arrival13:42Avg. DelayOn Time / +6m
Station
BARRACKPOREBP
Sch. Arrival13:41Actual Arrival13:45Avg. DelayOn Time / +4m
Station
PALTAPTF
Sch. Arrival13:44Actual Arrival13:44Avg. DelayOn Time
Station
ICHHAPURIP
Sch. Arrival13:47Actual Arrival13:52Avg. DelayOn Time / +5m
Station
SHYAMNAGARSNR
Sch. Arrival13:51Actual Arrival13:51Avg. DelayOn Time
Station
JAGADALJGDL
Sch. Arrival13:55Actual Arrival13:55Avg. DelayOn Time
Station
KANKINARAKNR
Sch. Arrival14:00Actual Arrival14:04Avg. DelayOn Time / +4m
Station
NAIHATI JNNH
Sch. Arrival14:10Actual Arrival14:10Avg. DelayOn Time

Frequently Asked Questions

Q: Is the SDAH-NH LOCAL (31425) usually on time?

A: Based on recent performance data, the SDAH-NH LOCAL maintains a Excellent punctuality record, arriving at its destination an average of 0 minutes late.

Q: Where is train 31425 delayed the most?

A: Historical running data indicates that the SDAH-NH LOCAL faces its highest average delays at TITAGARH.

Q: How can I check the past running status of the SDAH-NH LOCAL?

A: You can review the complete 7-day historical delay statistics, including average arrival and departure delays for all 15 stations, using the Train History tool above.