Invalid value 00309 - RAMPUR HAT - AZIMGANJ MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9931 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 00309 | 00309 | 00309 - RAMPUR HAT - AZIMGANJ MEMU Special | 2 | | | | | | | | | | |
Invalid value 01193 - MUMBAI LTT - KARMALI Summer Special (Starts 7 April) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9932 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01193 | 01193 | 01193 - MUMBAI LTT - KARMALI Summer Special (Starts 7 April) | 2 | | | | | | | | | | |
Invalid value 01194 - KARMALI - MUMBAI LTT SF Summer Special (Starts 7 April) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9933 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01194 | 01194 | 01194 - KARMALI - MUMBAI LTT SF Summer Special (Starts 7 April) | 2 | | | | | | | | | | |
Invalid value 01655 - Pune Jbp Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9934 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01655 | 01655 | 01655 - Pune Jbp Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 01656 - Jbp Pune Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9935 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01656 | 01656 | 01656 - Jbp Pune Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 01661 - Hbj Puri Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9936 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01661 | 01661 | 01661 - Hbj Puri Special | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 01662 - PURI HBJ SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9937 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01662 | 01662 | 01662 - PURI HBJ SPL | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 01663 - DWR HBJ EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9938 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01663 | 01663 | 01663 - DWR HBJ EXP | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 01664 - Hbj Dharwar Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9939 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01664 | 01664 | 01664 - Hbj Dharwar Express | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 01665 - Hbj Agartala Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9940 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01665 | 01665 | 01665 - Hbj Agartala Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 01666 - Agtl Hbj Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9941 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01666 | 01666 | 01666 - Agtl Hbj Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 01667 - YPR ERS EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9942 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01667 | 01667 | 01667 - YPR ERS EXP | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 01668 - YESVANTPUR EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9943 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01668 | 01668 | 01668 - YESVANTPUR EXP | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 01705 - BDTS JBP SUP SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9944 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01705 | 01705 | 01705 - BDTS JBP SUP SPL | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 01706 - Jbp Bdts Sup Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9945 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01706 | 01706 | 01706 - Jbp Bdts Sup Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 01707 - Jbp Atari Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9946 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01707 | 01707 | 01707 - Jbp Atari Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 01708 - Att Jbp Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9947 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 01708 | 01708 | 01708 - Att Jbp Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 02193 - Ten Jbp Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9948 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02193 | 02193 | 02193 - Ten Jbp Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 02194 - Jbp Ten Sup Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9949 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02194 | 02194 | 02194 - Jbp Ten Sup Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 02195 - Rewa Bpl Sf Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9950 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02195 | 02195 | 02195 - Rewa Bpl Sf Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 02196 - Bpl Rewa Sf Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9951 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02196 | 02196 | 02196 - Bpl Rewa Sf Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 02197 - CBE JBP EXPRESS in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9952 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02197 | 02197 | 02197 - CBE JBP EXPRESS | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 02198 - Jbp Cbe Sup Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9953 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02198 | 02198 | 02198 - Jbp Cbe Sup Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 02375 - ASN JSME SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9954 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02375 | 02375 | 02375 - ASN JSME SPL | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 02376 - JSME ASN SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9955 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02376 | 02376 | 02376 - JSME ASN SPL | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 02485 - Ned Nzm Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9956 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02485 | 02485 | 02485 - Ned Nzm Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 02486 - Nzm Ned Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9957 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02486 | 02486 | 02486 - Nzm Ned Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 02731 - Hyb Jp Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9958 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02731 | 02731 | 02731 - Hyb Jp Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 02732 - Jp Hyb Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9959 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02732 | 02732 | 02732 - Jp Hyb Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 02841 - SANTRAGACHI - CHENNAI CENTRAL SF Express (Start 18 Jan) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9960 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02841 | 02841 | 02841 - SANTRAGACHI - CHENNAI CENTRAL SF Express (Start 18 Jan) | 2 | | | | | | | | | | |
Invalid value 02842 - CHENNAI CENTRAL - SANTRAGACHI SF Express (Start 19 Jan) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9961 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 02842 | 02842 | 02842 - CHENNAI CENTRAL - SANTRAGACHI SF Express (Start 19 Jan) | 2 | | | | | | | | | | |
Invalid value 03021 - BALGONA - KATWA Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9962 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 03021 | 03021 | 03021 - BALGONA - KATWA Special | 2 | | | | | | | | | | |
Invalid value 03022 - KATWA - BALGONA Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9963 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 03022 | 03022 | 03022 - KATWA - BALGONA Passenger Special | 2 | | | | | | | | | | |
Invalid value 03219 - RAGHUNATHPUR - BUXAR MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9964 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 03219 | 03219 | 03219 - RAGHUNATHPUR - BUXAR MEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 03220 - BUXAR - RAGHUNATHPUR MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9965 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 03220 | 03220 | 03220 - BUXAR - RAGHUNATHPUR MEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 03301 - ASANSOL - DHANBAD MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9966 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 03301 | 03301 | 03301 - ASANSOL - DHANBAD MEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 03302 - DHANBAD - ASANSOL MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9967 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 03302 | 03302 | 03302 - DHANBAD - ASANSOL MEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 03601 - BUXAR - PT DEEN DAYAL UPADHYAYA Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9968 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 03601 | 03601 | 03601 - BUXAR - PT DEEN DAYAL UPADHYAYA Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 03602 - PT DEEN DAYAL UPADHYAYA - BUXAR Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9969 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 03602 | 03602 | 03602 - PT DEEN DAYAL UPADHYAYA - BUXAR Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04767 - HANUMANGARH - SHRI GANGANAGAR Passenger SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9970 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04767 | 04767 | 04767 - HANUMANGARH - SHRI GANGANAGAR Passenger SPL | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04768 - SHRI GANGANAGAR - HANUMANGARH Passenger SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9971 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04768 | 04768 | 04768 - SHRI GANGANAGAR - HANUMANGARH Passenger SPL | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04769 - HANUMANGARH - SHRI GANGANAGAR Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9972 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04769 | 04769 | 04769 - HANUMANGARH - SHRI GANGANAGAR Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04770 - SHRI GANGANAGAR - HANUMANGARH Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9973 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04770 | 04770 | 04770 - SHRI GANGANAGAR - HANUMANGARH Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04773 - SHRI GANGANAGAR - SURATGARH Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9974 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04773 | 04773 | 04773 - SHRI GANGANAGAR - SURATGARH Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04774 - SURATGARH - SHRI GANGANAGAR Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9975 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04774 | 04774 | 04774 - SURATGARH - SHRI GANGANAGAR Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04775 - SADULPUR - HANUMANGARH Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9976 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04775 | 04775 | 04775 - SADULPUR - HANUMANGARH Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04776 - HANUMANGARH - SADULPUR Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9977 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04776 | 04776 | 04776 - HANUMANGARH - SADULPUR Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04777 - SADULPUR - HANUMANGARH Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9978 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04777 | 04777 | 04777 - SADULPUR - HANUMANGARH Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04778 - HANUMANGARH - SADULPUR Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9979 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04778 | 04778 | 04778 - HANUMANGARH - SADULPUR Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04801 - Ju Dee Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9980 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04801 | 04801 | 04801 - Ju Dee Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04802 - Ngo Ju Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9981 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04802 | 04802 | 04802 - Ngo Ju Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04805 - ALWAR - KHAIRTHAL Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9982 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04805 | 04805 | 04805 - ALWAR - KHAIRTHAL Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04806 - KHAIRTHAL - ALWAR Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9983 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04806 | 04806 | 04806 - KHAIRTHAL - ALWAR Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04851 - MERTA ROAD - RATANGARH DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9984 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04851 | 04851 | 04851 - MERTA ROAD - RATANGARH DEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04852 - RATANGARH - MERTA ROAD DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9985 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04852 | 04852 | 04852 - RATANGARH - MERTA ROAD DEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04853 - RATANGARH - CHURU DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9986 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04853 | 04853 | 04853 - RATANGARH - CHURU DEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 04854 - CHURU - RATANGARH DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9987 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 04854 | 04854 | 04854 - CHURU - RATANGARH DEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 05069 - BNZ ASH SPECIAL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9988 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05069 | 05069 | 05069 - BNZ ASH SPECIAL | 2 | | | | | | | | | | |
Invalid value 05070 - ASH BNZ SPECIAL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9989 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05070 | 05070 | 05070 - ASH BNZ SPECIAL | 2 | | | | | | | | | | |
Invalid value 05305 - KANPUR ANWARGANJ - FARRUKHABAD Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9990 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05305 | 05305 | 05305 - KANPUR ANWARGANJ - FARRUKHABAD Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 05306 - FARRUKHABAD - KANPUR ANWARGANJ Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9991 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05306 | 05306 | 05306 - FARRUKHABAD - KANPUR ANWARGANJ Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 05309 - BAREILLY - LALKUAN Exp SPL (Unreserved) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9992 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05309 | 05309 | 05309 - BAREILLY - LALKUAN Exp SPL (Unreserved) | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 05310 - LALKUAN - BAREILLY Exp SPL (Unreserved) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9993 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05310 | 05310 | 05310 - LALKUAN - BAREILLY Exp SPL (Unreserved) | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 05521 - JAMALPUR - SAHARSA Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9994 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05521 | 05521 | 05521 - JAMALPUR - SAHARSA Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 05522 - SAHARSA - JAMALPUR Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9995 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05522 | 05522 | 05522 - SAHARSA - JAMALPUR Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 05613 - JHALAWAR CITY - KOTA Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9996 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05613 | 05613 | 05613 - JHALAWAR CITY - KOTA Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 05614 - KOTA - JHALAWAR CITY Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9997 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05614 | 05614 | 05614 - KOTA - JHALAWAR CITY Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 05683 - BIR - ITARSI Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9998 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05683 | 05683 | 05683 - BIR - ITARSI Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 05684 - ITARSI - BIR Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 9999 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05684 | 05684 | 05684 - ITARSI - BIR Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 05715 - NEW JALPAIGURI - KISHANGANJ Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10000 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05715 | 05715 | 05715 - NEW JALPAIGURI - KISHANGANJ Passenger | 2 | | | | | | | | | | |
Invalid value 05716 - KISHANGANJ - NEW JALPAIGURI Gareeb Nawaz Eyrake in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10001 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 05716 | 05716 | 05716 - KISHANGANJ - NEW JALPAIGURI Gareeb Nawaz Eyrake | 2 | | | | | | | | | | |
Invalid value 06083 - Mdu Cbe Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10002 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06083 | 06083 | 06083 - Mdu Cbe Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06084 - Cbe Mdu Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10003 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06084 | 06084 | 06084 - Cbe Mdu Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06085 - Ms Vlnk Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10004 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06085 | 06085 | 06085 - Ms Vlnk Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06086 - Vlnk Tbm Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10005 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06086 | 06086 | 06086 - Vlnk Tbm Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06512 - Jp Ypr Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10006 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06512 | 06512 | 06512 - Jp Ypr Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06513 - Sbc Pnbe Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10007 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06513 | 06513 | 06513 - Sbc Pnbe Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06567 - WHITEFIELD - BAIYYAPPANAHALI MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10008 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06567 | 06567 | 06567 - WHITEFIELD - BAIYYAPPANAHALI MEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06568 - BAIYYAPPANAHALI - WHITEFIELD MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10009 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06568 | 06568 | 06568 - BAIYYAPPANAHALI - WHITEFIELD MEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06569 - BAIYYAPPANAHALI - BANGALORE CITY MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10010 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06569 | 06569 | 06569 - BAIYYAPPANAHALI - BANGALORE CITY MEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06570 - Ngp Bnc Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10011 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06570 | 06570 | 06570 - Ngp Bnc Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06571 - Tiruchchi Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10012 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06571 | 06571 | 06571 - Tiruchchi Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06572 - HOSUR - BANASWADI DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10013 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06572 | 06572 | 06572 - HOSUR - BANASWADI DEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06573 - BANASWADI - HOSUR DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10014 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06573 | 06573 | 06573 - BANASWADI - HOSUR DEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06574 - HOSUR - BANASWADI DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10015 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06574 | 06574 | 06574 - HOSUR - BANASWADI DEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06575 - KSR BENGALURU - MYSORE MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10016 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06575 | 06575 | 06575 - KSR BENGALURU - MYSORE MEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06576 - KCVL YPR EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10017 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06576 | 06576 | 06576 - KCVL YPR EXP | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06577 - WHITEFIELD - BANASWADI DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10018 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06577 | 06577 | 06577 - WHITEFIELD - BANASWADI DEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06578 - BANASWADI - WHITEFIELD DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10019 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06578 | 06578 | 06578 - BANASWADI - WHITEFIELD DEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06591 - YESVANTPUR - HOSUR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10020 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06591 | 06591 | 06591 - YESVANTPUR - HOSUR Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06592 - HOSUR - YESVANTPUR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10021 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06592 | 06592 | 06592 - HOSUR - YESVANTPUR Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06593 - WHITEFIELD - BAIYYAPPANHALLI DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10022 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06593 | 06593 | 06593 - WHITEFIELD - BAIYYAPPANHALLI DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06594 - BAIYYAPPANHALI - WHITEFIELD DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10023 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06594 | 06594 | 06594 - BAIYYAPPANHALI - WHITEFIELD DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06595 - YESVANTPUR - DEVANAHALLI Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10024 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06595 | 06595 | 06595 - YESVANTPUR - DEVANAHALLI Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06596 - DEVANAHALLI - YESVANTPUR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10025 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06596 | 06596 | 06596 - DEVANAHALLI - YESVANTPUR Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06709 - COIMBATORE MAIN - PALANI Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10026 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06709 | 06709 | 06709 - COIMBATORE MAIN - PALANI Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06710 - PALANI - COIMBATORE MAIN Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10027 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06710 | 06710 | 06710 - PALANI - COIMBATORE MAIN Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06833 - KARUR - SALEM DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10028 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06833 | 06833 | 06833 - KARUR - SALEM DEMU Special | 2 | | | | | | | | | | |
Invalid value 06834 - SALEM - KARUR DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10029 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06834 | 06834 | 06834 - SALEM - KARUR DEMU Special | 2 | | | | | | | | | | |
Invalid value 06855 - PATTUKOTTAI - KARAIKKUDI DEMU Special (Start 14 Jan) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10030 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06855 | 06855 | 06855 - PATTUKOTTAI - KARAIKKUDI DEMU Special (Start 14 Jan) | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06856 - KARAIKKUDI - PATTUKOTTAI DEMU Special (Start 14 Jan) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10031 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06856 | 06856 | 06856 - KARAIKKUDI - PATTUKOTTAI DEMU Special (Start 14 Jan) | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06863 - MANNARGUDI - TIRUCHCHIRAPPALLI Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10032 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06863 | 06863 | 06863 - MANNARGUDI - TIRUCHCHIRAPPALLI Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06864 - TIRUCHCHIRAPALI - MANNARGUDI Special (UnReserved) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10033 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06864 | 06864 | 06864 - TIRUCHCHIRAPALI - MANNARGUDI Special (UnReserved) | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06865 - THANJAVUR - TIRUCHCHIRAPPALLI Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10034 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06865 | 06865 | 06865 - THANJAVUR - TIRUCHCHIRAPPALLI Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 06866 - TIRUCHCHIRAPPALLI - THANJAVUR Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10035 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 06866 | 06866 | 06866 - TIRUCHCHIRAPPALLI - THANJAVUR Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 07005 - Hyb Rxl Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10036 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07005 | 07005 | 07005 - Hyb Rxl Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07006 - Rxl Hyb Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10037 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07006 | 07006 | 07006 - Rxl Hyb Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07007 - Sc Dbg Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10038 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07007 | 07007 | 07007 - Sc Dbg Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07008 - Dbg Sc Wkly Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10039 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07008 | 07008 | 07008 - Dbg Sc Wkly Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07009 - Sc Bju Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10040 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07009 | 07009 | 07009 - Sc Bju Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07010 - Bju Sc Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10041 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07010 | 07010 | 07010 - Bju Sc Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07016 - Kcg Vskp Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10042 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07016 | 07016 | 07016 - Kcg Vskp Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07049 - MTM SC SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10043 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07049 | 07049 | 07049 - MTM SC SPL | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07050 - SC MTM SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10044 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07050 | 07050 | 07050 - SC MTM SPL | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07091 - Sc Rxl Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10045 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07091 | 07091 | 07091 - Sc Rxl Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07092 - Rxl Sc Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10046 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07092 | 07092 | 07092 - Rxl Sc Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07115 - Hyb Kcvl Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10047 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07115 | 07115 | 07115 - Hyb Kcvl Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07116 - Hyderabad Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10048 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07116 | 07116 | 07116 - Hyderabad Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07117 - Hyb Ers Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10049 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07117 | 07117 | 07117 - Hyb Ers Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07118 - Ers Hyb Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10050 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07118 | 07118 | 07118 - Ers Hyb Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07149 - Sc Kyq Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10051 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07149 | 07149 | 07149 - Sc Kyq Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07150 - Kyq Sc Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10052 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07150 | 07150 | 07150 - Kyq Sc Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07237 - CCT KRNT SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10053 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07237 | 07237 | 07237 - CCT KRNT SPL | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07238 - KRNT CCT SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10054 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07238 | 07238 | 07238 - KRNT CCT SPL | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07245 - Cct Rc Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10055 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07245 | 07245 | 07245 - Cct Rc Special | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07246 - Rc Cct Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10056 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07246 | 07246 | 07246 - Rc Cct Special | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07257 - Hyb Bza Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10057 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07257 | 07257 | 07257 - Hyb Bza Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07258 - Ns Hyb Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10058 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07258 | 07258 | 07258 - Ns Hyb Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07417 - Tpty Nsl Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10059 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07417 | 07417 | 07417 - Tpty Nsl Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07418 - Nsl Tpty Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10060 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07418 | 07418 | 07418 - Nsl Tpty Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07425 - Kcg Coa Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10061 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07425 | 07425 | 07425 - Kcg Coa Special | 2 | 0 | 1 | 1 | 1 | | | 1 | 0 | | |
Invalid value 07426 - Coa Kcg Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10062 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07426 | 07426 | 07426 - Coa Kcg Special | 2 | 0 | 1 | 1 | 1 | | | 1 | 0 | | |
Invalid value 07435 - KAKINADA TOWN - SECUNDERABAD Special (Start 08 Feb) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10063 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07435 | 07435 | 07435 - KAKINADA TOWN - SECUNDERABAD Special (Start 08 Feb) | 2 | | | | | | | | | | |
Invalid value 07438 - Kcg Tata Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10064 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07438 | 07438 | 07438 - Kcg Tata Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07439 - Tata Kcg Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10065 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07439 | 07439 | 07439 - Tata Kcg Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07479 - Vskp Tpty Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10066 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07479 | 07479 | 07479 - Vskp Tpty Special | 2 | 0 | 1 | 1 | 1 | | | 1 | 0 | | |
Invalid value 07526 - NEW BONGAIGAON - SILIGURI DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10067 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07526 | 07526 | 07526 - NEW BONGAIGAON - SILIGURI DEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 07607 - Ned Tpty Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10068 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07607 | 07607 | 07607 - Ned Tpty Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07608 - Tpty Ned Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10069 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07608 | 07608 | 07608 - Tpty Ned Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 07617 - Ned Pnvl Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10070 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07617 | 07617 | 07617 - Ned Pnvl Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 07618 - Pnvl Nanded Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10071 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07618 | 07618 | 07618 - Pnvl Nanded Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 07941 - KAKINADA TOWN - RENIGUNTA Special (Start 04 March) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10072 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07941 | 07941 | 07941 - KAKINADA TOWN - RENIGUNTA Special (Start 04 March) | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 07942 - TIRUPATI MAIN - KAKINADA TOWN Special (Start 03 March) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10073 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 07942 | 07942 | 07942 - TIRUPATI MAIN - KAKINADA TOWN Special (Start 03 March) | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08011 - CHAKRADHARPUR - TATANAGAR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10074 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08011 | 08011 | 08011 - CHAKRADHARPUR - TATANAGAR DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08012 - TATANAGAR - CHAKRADHARPUR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10075 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08012 | 08012 | 08012 - TATANAGAR - CHAKRADHARPUR DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08017 - KHARAGPUR - JHARGRAM MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10076 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08017 | 08017 | 08017 - KHARAGPUR - JHARGRAM MEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08018 - JHARGRAM - KHARAGPUR MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10077 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08018 | 08018 | 08018 - JHARGRAM - KHARAGPUR MEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08035 - KHARAGPUR - BALASORE DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10078 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08035 | 08035 | 08035 - KHARAGPUR - BALASORE DEMU Special | 2 | | | | | | | | | | |
Invalid value 08036 - BALASORE - KHARAGPUR DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10079 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08036 | 08036 | 08036 - BALASORE - KHARAGPUR DEMU Special | 2 | | | | | | | | | | |
Invalid value 08051 - KHARAGPUR - JHARGRAM MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10080 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08051 | 08051 | 08051 - KHARAGPUR - JHARGRAM MEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08052 - JHARGRAM - KHARAGPUR MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10081 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08052 | 08052 | 08052 - JHARGRAM - KHARAGPUR MEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08061 - SHALIMAR - JAIPUR Special (Start 14 Jan) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10082 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08061 | 08061 | 08061 - SHALIMAR - JAIPUR Special (Start 14 Jan) | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 08062 - JAIPUR - SHALIMAR Special (Start 16 Jan) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10083 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08062 | 08062 | 08062 - JAIPUR - SHALIMAR Special (Start 16 Jan) | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 08063 - KHARAGPUR - BANKURA DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10084 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08063 | 08063 | 08063 - KHARAGPUR - BANKURA DEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08064 - Ypr Hwh Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10085 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08064 | 08064 | 08064 - Ypr Hwh Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08065 - KHARAGPUR - BANKURA DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10086 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08065 | 08065 | 08065 - KHARAGPUR - BANKURA DEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08501 - Vskp Sc Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10087 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08501 | 08501 | 08501 - Vskp Sc Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 08502 - Sc Vskp Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10088 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08502 | 08502 | 08502 - Sc Vskp Special | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 08581 - BALHARSHAH - CHANDA FORT Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10089 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08581 | 08581 | 08581 - BALHARSHAH - CHANDA FORT Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08582 - CHANDA FORT - BALHARSHAH Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10090 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08582 | 08582 | 08582 - CHANDA FORT - BALHARSHAH Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08627 - Hwh Rnc Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10091 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08627 | 08627 | 08627 - Hwh Rnc Special | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 08628 - Rnc Hwh Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10092 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08628 | 08628 | 08628 - Rnc Hwh Special | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 08871 - GONDIA - DURG DEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10093 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08871 | 08871 | 08871 - GONDIA - DURG DEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08872 - DURG - GONDIA Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10094 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08872 | 08872 | 08872 - DURG - GONDIA Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08873 - DURG - DALLI RAJHARA Passenger Spl in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10095 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08873 | 08873 | 08873 - DURG - DALLI RAJHARA Passenger Spl | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 08874 - DALLI RAJHARA - GONDIA Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10096 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 08874 | 08874 | 08874 - DALLI RAJHARA - GONDIA Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 09069 - VAPI - SURAT Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10097 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 09069 | 09069 | 09069 - VAPI - SURAT Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 09070 - SURAT - VALSAD MEMU Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10098 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 09070 | 09070 | 09070 - SURAT - VALSAD MEMU Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 09072 - VALSAD - VAPI Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10099 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 09072 | 09072 | 09072 - VALSAD - VAPI Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 09601 - MAVLI - MARWAR Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10100 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 09601 | 09601 | 09601 - MAVLI - MARWAR Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 09602 - BEAS AII SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10101 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 09602 | 09602 | 09602 - BEAS AII SPL | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 09621 - AII BDTS SF SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10102 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 09621 | 09621 | 09621 - AII BDTS SF SPL | 2 | | | | | | | | | | |
Invalid value 09622 - BDTS AII SF SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10103 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 09622 | 09622 | 09622 - BDTS AII SF SPL | 2 | | | | | | | | | | |
Invalid value 09722 - Udz Jp Sf T Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10104 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 09722 | 09722 | 09722 - Udz Jp Sf T Special | 2 | 1 | 0 | 0 | 1 | | | 1 | 0 | | |
Invalid value 09723 - JP BDTS SF SPL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10105 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 09723 | 09723 | 09723 - JP BDTS SF SPL | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 09724 - MUMBAI BANDRA T - JAIPUR SF Special (Start 24 Jan) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10106 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 09724 | 09724 | 09724 - MUMBAI BANDRA T - JAIPUR SF Special (Start 24 Jan) | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 09762 - SURATGARH - SHRI GANGANAGAR Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10107 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 09762 | 09762 | 09762 - SURATGARH - SHRI GANGANAGAR Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 09763 - SURATGARH - HANUMANGARH Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10108 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 09763 | 09763 | 09763 - SURATGARH - HANUMANGARH Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 09764 - HANUMANGARH - SURATGARH Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10109 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 09764 | 09764 | 09764 - HANUMANGARH - SURATGARH Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 11065 - Mys Ru Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10110 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 11065 | 11065 | 11065 - Mys Ru Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 11066 - Ru Mys Wkly Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10111 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 11066 | 11066 | 11066 - Ru Mys Wkly Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 11139 - Csmt Gadag Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10112 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 11139 | 11139 | 11139 - Csmt Gadag Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 11140 - Gdg Csmt Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10113 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 11140 | 11140 | 11140 - Gdg Csmt Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 11273 - Itarsi - Katni Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10114 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 11273 | 11273 | 11273 - Itarsi - Katni Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 11274 - KATNI - ITARSI Express (UnReserved) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10115 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 11274 | 11274 | 11274 - KATNI - ITARSI Express (UnReserved) | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 11311 - Sur Hasan Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10116 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 11311 | 11311 | 11311 - Sur Hasan Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 11312 - Solapur Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10117 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 11312 | 11312 | 11312 - Solapur Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 11415 - Bidr Kop Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10118 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 11415 | 11415 | 11415 - Bidr Kop Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 11416 - Kop Bidr Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10119 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 11416 | 11416 | 11416 - Kop Bidr Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 12089 - Af Jan Shatabdi in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10120 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 12089 | 12089 | 12089 - Af Jan Shatabdi | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 12090 - Aii Jan Shatabdi in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10121 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 12090 | 12090 | 12090 - Aii Jan Shatabdi | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 12091 - Naini Doon Jan Shatabdi in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10122 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 12091 | 12091 | 12091 - Naini Doon Jan Shatabdi | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 12092 - Naini Doon Jan Shatabdi in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10123 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 12092 | 12092 | 12092 - Naini Doon Jan Shatabdi | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 12751 - Mugr Sc Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10124 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 12751 | 12751 | 12751 - Mugr Sc Express | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 12752 - Jat Ned Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10125 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 12752 | 12752 | 12752 - Jat Ned Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 13173 - Kanchanjunga Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10126 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 13173 | 13173 | 13173 - Kanchanjunga Express | 2 | 0 | 1 | 1 | 1 | | | 1 | 0 | | |
Invalid value 13174 - Kanchanjunga Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10127 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 13174 | 13174 | 13174 - Kanchanjunga Express | 2 | 0 | 1 | 1 | 1 | | | 1 | 0 | | |
Invalid value 13175 - Kanchanjanga Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10128 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 13175 | 13175 | 13175 - Kanchanjanga Express | 2 | 0 | 1 | 1 | 1 | | | 1 | 0 | | |
Invalid value 13176 - Kanchanjunga Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10129 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 13176 | 13176 | 13176 - Kanchanjunga Express | 2 | 0 | 1 | 1 | 1 | | | 1 | 0 | | |
Invalid value 13181 - KOAA SHTT EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10130 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 13181 | 13181 | 13181 - KOAA SHTT EXP | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 13182 - SHTT KOAA EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10131 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 13182 | 13182 | 13182 - SHTT KOAA EXP | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 14261 - Ekatmata Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10132 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 14261 | 14261 | 14261 - Ekatmata Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 14262 - Ekatmata Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10133 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 14262 | 14262 | 14262 - Ekatmata Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 14719 - BIKANER - BILASPUR Weekly Antyodaya Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10134 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 14719 | 14719 | 14719 - BIKANER - BILASPUR Weekly Antyodaya Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 14720 - BILASPUR - BIKANER Weekly Antyodaya Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10135 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 14720 | 14720 | 14720 - BILASPUR - BIKANER Weekly Antyodaya Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 14815 - Tbm Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10136 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 14815 | 14815 | 14815 - Tbm Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 14816 - Bgkt Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10137 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 14816 | 14816 | 14816 - Bgkt Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 15071 - Mau Ljn Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10138 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15071 | 15071 | 15071 - Mau Ljn Express | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 15072 - Ljn Mau Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10139 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15072 | 15072 | 15072 - Ljn Mau Express | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 15113 - Ljn Ci Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10140 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15113 | 15113 | 15113 - Ljn Ci Express | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 15114 - Ci Ljn Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10141 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15114 | 15114 | 15114 - Ci Ljn Express | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 15125 - Patna Jan Shatabdi in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10142 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15125 | 15125 | 15125 - Patna Jan Shatabdi | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 15126 - Jan Shatabdi Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10143 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15126 | 15126 | 15126 - Jan Shatabdi Express | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 15611 - Ghy Scl Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10144 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15611 | 15611 | 15611 - Ghy Scl Express | 2 | 0 | 1 | 1 | 1 | | | 1 | 0 | | |
Invalid value 15612 - Scl Ghy Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10145 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15612 | 15612 | 15612 - Scl Ghy Express | 2 | 0 | 1 | 1 | 1 | | | 1 | 0 | | |
Invalid value 15625 - Dghr Agtl Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10146 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15625 | 15625 | 15625 - Dghr Agtl Express | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 15626 - Agtl Dghr Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10147 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15626 | 15626 | 15626 - Agtl Dghr Express | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 15705 - Champaran Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10148 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15705 | 15705 | 15705 - Champaran Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 15706 - Champaran Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10149 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15706 | 15706 | 15706 - Champaran Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 15907 - TSK NHLN EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10150 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15907 | 15907 | 15907 - TSK NHLN EXP | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 15908 - NHLN TSK EXPRESS in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10151 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15908 | 15908 | 15908 - NHLN TSK EXPRESS | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 15911 - TSK NHLN EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10152 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15911 | 15911 | 15911 - TSK NHLN EXP | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 15912 - NHLN TSK EXPRESS in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10153 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15912 | 15912 | 15912 - NHLN TSK EXPRESS | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 15943 - Barak Bp Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10154 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15943 | 15943 | 15943 - Barak Bp Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 15944 - Barak Bp Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10155 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 15944 | 15944 | 15944 - Barak Bp Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 16191 - TAMBARAM - NAGERCOIL Antyodaya Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10156 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16191 | 16191 | 16191 - TAMBARAM - NAGERCOIL Antyodaya Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 16192 - NAGERCOIL - TAMBARAM Antyodaya Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10157 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16192 | 16192 | 16192 - NAGERCOIL - TAMBARAM Antyodaya Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 16319 - BAND HUMSAFAR in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10158 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16319 | 16319 | 16319 - BAND HUMSAFAR | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 16320 - KCVL HUMSAFAR in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10159 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16320 | 16320 | 16320 - KCVL HUMSAFAR | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 16355 - KOCHUVELI - MANGALORE Antyodaya Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10160 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16355 | 16355 | 16355 - KOCHUVELI - MANGALORE Antyodaya Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 16356 - MANGALORE - KOCHUVELI Antyodaya Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10161 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16356 | 16356 | 16356 - MANGALORE - KOCHUVELI Antyodaya Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 16511 - Kannur Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10162 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16511 | 16511 | 16511 - Kannur Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 16512 - Bangalore Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10163 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16512 | 16512 | 16512 - Bangalore Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 16513 - Karwar Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10164 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16513 | 16513 | 16513 - Karwar Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 16541 - Ypr Pvr Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10165 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16541 | 16541 | 16541 - Ypr Pvr Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 16542 - Pvr Ypr Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10166 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16542 | 16542 | 16542 - Pvr Ypr Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 16543 - Ypr Ubl Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10167 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16543 | 16543 | 16543 - Ypr Ubl Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 16544 - Ubl Ypr Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10168 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16544 | 16544 | 16544 - Ubl Ypr Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 16583 - Ypr Lur Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10169 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16583 | 16583 | 16583 - Ypr Lur Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 16585 - YPR MAQ EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10170 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16585 | 16585 | 16585 - YPR MAQ EXP | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 16586 - MAQ YPR EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10171 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16586 | 16586 | 16586 - MAQ YPR EXP | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 16795 - Trichy Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10172 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16795 | 16795 | 16795 - Trichy Express | 2 | 0 | 1 | 1 | 1 | | | 1 | 1 | | |
Invalid value 16796 - Chennai Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10173 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16796 | 16796 | 16796 - Chennai Express | 2 | 0 | 1 | 1 | 1 | | | 1 | 1 | | |
Invalid value 16851 - Rameswaram Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10174 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16851 | 16851 | 16851 - Rameswaram Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 16852 - Chennai Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10175 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16852 | 16852 | 16852 - Chennai Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 16865 - Uzhavan Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10176 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16865 | 16865 | 16865 - Uzhavan Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 16866 - Uzhavan Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10177 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 16866 | 16866 | 16866 - Uzhavan Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 17243 - Gnt Rgda Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10178 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 17243 | 17243 | 17243 - Gnt Rgda Express | 2 | 0 | 0 | 1 | 0 | | | 0 | 0 | | |
Invalid value 17244 - Vijayawada Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10179 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 17244 | 17244 | 17244 - Vijayawada Express | 2 | 0 | 0 | 1 | 0 | | | 0 | 0 | | |
Invalid value 17245 - Mtm Dmm Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10180 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 17245 | 17245 | 17245 - Mtm Dmm Express | 2 | 0 | 0 | 1 | 1 | | | 0 | 0 | | |
Invalid value 17246 - Dmm Mtm Ns Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10181 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 17246 | 17246 | 17246 - Dmm Mtm Ns Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 17247 - Ns Dmm Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10182 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 17247 | 17247 | 17247 - Ns Dmm Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 18513 - Krdl Vskp Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10183 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 18513 | 18513 | 18513 - Krdl Vskp Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 18514 - Vskp Krdl Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10184 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 18514 | 18514 | 18514 - Vskp Krdl Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 18633 - PNBE RNC EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10185 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 18633 | 18633 | 18633 - PNBE RNC EXP | 2 | 0 | 1 | 0 | 1 | | | 0 | 0 | | |
Invalid value 18634 - RNC PNBE EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10186 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 18634 | 18634 | 18634 - RNC PNBE EXP | 2 | 0 | 1 | 0 | 1 | | | 0 | 0 | | |
Invalid value 18801 - Hasdeo Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10187 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 18801 | 18801 | 18801 - Hasdeo Express | 2 | 1 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 18802 - Hasdeo Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10188 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 18802 | 18802 | 18802 - Hasdeo Express | 2 | 1 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 18803 - Hasdeo Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10189 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 18803 | 18803 | 18803 - Hasdeo Express | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 18804 - Hasdeo Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10190 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 18804 | 18804 | 18804 - Hasdeo Express | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 19003 - KHANDESH EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10191 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19003 | 19003 | 19003 - KHANDESH EXP | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 19004 - KHANDESH EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10192 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19004 | 19004 | 19004 - KHANDESH EXP | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 19043 - Bgkt Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10193 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19043 | 19043 | 19043 - Bgkt Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 19044 - Bdts Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10194 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19044 | 19044 | 19044 - Bdts Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 19315 - Lpi Indb Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10197 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19315 | 19315 | 19315 - Lpi Indb Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 19316 - Indb Lpi Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10198 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19316 | 19316 | 19316 - Indb Lpi Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 19317 - Puri Humsafar Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10199 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19317 | 19317 | 19317 - Puri Humsafar Express | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 19318 - Indb Humsafar Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10200 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19318 | 19318 | 19318 - Indb Humsafar Express | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 19319 - Indore Mahamana in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10201 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19319 | 19319 | 19319 - Indore Mahamana | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 19320 - Veraval Mahamana in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10202 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19320 | 19320 | 19320 - Veraval Mahamana | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 19333 - BKN MAHAMANA EX in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10203 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19333 | 19333 | 19333 - BKN MAHAMANA EX | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 19334 - INDB MAHAMANA EX in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10204 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19334 | 19334 | 19334 - INDB MAHAMANA EX | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 19335 - GIMB INDB EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10205 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19335 | 19335 | 19335 - GIMB INDB EXP | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 19336 - INDORE GIMB EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10206 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19336 | 19336 | 19336 - INDORE GIMB EXP | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 19337 - INDB DEE EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10207 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19337 | 19337 | 19337 - INDB DEE EXP | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 19338 - DEE INDB EXPRESS in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10208 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19338 | 19338 | 19338 - DEE INDB EXPRESS | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 19423 - Gimb Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10209 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19423 | 19423 | 19423 - Gimb Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 19424 - Ten Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10210 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19424 | 19424 | 19424 - Ten Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 19603 - Adi Sln Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10211 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19603 | 19603 | 19603 - Adi Sln Express | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 19604 - Ajmer Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10212 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19604 | 19604 | 19604 - Ajmer Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 19663 - INDB KURJ EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10213 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19663 | 19663 | 19663 - INDB KURJ EXP | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 19664 - KURJ INDB EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10214 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19664 | 19664 | 19664 - KURJ INDB EXP | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 19667 - Mys Humsafar Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10215 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19667 | 19667 | 19667 - Mys Humsafar Express | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 19669 - Ppta Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10216 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19669 | 19669 | 19669 - Ppta Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 19670 - Humsafar Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10217 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 19670 | 19670 | 19670 - Humsafar Express | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 20503 - Dbrg Ndls Rajdhani in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10218 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20503 | 20503 | 20503 - Dbrg Ndls Rajdhani | 2 | 0 | 1 | 0 | 1 | | | 0 | 1 | | |
Invalid value 20504 - Ndls Dbrg Rajdhani in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10219 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20504 | 20504 | 20504 - Ndls Dbrg Rajdhani | 2 | 0 | 1 | 0 | 1 | | | 0 | 1 | | |
Invalid value 20505 - Dbrt Rajdhani Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10220 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20505 | 20505 | 20505 - Dbrt Rajdhani Express | 2 | 0 | 1 | 0 | 1 | | | 0 | 1 | | |
Invalid value 20506 - Ndls Dbrt Rajdhani in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10221 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20506 | 20506 | 20506 - Ndls Dbrt Rajdhani | 2 | 0 | 1 | 0 | 1 | | | 0 | 1 | | |
Invalid value 20801 - Magadh Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10222 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20801 | 20801 | 20801 - Magadh Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 20802 - Magadh Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10223 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20802 | 20802 | 20802 - Magadh Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 1 | | |
Invalid value 20817 - Bbs Rajdhani Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10224 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20817 | 20817 | 20817 - Bbs Rajdhani Express | 2 | 0 | 1 | 0 | 1 | | | 0 | 1 | | |
Invalid value 20818 - Bhubaneswar Rajdhani in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10225 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20818 | 20818 | 20818 - Bhubaneswar Rajdhani | 2 | 0 | 1 | 0 | 1 | | | 0 | 1 | | |
Invalid value 20821 - Src Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10226 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20821 | 20821 | 20821 - Src Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 20822 - Humsafar Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10227 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20822 | 20822 | 20822 - Humsafar Express | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 20827 - Jbp Src Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10228 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20827 | 20827 | 20827 - Jbp Src Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 20828 - Humsafar Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10229 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20828 | 20828 | 20828 - Humsafar Express | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 20839 - Rnc Ndls Raj Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10230 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20839 | 20839 | 20839 - Rnc Ndls Raj Express | 2 | 0 | 1 | 0 | 1 | | | 0 | 1 | | |
Invalid value 20840 - Ndls Rnc Raj Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10231 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 20840 | 20840 | 20840 - Ndls Rnc Raj Express | 2 | 0 | 1 | 0 | 1 | | | 0 | 1 | | |
Invalid value 22155 - Sur Mrj Sfast in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10232 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22155 | 22155 | 22155 - Sur Mrj Sfast | 2 | 0 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 22156 - Mrj Sur Sfast in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10233 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22156 | 22156 | 22156 - Mrj Sur Sfast | 2 | 0 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 22169 - Hbj Src Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10234 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22169 | 22169 | 22169 - Hbj Src Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 22170 - Src Hbj Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10235 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22170 | 22170 | 22170 - Src Hbj Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 22171 - Pune Hbj Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10236 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22171 | 22171 | 22171 - Pune Hbj Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 22172 - Hbj Pune Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10237 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22172 | 22172 | 22172 - Hbj Pune Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 22221 - NZM RAJDHANI EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10238 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22221 | 22221 | 22221 - NZM RAJDHANI EXP | 2 | 0 | 1 | 0 | 1 | | | 0 | 1 | | |
Invalid value 22222 - CSMT RAJDHANI in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10239 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22222 | 22222 | 22222 - CSMT RAJDHANI | 2 | 0 | 1 | 0 | 1 | | | 0 | 1 | | |
Invalid value 22317 - Humsafar Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10240 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22317 | 22317 | 22317 - Humsafar Express | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 22318 - Humsafar Sf in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10241 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22318 | 22318 | 22318 - Humsafar Sf | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 22435 - VANDE BHARAT EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10242 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22435 | 22435 | 22435 - VANDE BHARAT EXP | 2 | 1 | 0 | 0 | 0 | | | 0 | 1 | | |
Invalid value 22436 - VANDE BHARAT EXP in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10243 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22436 | 22436 | 22436 - VANDE BHARAT EXP | 2 | 1 | 0 | 0 | 0 | | | 0 | 1 | | |
Invalid value 22437 - Anvt Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10244 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22437 | 22437 | 22437 - Anvt Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 22438 - Ald Humsafar in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10245 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22438 | 22438 | 22438 - Ald Humsafar | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 22547 - Gwl Adi Sup in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10246 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22547 | 22547 | 22547 - Gwl Adi Sup | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 22548 - Adi Gwl Sf Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10247 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22548 | 22548 | 22548 - Adi Gwl Sf Express | 2 | 0 | 1 | 1 | 1 | | | 0 | 0 | | |
Invalid value 22551 - DARBHANGA - JALANDHAR CITY Antyodaya Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10248 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22551 | 22551 | 22551 - DARBHANGA - JALANDHAR CITY Antyodaya Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 22552 - JALANDHAR CITY - DARBHANGA Antyodaya Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10249 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22552 | 22552 | 22552 - JALANDHAR CITY - DARBHANGA Antyodaya Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 22665 - Sbc Cbe Uday Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10250 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22665 | 22665 | 22665 - Sbc Cbe Uday Express | 2 | 1 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 22666 - Cbe Sbc Uday Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10251 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22666 | 22666 | 22666 - Cbe Sbc Uday Express | 2 | 1 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 22842 - CHENNAI CENTRAL - SANTRAGACHI Antyodaya Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10252 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22842 | 22842 | 22842 - CHENNAI CENTRAL - SANTRAGACHI Antyodaya Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 22895 - DURG - FIROZPUR CANTT Antyodaya Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10253 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22895 | 22895 | 22895 - DURG - FIROZPUR CANTT Antyodaya Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 22896 - FIROZPUR CANTT - DURG Antyodaya Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10254 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22896 | 22896 | 22896 - FIROZPUR CANTT - DURG Antyodaya Express | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 22986 - Raj Hamsafar Express in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10255 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22986 | 22986 | 22986 - Raj Hamsafar Express | 2 | 0 | 0 | 0 | 1 | | | 0 | 0 | | |
Invalid value 22987 - Aii Af Superfast in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10256 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22987 | 22987 | 22987 - Aii Af Superfast | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 22988 - Af Aii Superfast in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10257 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 22988 | 22988 | 22988 - Af Aii Superfast | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 31419 - SEALDAH - NAIHATI Local in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10258 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 31419 | 31419 | 31419 - SEALDAH - NAIHATI Local | 2 | | | | | | | | | | |
Invalid value 33684 - GOBARDANGA - SEALDAH Local in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10259 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 33684 | 33684 | 33684 - GOBARDANGA - SEALDAH Local | 2 | | | | | | | | | | |
Invalid value 37051 - HOWRAH - SEORAPHULI Local in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10260 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 37051 | 37051 | 37051 - HOWRAH - SEORAPHULI Local | 2 | | | | | | | | | | |
Invalid value 37052 - SEORAPHULI - HOWRAH Local in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10261 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 37052 | 37052 | 37052 - SEORAPHULI - HOWRAH Local | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 37059 - HOWRAH - SEORAPHULI Local in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10262 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 37059 | 37059 | 37059 - HOWRAH - SEORAPHULI Local | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 51709 - NAINPUR - CHIRAIDONGRI Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10263 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 51709 | 51709 | 51709 - NAINPUR - CHIRAIDONGRI Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 51711 - NAINPUR - CHIRAIDONGRI Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10264 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 51711 | 51711 | 51711 - NAINPUR - CHIRAIDONGRI Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 51712 - CHIRAIDONGRI - NAINPUR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10265 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 51712 | 51712 | 51712 - CHIRAIDONGRI - NAINPUR Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 51713 - NAINPUR - CHIRAIDONGRI Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10266 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 51713 | 51713 | 51713 - NAINPUR - CHIRAIDONGRI Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 51714 - CHIRAIDONGRI - NAINPUR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10267 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 51714 | 51714 | 51714 - CHIRAIDONGRI - NAINPUR Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 52249 - BAHRAICH - MAILANI Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10268 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 52249 | 52249 | 52249 - BAHRAICH - MAILANI Passenger | 2 | | | | | | | | | | |
Invalid value 52250 - MAILANI - BAHRAICH Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10269 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 52250 | 52250 | 52250 - MAILANI - BAHRAICH Passenger | 2 | | | | | | | | | | |
Invalid value 52261 - BAHRAICH - NEPALGANJ ROAD Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10270 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 52261 | 52261 | 52261 - BAHRAICH - NEPALGANJ ROAD Passenger | 2 | | | | | | | | | | |
Invalid value 52262 - NEPALGANJ ROAD - BAHRAICH Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10271 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 52262 | 52262 | 52262 - NEPALGANJ ROAD - BAHRAICH Passenger | 2 | | | | | | | | | | |
Invalid value 52459 - KLK SML SPECIAL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10272 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 52459 | 52459 | 52459 - KLK SML SPECIAL | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 52460 - SML KLK SPECIAL in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10273 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 52460 | 52460 | 52460 - SML KLK SPECIAL | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 52475 - PTK BJPL EXPRESS in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10274 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 52475 | 52475 | 52475 - PTK BJPL EXPRESS | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 52476 - BJPL PTK EXPRESS in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10275 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 52476 | 52476 | 52476 - BJPL PTK EXPRESS | 2 | 1 | 0 | 0 | 0 | | | 1 | 0 | | |
Invalid value 52965 - INDORE - MHOW Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10276 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 52965 | 52965 | 52965 - INDORE - MHOW Passenger | 2 | | | | | | | | | | |
Invalid value 52966 - MHOW-UJJN MG FAST PASS in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10277 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 52966 | 52966 | 52966 - MHOW-UJJN MG FAST PASS | 2 | | | | | | | | | | |
Invalid value 53081 - RAMPUR HAT - JASIDIH Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10278 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 53081 | 53081 | 53081 - RAMPUR HAT - JASIDIH Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 53082 - JASIDIH - RAMPURHAT Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10279 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 53082 | 53082 | 53082 - JASIDIH - RAMPURHAT Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 53375 - BARKA KANA - SIDHWAR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10280 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 53375 | 53375 | 53375 - BARKA KANA - SIDHWAR Passenger | 2 | | | | | | | | | | |
Invalid value 53376 - SIDHWAR - BARKA KANA Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10281 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 53376 | 53376 | 53376 - SIDHWAR - BARKA KANA Passenger | 2 | | | | | | | | | | |
Invalid value 53451 - DUMKA - HANSDIHA Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10282 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 53451 | 53451 | 53451 - DUMKA - HANSDIHA Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 53452 - HANSDIHA - DUMKA Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10283 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 53452 | 53452 | 53452 - HANSDIHA - DUMKA Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 54610 - AMRITSAR - JALANDHAR CITY Passenger Special in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10284 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 54610 | 54610 | 54610 - AMRITSAR - JALANDHAR CITY Passenger Special | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 54767 - SGNR TKJ PASS in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10285 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 54767 | 54767 | 54767 - SGNR TKJ PASS | 2 | 0 | 0 | 1 | 0 | | | 0 | 0 | | |
Invalid value 54768 - TKJ SGNR PASS in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10286 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 54768 | 54768 | 54768 - TKJ SGNR PASS | 2 | 0 | 0 | 1 | 0 | | | 0 | 0 | | |
Invalid value 54769 - TILAK BRIDGE - ROHTAK Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10287 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 54769 | 54769 | 54769 - TILAK BRIDGE - ROHTAK Passenger | 2 | | | | | | | | | | |
Invalid value 54770 - ROHTAK - TILAK BRIDGE Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10288 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 54770 | 54770 | 54770 - ROHTAK - TILAK BRIDGE Passenger | 2 | | | | | | | | | | |
Invalid value 55061 - SITAPUR - LUCKNOW Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10289 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 55061 | 55061 | 55061 - SITAPUR - LUCKNOW Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 55062 - LUCKNOW - SITAPUR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10290 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 55062 | 55062 | 55062 - LUCKNOW - SITAPUR Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 55063 - SITAPUR - DALIGANJ Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10291 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 55063 | 55063 | 55063 - SITAPUR - DALIGANJ Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 55064 - DALIGANJ - SITAPUR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10292 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 55064 | 55064 | 55064 - DALIGANJ - SITAPUR Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 55065 - SITAPUR - LUCKNOW Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10293 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 55065 | 55065 | 55065 - SITAPUR - LUCKNOW Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 55066 - LUCKNOW - SITAPUR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10294 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 55066 | 55066 | 55066 - LUCKNOW - SITAPUR Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 55377 - PILIBHIT - TANAKPUR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10295 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 55377 | 55377 | 55377 - PILIBHIT - TANAKPUR Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 55585 - RAXAUL - NARKATIAGANJ Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10296 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 55585 | 55585 | 55585 - RAXAUL - NARKATIAGANJ Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 55586 - NARKATIAGANJ - RAXAUL Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10297 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 55586 | 55586 | 55586 - NARKATIAGANJ - RAXAUL Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 55587 - RAXAUL - NARKATIAGANJ Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10298 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 55587 | 55587 | 55587 - RAXAUL - NARKATIAGANJ Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 55588 - NARKATIAGANJ - RAXAUL Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10299 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 55588 | 55588 | 55588 - NARKATIAGANJ - RAXAUL Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 56927 - HUBLI - CHIKKABENAKAL Fast Passenger (UnReserved) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10300 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 56927 | 56927 | 56927 - HUBLI - CHIKKABENAKAL Fast Passenger (UnReserved) | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 56928 - CHIKKABENAKAL - HUBLI Fast Passenger (UnReserved) in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10301 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 56928 | 56928 | 56928 - CHIKKABENAKAL - HUBLI Fast Passenger (UnReserved) | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 58305 - BALANGIR - BICHHUPALI Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10302 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 58305 | 58305 | 58305 - BALANGIR - BICHHUPALI Passenger | 2 | | | | | | | | | | |
Invalid value 58306 - BICHHUPALI - BALANGIR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10303 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 58306 | 58306 | 58306 - BICHHUPALI - BALANGIR Passenger | 2 | | | | | | | | | | |
Invalid value 58307 - BALANGIR - BICHHUPALI Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10304 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 58307 | 58307 | 58307 - BALANGIR - BICHHUPALI Passenger | 2 | | | | | | | | | | |
Invalid value 58308 - BICHHUPALI - BALANGIR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10305 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 58308 | 58308 | 58308 - BICHHUPALI - BALANGIR Passenger | 2 | | | | | | | | | | |
Invalid value 61001 - BOISAR - VASAI ROAD MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10306 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61001 | 61001 | 61001 - BOISAR - VASAI ROAD MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61002 - DOMVIVALI - BOISAR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10307 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61002 | 61002 | 61002 - DOMVIVALI - BOISAR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61003 - VASAI ROAD - DIVA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10308 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61003 | 61003 | 61003 - VASAI ROAD - DIVA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61004 - DIVA - VASAI ROAD MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10309 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61004 | 61004 | 61004 - DIVA - VASAI ROAD MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61005 - VASAI ROAD - DIVA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10310 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61005 | 61005 | 61005 - VASAI ROAD - DIVA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61006 - DIVA - VASAI ROAD MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10311 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61006 | 61006 | 61006 - DIVA - VASAI ROAD MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61007 - VASAI ROAD - DIVA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10312 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61007 | 61007 | 61007 - VASAI ROAD - DIVA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61008 - DIVA - VASAI ROAD MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10313 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61008 | 61008 | 61008 - DIVA - VASAI ROAD MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61009 - VASAI ROAD - DIVA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10314 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61009 | 61009 | 61009 - VASAI ROAD - DIVA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61010 - ROHA - DIVA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10315 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61010 | 61010 | 61010 - ROHA - DIVA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61011 - DIVA - ROHA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10316 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61011 | 61011 | 61011 - DIVA - ROHA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61012 - ROHA - DIVA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10317 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61012 | 61012 | 61012 - ROHA - DIVA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61013 - DIVA - ROHA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10318 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61013 | 61013 | 61013 - DIVA - ROHA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61015 - DIVA - PEN MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10319 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61015 | 61015 | 61015 - DIVA - PEN MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61016 - PEN - DIVA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10320 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61016 | 61016 | 61016 - PEN - DIVA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61017 - DIVA - PANVEL MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10321 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61017 | 61017 | 61017 - DIVA - PANVEL MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61018 - PANVEL - DIVA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10322 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61018 | 61018 | 61018 - PANVEL - DIVA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61019 - DIVA - PEN MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10323 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61019 | 61019 | 61019 - DIVA - PEN MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61020 - PEN - DIVA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10324 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61020 | 61020 | 61020 - PEN - DIVA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61021 - VASAI ROAD - DIVA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10325 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61021 | 61021 | 61021 - VASAI ROAD - DIVA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61022 - DIVA - VASAI ROAD MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10326 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61022 | 61022 | 61022 - DIVA - VASAI ROAD MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61633 - BHOPAL - BINA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10327 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61633 | 61633 | 61633 - BHOPAL - BINA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 61634 - BINA - BHOPAL MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10328 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 61634 | 61634 | 61634 - BINA - BHOPAL MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63007 - KATWA - RAMPUR HAT MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10329 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63007 | 63007 | 63007 - KATWA - RAMPUR HAT MEMU | 2 | | | | | | | | | | |
Invalid value 63010 - AZIMGANJ - KATWA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10330 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63010 | 63010 | 63010 - AZIMGANJ - KATWA MEMU | 2 | | | | | | | | | | |
Invalid value 63026 - RAMPUR HAT - AZIMGANJ MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10331 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63026 | 63026 | 63026 - RAMPUR HAT - AZIMGANJ MEMU | 2 | | | | | | | | | | |
Invalid value 63201 - BARAUNI - SAMASTIPUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10332 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63201 | 63201 | 63201 - BARAUNI - SAMASTIPUR MEMU | 2 | | | | | | | | | | |
Invalid value 63202 - SAMASTIPUR - BARAUNI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10333 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63202 | 63202 | 63202 - SAMASTIPUR - BARAUNI MEMU | 2 | | | | | | | | | | |
Invalid value 63215 - SAMASTIPUR - MUZAFFARPUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10334 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63215 | 63215 | 63215 - SAMASTIPUR - MUZAFFARPUR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63216 - MUZAFFARPUR - SAMASTIPUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10335 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63216 | 63216 | 63216 - MUZAFFARPUR - SAMASTIPUR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63229 - BUXAR - MANDUADIH MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10336 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63229 | 63229 | 63229 - BUXAR - MANDUADIH MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63230 - MANDUADIH - BUXAR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10337 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63230 | 63230 | 63230 - MANDUADIH - BUXAR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63268 - PATLIPUTRA - MUZAFFARPUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10338 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63268 | 63268 | 63268 - PATLIPUTRA - MUZAFFARPUR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63297 - VARANASI CITY - BALLIA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10339 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63297 | 63297 | 63297 - VARANASI CITY - BALLIA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63298 - BALLIA - VARANASI CITY MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10340 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63298 | 63298 | 63298 - BALLIA - VARANASI CITY MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63301 - KATIHAR - BARAUNI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10341 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63301 | 63301 | 63301 - KATIHAR - BARAUNI MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63302 - BARAUNI - KATIHAR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10342 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63302 | 63302 | 63302 - BARAUNI - KATIHAR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63303 - KATIHAR - SAMASTIPUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10343 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63303 | 63303 | 63303 - KATIHAR - SAMASTIPUR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63304 - SAMASTIPUR - KATIHAR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10344 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63304 | 63304 | 63304 - SAMASTIPUR - KATIHAR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63315 - JHAJHA - GAYA MEMU? in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10345 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63315 | 63315 | 63315 - JHAJHA - GAYA MEMU? | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63316 - GAYA - JHAJHA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10346 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63316 | 63316 | 63316 - GAYA - JHAJHA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63317 - KIUL - GAYA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10347 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63317 | 63317 | 63317 - KIUL - GAYA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63318 - GAYA - KIUL MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10348 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63318 | 63318 | 63318 - GAYA - KIUL MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63319 - KIUL - GAYA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10349 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63319 | 63319 | 63319 - KIUL - GAYA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63320 - GAYA - KIUL MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10350 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63320 | 63320 | 63320 - GAYA - KIUL MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63325 - ISLAMPUR - PATNA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10351 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63325 | 63325 | 63325 - ISLAMPUR - PATNA MEMU | 2 | | | | | | | | | | |
Invalid value 63326 - PATNA - ISLAMPUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10352 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63326 | 63326 | 63326 - PATNA - ISLAMPUR MEMU | 2 | | | | | | | | | | |
Invalid value 63327 - ISLAMPUR - PATNA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10353 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63327 | 63327 | 63327 - ISLAMPUR - PATNA MEMU | 2 | | | | | | | | | | |
Invalid value 63328 - PATNA - ISLAMPUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10354 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63328 | 63328 | 63328 - PATNA - ISLAMPUR MEMU | 2 | | | | | | | | | | |
Invalid value 63329 - RAJGIR - FATUHA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10355 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63329 | 63329 | 63329 - RAJGIR - FATUHA MEMU | 2 | | | | | | | | | | |
Invalid value 63330 - FATUHA - RAJGIR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10356 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63330 | 63330 | 63330 - FATUHA - RAJGIR MEMU | 2 | | | | | | | | | | |
Invalid value 63331 - ISLAMPUR - FATUHA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10357 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63331 | 63331 | 63331 - ISLAMPUR - FATUHA MEMU | 2 | | | | | | | | | | |
Invalid value 63332 - FATUHA - ISLAMPUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10358 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63332 | 63332 | 63332 - FATUHA - ISLAMPUR MEMU | 2 | | | | | | | | | | |
Invalid value 63503 - BARDDHAMAN - HATIA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10359 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63503 | 63503 | 63503 - BARDDHAMAN - HATIA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 63504 - HATIA - BARDDHAMAN MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10360 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 63504 | 63504 | 63504 - HATIA - BARDDHAMAN MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 66545 - MARIKUPPAM - KSR BENGALURU MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10361 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 66545 | 66545 | 66545 - MARIKUPPAM - KSR BENGALURU MEMU | 2 | | | | | | | | | | |
Invalid value 66546 - KSR BENGALURU - MARIKUPPAM MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10362 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 66546 | 66546 | 66546 - KSR BENGALURU - MARIKUPPAM MEMU | 2 | | | | | | | | | | |
Invalid value 66547 - BANGARAPET - MARIKUPPAM MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10363 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 66547 | 66547 | 66547 - BANGARAPET - MARIKUPPAM MEMU | 2 | | | | | | | | | | |
Invalid value 66548 - MARIKUPPAM - BANGARAPET MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10364 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 66548 | 66548 | 66548 - MARIKUPPAM - BANGARAPET MEMU | 2 | | | | | | | | | | |
Invalid value 67221 - VIJAYAWADA - TENALI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10365 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67221 | 67221 | 67221 - VIJAYAWADA - TENALI MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67222 - TENALI - GUNTUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10366 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67222 | 67222 | 67222 - TENALI - GUNTUR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67223 - GUNTUR - VIJAYAWADA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10367 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67223 | 67223 | 67223 - GUNTUR - VIJAYAWADA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67224 - VIJAYAWADA - GUNTUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10368 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67224 | 67224 | 67224 - VIJAYAWADA - GUNTUR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67225 - GUNTUR - TENALI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10369 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67225 | 67225 | 67225 - GUNTUR - TENALI MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67226 - TENALI - VIJAYAWADA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10370 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67226 | 67226 | 67226 - TENALI - VIJAYAWADA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67227 - VIJAYAWADA - TENALI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10371 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67227 | 67227 | 67227 - VIJAYAWADA - TENALI MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67228 - Tenali Guntur Memu in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10372 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67228 | 67228 | 67228 - Tenali Guntur Memu | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67229 - GUNTUR - VIJAYAWADA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10373 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67229 | 67229 | 67229 - GUNTUR - VIJAYAWADA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67231 - TIRUPATI MAIN - GUNTUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10374 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67231 | 67231 | 67231 - TIRUPATI MAIN - GUNTUR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67232 - GUNTUR - TIRUPATI MAIN MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10375 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67232 | 67232 | 67232 - GUNTUR - TIRUPATI MAIN MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67233 - BITRAGUNTA - VIJAYAWADA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10376 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67233 | 67233 | 67233 - BITRAGUNTA - VIJAYAWADA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67234 - VIJAYAWADA - BITRAGUNTA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10377 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67234 | 67234 | 67234 - VIJAYAWADA - BITRAGUNTA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67237 - TIRUPATI MAIN - GUDUR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10378 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67237 | 67237 | 67237 - TIRUPATI MAIN - GUDUR Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67238 - GUDUR - TIRUPATI MAIN Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10379 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67238 | 67238 | 67238 - GUDUR - TIRUPATI MAIN Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67239 - RENIGUNTA - GUDUR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10380 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67239 | 67239 | 67239 - RENIGUNTA - GUDUR Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67240 - GUDUR - RENIGUNTA Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10381 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67240 | 67240 | 67240 - GUDUR - RENIGUNTA Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67241 - VIJAYAWADA - KAKINADA PORT Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10382 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67241 | 67241 | 67241 - VIJAYAWADA - KAKINADA PORT Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67243 - KAKINADA PORT - VISAKHAPATNAM MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10383 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67243 | 67243 | 67243 - KAKINADA PORT - VISAKHAPATNAM MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67244 - VISAKHAPATNAM - KAKINADA PORT MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10384 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67244 | 67244 | 67244 - VISAKHAPATNAM - KAKINADA PORT MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 67245 - VIJAYAWADA - BHADRACHALAM ROAD MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10385 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 67245 | 67245 | 67245 - VIJAYAWADA - BHADRACHALAM ROAD MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68025 - CHAKRADHARPUR - ROURKELA Saranda MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10386 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68025 | 68025 | 68025 - CHAKRADHARPUR - ROURKELA Saranda MEMU | 2 | | | | | | | | | | |
Invalid value 68026 - ROURKELA - CHAKRADHARPUR Saranda DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10387 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68026 | 68026 | 68026 - ROURKELA - CHAKRADHARPUR Saranda DEMU | 2 | | | | | | | | | | |
Invalid value 68028 - SAMBALPUR - ROURKELA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10388 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68028 | 68028 | 68028 - SAMBALPUR - ROURKELA MEMU | 2 | | | | | | | | | | |
Invalid value 68029 - ROURKELA - JHARSUGUDA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10389 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68029 | 68029 | 68029 - ROURKELA - JHARSUGUDA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68030 - JHARSUGUDA - ROURKELA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10390 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68030 | 68030 | 68030 - JHARSUGUDA - ROURKELA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68032 - SAMBALPUR - JHARSUGUDA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10391 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68032 | 68032 | 68032 - SAMBALPUR - JHARSUGUDA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68033 - JHARSUGUDA - SAMBALPUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10392 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68033 | 68033 | 68033 - JHARSUGUDA - SAMBALPUR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68034 - SAMBALPUR - JHARSUGUDA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10393 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68034 | 68034 | 68034 - SAMBALPUR - JHARSUGUDA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68035 - RANCHI - LOHARDAGA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10394 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68035 | 68035 | 68035 - RANCHI - LOHARDAGA MEMU | 2 | | | | | | | | | | |
Invalid value 68036 - LOHARDAGA - RANCHI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10395 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68036 | 68036 | 68036 - LOHARDAGA - RANCHI MEMU | 2 | | | | | | | | | | |
Invalid value 68037 - RANCHI - TORI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10396 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68037 | 68037 | 68037 - RANCHI - TORI MEMU | 2 | | | | | | | | | | |
Invalid value 68038 - TORI - RANCHI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10397 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68038 | 68038 | 68038 - TORI - RANCHI MEMU | 2 | | | | | | | | | | |
Invalid value 68039 - RANCHI - LOHARDAGA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10398 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68039 | 68039 | 68039 - RANCHI - LOHARDAGA MEMU | 2 | | | | | | | | | | |
Invalid value 68040 - LOHARDAGA - RANCHI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10399 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68040 | 68040 | 68040 - LOHARDAGA - RANCHI MEMU | 2 | | | | | | | | | | |
Invalid value 68041 - RANCHI - LOHARDAGA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10400 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68041 | 68041 | 68041 - RANCHI - LOHARDAGA MEMU | 2 | | | | | | | | | | |
Invalid value 68042 - LOHARDAGA - RANCHI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10401 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68042 | 68042 | 68042 - LOHARDAGA - RANCHI MEMU | 2 | | | | | | | | | | |
Invalid value 68049 - KHARAGPUR - BHADRAKH MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10402 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68049 | 68049 | 68049 - KHARAGPUR - BHADRAKH MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68050 - BHADRAKH - KHARAGPUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10403 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68050 | 68050 | 68050 - BHADRAKH - KHARAGPUR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68051 - BALASORE - BHADRAKH MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10404 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68051 | 68051 | 68051 - BALASORE - BHADRAKH MEMU | 2 | | | | | | | | | | |
Invalid value 68052 - BHADRAKH - BALASORE MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10405 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68052 | 68052 | 68052 - BHADRAKH - BALASORE MEMU | 2 | | | | | | | | | | |
Invalid value 68085 - KHARAGPUR - RANCHI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10406 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68085 | 68085 | 68085 - KHARAGPUR - RANCHI MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68086 - RANCHI - KHARAGPUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10407 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68086 | 68086 | 68086 - RANCHI - KHARAGPUR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68413 - TALCHER - PURI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10408 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68413 | 68413 | 68413 - TALCHER - PURI MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68414 - PURI - TALCHER MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10409 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68414 | 68414 | 68414 - PURI - TALCHER MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68421 - ANGUL - PURI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10410 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68421 | 68421 | 68421 - ANGUL - PURI MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68422 - PURI - ANGUL MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10411 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68422 | 68422 | 68422 - PURI - ANGUL MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68433 - CUTTACK - BRAHMAPUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10412 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68433 | 68433 | 68433 - CUTTACK - BRAHMAPUR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68434 - BRAHMAPUR - CUTTACK MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10413 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68434 | 68434 | 68434 - BRAHMAPUR - CUTTACK MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 68435 - CUTTACK - PARADEEP MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10414 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68435 | 68435 | 68435 - CUTTACK - PARADEEP MEMU | 2 | | | | | | | | | | |
Invalid value 68436 - PARADEEP - CUTTACK MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10415 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68436 | 68436 | 68436 - PARADEEP - CUTTACK MEMU | 2 | | | | | | | | | | |
Invalid value 68751 - RAMTEK - ITWARI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10416 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68751 | 68751 | 68751 - RAMTEK - ITWARI MEMU | 2 | | | | | | | | | | |
Invalid value 68752 - ITWARI - RAMTEK MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10417 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68752 | 68752 | 68752 - ITWARI - RAMTEK MEMU | 2 | | | | | | | | | | |
Invalid value 68753 - RAMTEK - ITWARI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10418 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68753 | 68753 | 68753 - RAMTEK - ITWARI MEMU | 2 | | | | | | | | | | |
Invalid value 68754 - ITWARI - RAMTEK MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10419 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68754 | 68754 | 68754 - ITWARI - RAMTEK MEMU | 2 | | | | | | | | | | |
Invalid value 68755 - RAMTEK - NAGPUR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10420 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68755 | 68755 | 68755 - RAMTEK - NAGPUR MEMU | 2 | | | | | | | | | | |
Invalid value 68756 - NAGPUR - RAMTEK MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10421 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 68756 | 68756 | 68756 - NAGPUR - RAMTEK MEMU | 2 | | | | | | | | | | |
Invalid value 69155 - RATLAM - MATHURA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10422 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 69155 | 69155 | 69155 - RATLAM - MATHURA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 69156 - MATHURA - RATLAM Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10423 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 69156 | 69156 | 69156 - MATHURA - RATLAM Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 69157 - BAYANA - YAMUNA BDG AGRA Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10424 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 69157 | 69157 | 69157 - BAYANA - YAMUNA BDG AGRA Passenger | 2 | | | | | | | | | | |
Invalid value 69160 - MATHURA - BAYANA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10425 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 69160 | 69160 | 69160 - MATHURA - BAYANA MEMU | 2 | | | | | | | | | | |
Invalid value 69175 - BHARUCH - ANAND MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10426 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 69175 | 69175 | 69175 - BHARUCH - ANAND MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 69176 - ANAND - BHARUCH MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10427 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 69176 | 69176 | 69176 - ANAND - BHARUCH MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 69177 - UDHNA - NANDURBAR MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10428 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 69177 | 69177 | 69177 - UDHNA - NANDURBAR MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 69178 - NANDURBAR - UDHNA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10429 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 69178 | 69178 | 69178 - NANDURBAR - UDHNA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 69179 - UDHNA - PALDHI MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10430 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 69179 | 69179 | 69179 - UDHNA - PALDHI MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 69180 - PALDHI - UDHNA MEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10431 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 69180 | 69180 | 69180 - PALDHI - UDHNA MEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 71302 - GUNTAKAL - KALABURAGI DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10432 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 71302 | 71302 | 71302 - GUNTAKAL - KALABURAGI DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 71304 - GADAG - SOLAPUR Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10433 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 71304 | 71304 | 71304 - GADAG - SOLAPUR Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 71305 - KALABURAGI - WADI DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10434 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 71305 | 71305 | 71305 - KALABURAGI - WADI DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 71306 - WADI - SOLAPUR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10435 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 71306 | 71306 | 71306 - WADI - SOLAPUR DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 73041 - KATWA - AHMADPUR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10436 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 73041 | 73041 | 73041 - KATWA - AHMADPUR DEMU | 2 | | | | | | | | | | |
Invalid value 73042 - AHMADPUR - KATWA DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10437 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 73042 | 73042 | 73042 - AHMADPUR - KATWA DEMU | 2 | | | | | | | | | | |
Invalid value 74859 - SIKAR - CHURU DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10438 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 74859 | 74859 | 74859 - SIKAR - CHURU DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 74860 - Churu - Sikar Demu in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10439 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 74860 | 74860 | 74860 - Churu - Sikar Demu | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 74861 - SIKAR - CHURU DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10440 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 74861 | 74861 | 74861 - SIKAR - CHURU DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 74862 - CHURU - SIKAR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10441 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 74862 | 74862 | 74862 - CHURU - SIKAR DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75017 - GONDA - BAHRAICH DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10442 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75017 | 75017 | 75017 - GONDA - BAHRAICH DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75018 - BAHRAICH - GONDA DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10443 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75018 | 75018 | 75018 - BAHRAICH - GONDA DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75019 - GONDA - BAHRAICH DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10444 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75019 | 75019 | 75019 - GONDA - BAHRAICH DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75020 - BAHRAICH - GONDA DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10445 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75020 | 75020 | 75020 - BAHRAICH - GONDA DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75021 - GONDA - BAHRAICH DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10446 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75021 | 75021 | 75021 - GONDA - BAHRAICH DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75022 - BAHRAICH - GONDA DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10447 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75022 | 75022 | 75022 - BAHRAICH - GONDA DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75257 - MUZAFFARPUR - NARKATIAGANJ DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10448 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75257 | 75257 | 75257 - MUZAFFARPUR - NARKATIAGANJ DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75258 - NARKATIAGANJ - MUZAFFARPUR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10449 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75258 | 75258 | 75258 - NARKATIAGANJ - MUZAFFARPUR DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75259 - MUZAFFARPUR - NARKATIAGANJ DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10450 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75259 | 75259 | 75259 - MUZAFFARPUR - NARKATIAGANJ DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75260 - NARKATIAGANJ - MUZAFFARPUR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10451 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75260 | 75260 | 75260 - NARKATIAGANJ - MUZAFFARPUR DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75261 - MUZAFFARPUR - NARKATIAGANJ DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10452 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75261 | 75261 | 75261 - MUZAFFARPUR - NARKATIAGANJ DEMU | 2 | | | | | | | | | | |
Invalid value 75262 - NARKATIAGANJ - MUZAFFARPUR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10453 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75262 | 75262 | 75262 - NARKATIAGANJ - MUZAFFARPUR DEMU | 2 | | | | | | | | | | |
Invalid value 75263 - MUZAFFARPUR - RAXAUL DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10454 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75263 | 75263 | 75263 - MUZAFFARPUR - RAXAUL DEMU | 2 | | | | | | | | | | |
Invalid value 75264 - RAXAUL - MUZAFFARPUR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10455 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75264 | 75264 | 75264 - RAXAUL - MUZAFFARPUR DEMU | 2 | | | | | | | | | | |
Invalid value 75265 - MUZAFFARPUR - RAXAUL DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10456 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75265 | 75265 | 75265 - MUZAFFARPUR - RAXAUL DEMU | 2 | | | | | | | | | | |
Invalid value 75266 - RAXAUL - MUZAFFARPUR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10457 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75266 | 75266 | 75266 - RAXAUL - MUZAFFARPUR DEMU | 2 | | | | | | | | | | |
Invalid value 75301 - BAREILLY CITY - LAL KUAN DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10458 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75301 | 75301 | 75301 - BAREILLY CITY - LAL KUAN DEMU | 2 | | | | | | | | | | |
Invalid value 75302 - LAL KUAN - BAREILLY CITY DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10459 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75302 | 75302 | 75302 - LAL KUAN - BAREILLY CITY DEMU | 2 | | | | | | | | | | |
Invalid value 75303 - LAL KUAN - KASHIPUR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10460 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75303 | 75303 | 75303 - LAL KUAN - KASHIPUR DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75304 - KASHIPUR - LAL KUAN DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10461 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75304 | 75304 | 75304 - KASHIPUR - LAL KUAN DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75305 - BAREILLY CITY - PILIBHIT DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10462 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75305 | 75305 | 75305 - BAREILLY CITY - PILIBHIT DEMU | 2 | | | | | | | | | | |
Invalid value 75306 - PILIBHIT - BAREILLY CITY DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10463 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75306 | 75306 | 75306 - PILIBHIT - BAREILLY CITY DEMU | 2 | | | | | | | | | | |
Invalid value 75741 - SILIGURI - DHUBRI DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10464 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75741 | 75741 | 75741 - SILIGURI - DHUBRI DEMU | 2 | | | | | | | | | | |
Invalid value 75742 - DHUBRI - SILIGURI DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10465 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75742 | 75742 | 75742 - DHUBRI - SILIGURI DEMU | 2 | | | | | | | | | | |
Invalid value 75751 - KATIHAR - JOGBANI Passenger in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10466 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75751 | 75751 | 75751 - KATIHAR - JOGBANI Passenger | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75753 - KATIHAR - JOGBANI DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10467 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75753 | 75753 | 75753 - KATIHAR - JOGBANI DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75754 - JOGBANI - KATIHAR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10468 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75754 | 75754 | 75754 - JOGBANI - KATIHAR DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75755 - KATIHAR - JOGBANI DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10469 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75755 | 75755 | 75755 - KATIHAR - JOGBANI DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75756 - JOGBANI - KATIHAR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10470 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75756 | 75756 | 75756 - JOGBANI - KATIHAR DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75758 - JOGBANI - KATIHAR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10471 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75758 | 75758 | 75758 - JOGBANI - KATIHAR DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75759 - KATIHAR - JOGBANI DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10472 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75759 | 75759 | 75759 - KATIHAR - JOGBANI DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 75762 - JOGBANI - KATIHAR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10473 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 75762 | 75762 | 75762 - JOGBANI - KATIHAR DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 78829 - GONDIA - SAMNAPUR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10474 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 78829 | 78829 | 78829 - GONDIA - SAMNAPUR DEMU | 2 | | | | | | | | | | |
Invalid value 78830 - SAMNAPUR - GONDIA DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10475 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 78830 | 78830 | 78830 - SAMNAPUR - GONDIA DEMU | 2 | | | | | | | | | | |
Invalid value 78831 - GONDIA - SAMNAPUR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10476 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 78831 | 78831 | 78831 - GONDIA - SAMNAPUR DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 78832 - SAMNAPUR - GONDIA DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10477 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 78832 | 78832 | 78832 - SAMNAPUR - GONDIA DEMU | 2 | 0 | 0 | 0 | 0 | | | 0 | 0 | | |
Invalid value 79601 - AJMER - JAIPUR DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10478 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 79601 | 79601 | 79601 - AJMER - JAIPUR DEMU | 2 | | | | | | | | | | |
Invalid value 79602 - JAIPUR - AJMER DEMU in field route_long_name
route_long_name shouldn't contain the route_short_name value, as both fields are often displayed side-by-side.
in line 10479 of routes.txt
| route_id | route_short_name | route_long_name | route_type | IN_CC | IN_2A | IN_SL | IN_3A | IN_3E | IN_FC | IN_2S | IN_1A | IN_GN | IN_UNRESERVED |
| 79602 | 79602 | 79602 - JAIPUR - AJMER DEMU | 2 | | | | | | | | | | |