Every one of those 1 sits in a single category, logistics. Barbil – Bolanikhadan doubling project is most often covered alongside Energy, Mineral and Cement Corridor, which appears in 1 of these 1 story. Barbil – Bolanikhadan doubling project appears in 1 tracked Supply Chain story from October 1, 2026.
Figures are computed live from our source-verified story record
— see our methodology for how impact and
sentiment are derived.
What the coverage shows about Barbil – Bolanikhadan doubling project
Every one of those 1 sits in a single category, logistics. Barbil – Bolanikhadan doubling project is most often covered alongside Energy, Mineral and Cement Corridor, which appears in 1 of these 1 story. Barbil – Bolanikhadan doubling project appears in 1 tracked Supply Chain story from October 1, 2026. The tracked stories average 2 original sources each.
Stories tracked
1
Sources per story
2
Computed from the 1 stories linked to this entity, with beat comparisons drawn from all 10 Supply Chain stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.
Coverage cohort
Appears alongside
Other entities that clear the same relevance threshold in stories also covering Barbil – Bolanikhadan doubling project. Shared-story counts are live from our verified record — not editorial picks.
Indian Railways approved a ₹122 crore doubling of the 6 km Barbil–Bolanikhadan section, targeting 8.9 MTPA of additional freight capacity for high-grade iron ore and pellets. The current single line already moves about 9 MTPA and six loaded rakes per day, so the project directly de-bottlenecks a critical mineral corridor ahead of SAIL mine expansion. Supply chain teams should track construction risks and commissioning timelines for improved rail reliability to steel plants and ports.
Barbil – Bolanikhadan doubling project is linked from 1 story on this site, each scored at or above our 35% relevance threshold — see how these pages are built.
See something wrong on this page — a misattributed entity, a wrong stat, a broken source
link? Report a data issue.
