Battle of Chora
2007 battle during the War in Afghanistan

The Battle of Chora was a military engagement in Chora District, Uruzgan Province, Afghanistan, occurring from 15 to 19 June 2007. The battle was between ISAF – primarily composed of Dutch troops – and allied Afghan forces against anti-coalition militias (ACM), believed to be affiliated with the Taliban. The battle centered on control of the Chora District's administrative center, a strategic location for the Taliban due to its role as a key ground route linking the contested Gizab District in the north to the provincial capital, Tarinkot. According to some press reports, the fighting was the largest Taliban offensive of 2007 in Afghanistan, and resulted in the death of one Dutch soldier, as well as approximately 50 to 80 civilians and 70 Taliban fighters.
Background
In August 2006, the ISAF Task Force Uruzgan (TFU) assumed responsibility for Uruzgan Province, southern Afghanistan, replacing the U.S.-led Operation Enduring Freedom in the region. The TFU, led by the Dutch, comprised approximately 1,200 Dutch troops and several hundred Australian personnel. The Dutch military sought to restore its reputation, particularly after its failure to prevent the Srebrenica massacre in 1995. The Dutch government emphasized that the mission would prioritize reconstruction over combat.
The TFU established its two primary bases near the towns of Tarinkot (Kamp Holland) and Deh Rawood. Additionally, two patrol bases were positioned in the Dehrashan Valley and north of Deh Rawood.
This brief starts where responsible research should: with the source description of “Battle of Chora” as 2007 battle during the War in Afghanistan. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the history & society register because the source frames it as 2007 battle during the War in Afghanistan. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Chronology, provenance and viewpoint should be read together before a broad social or political interpretation is accepted. The source revision retrieved here is dated Aug 21, 2026. The linked authority identifier is Q1485258. Authority coordinates are 32.853, 66.085. None of the 1 selected statements returned an explicit reference. The first chronological checks are 2007, 2006 and 1995.
Institutional narratives can privilege the records that survived while minimizing voices that were never formally collected. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Battle of Chora”, its source revision and the description used here.
- Expand the search: follow Battle of Chora primary sources, Battle of Chora archive and Battle 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 “Battle of Chora”?
- Who created the surviving record, and for what administrative purpose?
- Which voices are present, absent or mediated by the institution?
Search terms from this dossier
This entry incorporates text from “Battle of Chora” 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.