Koderma–Hazaribagh–Barkakana–Ranchi line
railway route in India
The Koderma–Hazaribagh–Barkakana–Ranchi line is an Indian railway line connecting Koderma Junction in the Asansol–Gaya section with Hazaribagh Town, Barkakana and Ranchi. This 211-kilometre (131 mi) track is under the jurisdiction of South Eastern Railway and East Central Railway.
History
This line was announced in rail budget 1999 under the rule of Atal Bihari Vajpayee. The Koderma–Hazaribagh Town section was completed on 20 February 2015. It was inaugurated by Prime Minister Narendra Modi along with Jharkhand Governor Syed Ahmad, Chief Minister Raghubar Das, Union Railways Minister Suresh Prabhu, Union Minister of State for Railways Manoj Sinha, Union Minister of State for Finance and Hazaribagh MP Jayant Sinha.
The 57 km-long Hazaribagh Town–Barkakana section was opened for passenger trains on 7 December 2016 by Railway Minister Suresh Prabhu in the presence of Chief Minister Raghubar Das. As the line passes through a coal mining belt it will carry a lot of coal, in addition to passenger traffic.
Special passenger train service started on 31 March 2017 from Barkakana Junction to Sidhwar station of Barkakana–Ranchi new line section.
Trial run of passenger train between Tatisilwai and Shanki railway station (31.4 km) of Ranchi–Barkakana new rail line done on 17 January 2018.
New Railway line between Tatisilwai and Sanki was inaugurated by CM Raghubar Das on 29 August 2019.
“Koderma–Hazaribagh–Barkakana–Ranchi line” enters the record as railway route in India. Crown Archives preserves that source wording while asking what Koderma, Hazaribagh and Barkakana can confirm, complicate or overturn.
Why this record matters
“Koderma–Hazaribagh–Barkakana–Ranchi line” is worth following because a concise public description often conceals a longer documentary argument. Here, Koderma, Hazaribagh and Barkakana provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jun 23, 2025. The linked authority identifier is Q96386192. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1999, 2015, 2016 and 2017.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Koderma–Hazaribagh–Barkakana–Ranchi line”, its source revision and the description used here.
- Expand the search: follow Koderma–Hazaribagh–Barkakana–Ranchi line primary sources, Koderma–Hazaribagh–Barkakana–Ranchi line archive and Koderma research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Koderma–Hazaribagh–Barkakana–Ranchi line”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Koderma–Hazaribagh–Barkakana–Ranchi line” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.