Harosheth Haggoyim
Fortress described in the Book of Judges
Harosheth Haggoyim (Hebrew: חרושת הגויים, lit. Smithy of the Nations) is a fortress described in the Book of Judges as the fortress or cavalry base of Sisera, commander of the army of "Jabin, King of Canaan".
Sisera is described as having had nine hundred iron chariots with which he fought the Israelites. In Judges 5, the mother of Sisera is poignantly described looking from a window, presumably in Harosheth Haggoyim, and asking "Why is his chariot so long in coming? Why is the clatter of his chariots delayed?" when he does not return from the battle where his army was defeated by the Israelites, and he was killed by the Biblical heroine Yael.
Modern identifications
Hariss in Lebanon
In the late 19th century, Victor Guérin identified the southern Lebanese village of Hariss with Harosheth, a location with which the PEF's Survey of Western Palestine seems to agree.
El-Ahwat in Israel
Archaeologist Adam Zertal of the University of Haifa proposed that the site of El-Ahwat, between Katzir-Harish and Nahal Iron, is the site of Harosheth Haggoyim, and the more recent find of a fancy chariot linchpin by archaeologist Oren Cohen seems to corroborate this hypothesis.
The site was excavated from 1993-2000 by teams from the University of Haifa and the University of Cagliari in Sardinia. The dig was headed by Professor Zertal. The dig revealed a fortified place dating to the Late Bronze Age and early Iron Age (13th-12th centuries BCE).
The public source identifies “Harosheth Haggoyim” as fortress described in the Book of Judges. This brief keeps that definition visible, then builds a research path around Harosheth, Haggoyim and Fortress.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Harosheth Haggoyim”, the useful work is to connect “fortress described in the Book of Judges” to the records capable of establishing context and consequence.
The strongest evidence will usually combine a dated visual record with documents produced by the authority responsible for the place. The source revision retrieved here is dated Jun 11, 2026. The linked authority identifier is Q2920321. None of the 1 selected statements returned an explicit reference. The first chronological checks are 1993 and 2000.
Modern boundaries and familiar names can conceal earlier jurisdictions or structures that do not align with the present site. 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
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Harosheth Haggoyim”, its source revision and the description used here.
- Expand the search: follow Harosheth Haggoyim primary sources, Harosheth Haggoyim archive and Harosheth 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 “Harosheth Haggoyim”?
- What physical evidence or contemporary plan supports the description?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “Harosheth Haggoyim” 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.