BT -SDAH LOCAL (33438) Historical Delay Report

The BT -SDAH LOCAL (33438) is highly reliable. Based on 7-day historical logs, it maintains an excellent punctuality record, typically arriving at SEALDAH just 3 minutes late. The only notable slowdown usually occurs near MADHYAMGRAM.

7-Day Average Delay Statistics

Station
BARASATBT
Sch. Arrival-Actual ArrivalSourceAvg. DelayOn Time
Station
HRIDAYPURHHR
Sch. Arrival14:50Actual Arrival14:50Avg. DelayOn Time
Station
MADHYAMGRAMMMG
Sch. Arrival14:53Actual Arrival14:57Avg. DelayOn Time / +4m
Station
NEW BARRACKPORENBE
Sch. Arrival14:56Actual Arrival14:56Avg. DelayOn Time
Station
BISHARPARA KODALIABRPK
Sch. Arrival14:59Actual Arrival14:59Avg. DelayOn Time
Station
BIRATIBBT
Sch. Arrival15:02Actual Arrival15:06Avg. DelayOn Time / +4m
Station
DURGANAGARDGNR
Sch. Arrival15:05Actual Arrival15:05Avg. DelayOn Time
Station
DUM DUM CANTDDC
Sch. Arrival15:08Actual Arrival15:12Avg. DelayOn Time / +4m
Station
DUM DUMDDJ
Sch. Arrival15:16Actual Arrival15:18Avg. DelayOn Time / +2m
Station
BIDHAN NAGARBNXR
Sch. Arrival15:20Actual Arrival15:20Avg. DelayOn Time
Station
SEALDAHSDAH
Sch. Arrival15:35Actual Arrival15:38Avg. DelayOn Time / +3m

Frequently Asked Questions

Q: Is the BT -SDAH LOCAL (33438) usually on time?

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

Q: Where is train 33438 delayed the most?

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

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

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