The scheduled September 13 Pune Yard block window has ended. Central Railway-attributed reports had set the nine-hour traffic and power block for 08:00 to 17:00 IST on Sunday, September 13, with seven trains cancelled and eleven other services short-terminated or short-originated from alternate Pune-area stations.
Those operating changes were specifically tied to September 13. Passengers travelling on September 14 or later should not use the September 13 cancellation and alternate-station list as a current timetable. TPS did not recover a direct Central Railway post-block restoration notice, so passengers should verify the live status of their exact train through current railway enquiry channels before travelling.
Current answer: The September 13 Pune Yard block is no longer an active scheduled block window. The seven cancellations and eleven changed-origin or changed-termination services listed below describe the September 13 operating plan, not an automatic September 14 schedule. Check the latest train-running status before leaving.
What was the September 13 Pune Yard block?
Current Central Railway-attributed reports described a nine-hour special traffic and power block at Pune Yard from 8 AM to 5 PM on September 13. The work involved engineering, signalling and electrical activity connected with yard and track upgrades on the Pune–Daund side.
The planned restrictions affected Platform No. 1 and main-line movements from the CSMT end, producing a mix of full cancellations, short terminations and short originations.
Which trains were cancelled on September 13?
The seven services reported as fully cancelled for the September 13 block were:
- 99902 Pune–Talegaon
- 99903 Talegaon–Pune
- 99818 Pune–Lonavala
- 99817 Lonavala–Shivajinagar
- 11007 CSMT–Pune Express
- 11008 Pune–CSMT Express
- 71407 Pune–Daund DEMU
These cancellations were part of the September 13 operating plan. They should not be assumed to continue on later dates without a separate railway instruction.
Which trains were short-terminated on September 13?
Seven Pune-bound services were reported to terminate at an alternate station during the block:
- 12940 Jaipur–Pune — Khadki
- 12136 Nagpur–Pune — Hadapsar
- 11406 Amravati–Pune — Hadapsar
- 12127 CSMT–Pune — Khadki
- 11078 Jammu Tawi–Pune — Hadapsar
- 99813 Lonavala–Pune — Shivajinagar
- 71406 Baramati–Pune — Daund
Which trains started from another station?
Four Pune-origin services were reported to start from an alternate station on September 13:
- 99820 Pune–Lonavala — Shivajinagar
- 12939 Pune–Jaipur — Khadki at 17:35
- 12135 Pune–Nagpur — Hadapsar at 17:45
- 12128 Pune–CSMT — Khadki at 17:55
Are these September 13 changes still active?
They should not be treated as current merely because they appeared in the September 13 operating plan. The scheduled block ended at 17:00 on September 13.
TPS did not identify current reporting that extended the same September 13 block into September 14. However, TPS also did not recover a direct Central Railway completion or restoration notice proving the exact time at which every affected service returned to its normal origin, destination or timetable.
For travel now, verify the current train number, running status, origin and destination rather than relying on the historical September 13 list.
How should passengers verify a train now?
Match the exact train number
Use the train number rather than only the route or service name, especially where similar Pune–Mumbai, Pune–Lonavala or Pune–Daund services operate.
Check the current origin
Confirm whether the train is currently starting from Pune Junction or another station before leaving for the station.
Check the current destination
For Pune-bound travel, verify that the train is operating to its normal terminus rather than relying on the September 13 short-termination plan.
Use current railway information
Check Indian Railways enquiry or other current official railway guidance close to departure because operational changes can be issued independently of the September 13 block.
Was Pune railway station completely closed?
No. The September 13 reports described a defined traffic and power block affecting specified Pune Yard lines and selected services, not a complete all-day shutdown of every train at Pune Junction.
The key passenger distinction was between trains that were fully cancelled and trains that continued to operate with a different origin or termination station.
Is this the same as the September 19 Pune–Hadapsar mega-block?
No. The September 13 Pune Yard block was a separate one-day operating event.
A different Pune-area infrastructure programme is scheduled to begin on September 19 and continue in phases into early October for work connected with the Hadapsar–Ghorpadi third-line project. That later block has its own cancellation, diversion, regulation and station-change plan and should be checked separately.
What remains unresolved?
- The controlling Central Railway notice or notice identifier for the September 13 block was not directly recovered by TPS.
- TPS did not recover a direct railway completion notice stating the exact restoration time after the planned 17:00 block end.
- Passenger-specific current train status cannot be inferred from the September 13 operating matrix.
- The September 19–October 4 Pune-area infrastructure blocks are a separate event with a different operating plan.
Verification note: ThePulseSignal compared multiple Central Railway-attributed reports for the September 13 block timing, seven cancellations and eleven short-termination or short-origination changes. Current checks found no evidence that the same September 13 block was extended into September 14. A direct Central Railway post-block restoration notice was not recovered, so current passenger travel should be verified through live railway information.
