The excel version of Chainage file v3.3 prepared by me was tweaked to throw sections that are less than 1.5 km for inter-distance category. The uploaded file ( click here ) has the list with combinations that are less than 1.5 km, classified as per indianrail.gov.in as 1 km or rounded off to the next higher number i.e. 2 km. The rationale for picking up yellow highlighted combinations is as follows:
1. Filter for 1 km. 2S clearly goes to 58839 PDE-TPNI.
2. Similarly SL clearly goes to 57306 YKA-DQR.
3....
more... Just to ensure coverage of all 1 km sections, I have picked up 57563 MJF-DYE for FC and DYE-SFX for 3A.
4. Moving on to 2 Km filter, 13235 KIUL-LKR clearly wins the category for CC with only CC coaches in formation.
5. In 2A category, 12693 TME-TN wins with more variety in it
6. In 1A category, the other two sections have a representation, hence 19665 AGC-IDH wins by default.
Total Cost comes to 2700, plus iTicket charges as applicable. The lighter version for 1000 will exclude 1A and 2A (what I was planning to book!)
Here are the PNRs booked today (posted in PNR section):
2S - 8613602073
CC - 6520381083
SL - 4252138496
FC - 4805832448
3A - 4351876819
FC ticket cannot be booked in 1 km distance through an iTicket. IR has consciously(?) made the fare with nearly 16 decimals such that it gets rejected in Bank transaction. Guess it can be done over the counter. I have uploaded a screen dump (
click here ) for reference. Even 2693 has NOT AVAILABLE for 2 Km TME-TN stretch. Finally, I managed to book an eTicket.
Experts may clarify what is the bug in iTicket!!
I am planning to preserve these iTickets and when budget permits, I will book 2A and 1A too!