Numbers 35:16–21, King James Version
Italic words were supplied in the English translation for clarity.
Numbers 35:16–21
Weapons, Force, Hatred, and Ambush Mark Murder
Killing with iron, a lethal stone or wooden object, striking from hatred, or ambush identifies a murderer; the ancient law assigns death at the blood avenger's hand when the killer is found.
Numbers 35:16–21 opens with “And if he smite him with an instrument of iron, so that he die, he is a murderer:…” and closes with “Or in enmity smite him with his hand, that he die: he that smote him shall surely be….”
How the passage moves
Instrument and lethal capacity establish several explicit murder cases.
Hatred and ambush add intent before the avenger's role.
A phrase that matters
refuge / blood avenger
מִקְלָט / גֹּאֵל הַדָּם · miqlat / goel haddam
In 35:16-21, this wording keeps the unit's own claim and limit together: The law does not authorize private revenge, execution without fair trial, weapon vigilantism, racialized suspicion, or treating one object as automatic proof.
How this should shape us
How should this shape us today?
Evaluate a property or jurisdiction claim through current law, consent, evidence, displacement risk, gender equality, indigenous and resident rights, and accessible remedy rather than biblical name matching. The law does not authorize private revenge, execution without fair trial, weapon vigilantism, racialized suspicion, or treating one object as automatic proof.
Teach it back
Explain Numbers 35:16–21 in your own words. Include its place in Numbers' movement from Sinai to Moab, both movements within this thought unit, one material uncertainty, one affected person or group, and one use the complete context rules out.
Your explanation stays in this browser. It is not sent or saved.
Go deeper
The explanation above is meant to stand on its own. Open these notes only if you want language, history, disagreements, or source locations.
Read it sentence by sentenceEach line inside the larger movement
Literary movement
Instrument and lethal capacity establish several explicit murder cases. Hatred and ambush add intent before the avenger's role.
Contextual judgment
Killing with iron, a lethal stone or wooden object, striking from hatred, or ambush identifies a murderer; the ancient law assigns death at the blood avenger's hand when the killer is found. The law does not authorize private revenge, execution without fair trial, weapon vigilantism, racialized suspicion, or treating one object as automatic proof.
Original-language wording and grammarTechnical detail appears only where it helps
refuge / blood avenger
The law limits vengeance through asylum and adjudication while retaining institutions that modern justice must not copy uncritically.
How certain? probableWhat the first readers would have understoodRelevant history and culture
Covenantal rhetoric, law, and historical setting
Allotments, inheritance, boundaries, towns, refuge, tribal holdings, Transjordan settlement, and Zelophehad's daughters organize land through ancient patrilineal tribes before entry. Protection and constraint coexist. For this unit, reconstruction remains bounded by the received movement: Killing with iron, a lethal stone or wooden object, striking from hatred, or ambush identifies a murderer; the ancient law assigns death at the blood avenger's hand when the killer is found.
How certain? probableWhy translations sometimes differMaterial translation choices
KJV wording and material alternatives
The pinned KJV wording of 35:16-21 is read with the complete Masoretic record and NET translator notes. A material chapter expression is “refuge / blood avenger” (miqlat / goel haddam): The law limits vengeance through asylum and adjudication while retaining institutions that modern justice must not copy uncritically.
How certain? probableEarlier Scripture and inherited backgroundSupported quotations, allusions, and inherited ideas
Numbers within Torah and Jewish Scripture
Exodus, Leviticus, Deuteronomy, Joshua, Psalms, prophets, and later Jewish Scripture are compared where they frame, retell, or receive this unit. Final-form relationships remain primary; compositional, chronological, and historical alternatives are stated rather than harmonized away.
How certain? strongHow this connects with the rest of ScriptureThe passage's own meaning remains primary
Canonical relationships after the first horizon
Genesis supplies ancestral promise; Joshua narrates allocation; Deuteronomy presents land law and memory; later prophets and histories contest possession and injustice. Numbers does not settle present borders.
How certain? probableTextual variantsManuscript differences only when they affect meaning
Textual witnesses and reconstruction limits
The pinned KJV remains the displayed text. The reviewed Masoretic record and NET notes disclose material wording, number, name, syntax, and witness questions where present; no variant is silently substituted and textual silence is not converted into certainty.
How certain? probableWhere careful interpreters disagreeThe strongest options and their difficulties
Where do careful interpreters disagree?
Best judgment: Interpreters debate historical geography, boundary idealization, settlement, source layers, women's property status, tribal memory, asylum development, and relationship to Joshua and Deuteronomy. The law's patrilineal gains and limits must both remain visible. For “Weapons, Force, Hatred, and Ambush Mark Murder,” confidence is strongest in the received unit's stated sequence and literary function; source, date, demography, geography, mechanism, archaeology, and historical reconstruction remain probable, plausible, or uncertain as the evidence warrants.
How certain? probableTheology that emerges from this passageConclusions drawn after reading the complete section
Theological contribution
Land is portrayed as gift held through ordered allotment, protected blood, communal responsibility, and generational continuity rather than limitless private conquest. This unit contributes that claim without making its severe action, unequal institution, or narrator-approved judgment ethically easy: Killing with iron, a lethal stone or wooden object, striking from hatred, or ambush identifies a murderer; the ancient law assigns death at the blood avenger's hand when the killer is found.
How certain? strongTheological contribution
Across Numbers this unit contributes to the movement from Sinai's ordered camp through wilderness crisis and generational death toward Moab, succession, worship, land, and justice: Killing with iron, a lethal stone or wooden object, striking from hatred, or ambush identifies a murderer; the ancient law assigns death at the blood avenger's hand when the killer is found.
How certain? strongCommon ways this passage gets misusedFair explanation, context check, and stronger reading
The law does not authorize private revenge, execution without fair trial, weapon vigilantism, racialized suspicion, or treating one object as automatic proof.
A vivid command, blessing, curse, land claim, penalty, speech, or poetic line can feel easier to transfer than the complete covenant case and its affected people.
Killing with iron, a lethal stone or wooden object, striking from hatred, or ambush identifies a murderer; the ancient law assigns death at the blood avenger's hand when the killer is found.
Property systems should make access, inheritance, safety, due process, affected communities, and unequal bargaining power visible instead of treating land as morally self-authenticating. This unit also keeps the following boundary explicit: The law does not authorize private revenge, execution without fair trial, weapon vigilantism, racialized suspicion, or treating one object as automatic proof.
Instrument and lethal capacity establish several explicit murder cases. Hatred and ambush add intent before the avenger's role.
This unit does not turn Israel's camp, priesthood, purity system, vow, war, land, penalty, census, or leadership arrangement into a direct constitution for a modern state, church, family, or military.
A vivid command, blessing, curse, land claim, penalty, speech, or poetic line can feel easier to transfer than the complete covenant case and its affected people.
Killing with iron, a lethal stone or wooden object, striking from hatred, or ambush identifies a murderer; the ancient law assigns death at the blood avenger's hand when the killer is found.
Property systems should make access, inheritance, safety, due process, affected communities, and unequal bargaining power visible instead of treating land as morally self-authenticating. This unit also keeps the following boundary explicit: The law does not authorize private revenge, execution without fair trial, weapon vigilantism, racialized suspicion, or treating one object as automatic proof.
Instrument and lethal capacity establish several explicit murder cases. Hatred and ambush add intent before the avenger's role.
This passage must not be used for antisemitism, supersessionism, ethnic stigma, nationalism, genocide, conquest, misogyny, abuse, coercive obedience, date-setting, prosperity guarantees, or cruelty toward vulnerable people.
A vivid command, blessing, curse, land claim, penalty, speech, or poetic line can feel easier to transfer than the complete covenant case and its affected people.
Killing with iron, a lethal stone or wooden object, striking from hatred, or ambush identifies a murderer; the ancient law assigns death at the blood avenger's hand when the killer is found.
Property systems should make access, inheritance, safety, due process, affected communities, and unequal bargaining power visible instead of treating land as morally self-authenticating. This unit also keeps the following boundary explicit: The law does not authorize private revenge, execution without fair trial, weapon vigilantism, racialized suspicion, or treating one object as automatic proof.
Instrument and lethal capacity establish several explicit murder cases. Hatred and ambush add intent before the avenger's role.
Research trail and exact locationsThe source record behind this section
Supports: Exact reader-facing KJV wording, paragraph metadata, supplied-word markup, and complete verse coverage for this thought unit.
Numbers 35:16–21, pinned eng-kjv2006 USFM corpus
Supports: Hebrew wording, morphology, names, numbers, speeches, poems, legal clauses, older-English controls, and translation limits.
Open Scriptures MorphHB v.2.2, commit 6a5db284c715c18b239422e57bb89684e6a19f00, wlc/Num.xml, Masoretic words and morphology for 35:16–21
Supports: Unit-bounded translation, syntax, lexical, ritual, legal, number, name, poetic, and selected textual notes; silence is not evidence.
NET Bible Numbers PDF, complete 134-page PDF, translation and translator notes attached to 35:16–21
Supports: Moab movement, law, leadership transition, land, war, women, refuge, and compositional framing.
Yale Bible Study, Numbers Part 2, complete two-page study guide sections on Balaam, Baal Peor, second census, women and inheritance, war with Midian, Transjordan, itinerary, boundaries, Levite and refuge cities, and final inheritance, applied to Numbers 35:16–21
Supports: Refuge-city adjudication, intent, blood vengeance, legal revision, due-process gains, and remaining ethical limits.
TheTorah, “Revising the Laws of Murder to Accommodate Blood Vengeance,” complete comparison of Exodus, Numbers 35, and Deuteronomy 19 on murder, accident, asylum, avenger, witnesses, and legal development, applied to Numbers 35:16–21
Sources for This Section
These records identify the source, the claim it supports, and the exact location used. A source remains evidence to evaluate; it does not replace the biblical text.
Biblical text
King James (Authorized) Version — eng-kjv2006
eBible.org and CrossWire Bible Society
USFM archive eng-kjv2006_usfm.zip; source files dated 2026-08-19; downloaded 2026-08-24; archive SHA-256 aec1b3b26c622fd3d963d2bbac963016b9513246ffbfa20da00bb100372ea007; normalized corpus SHA-256 09aef51d90488aa7b9722b3fd9a93f4b25f6bf2064c5fd798fb39673c300ddf2.
Supports: Exact reader-facing KJV wording, paragraph metadata, supplied-word markup, and complete verse coverage for this thought unit.
Exact location: Numbers 35:16–21, pinned eng-kjv2006 USFM corpus
Open source ↗hebrew text and morphology
Open Scriptures Hebrew Bible: Numbers
Open Scriptures Hebrew Bible Project
Open Scriptures, release 2.2, 2021
Supports: Hebrew wording, morphology, names, numbers, speeches, poems, legal clauses, older-English controls, and translation limits.
Exact location: Open Scriptures MorphHB v.2.2, commit 6a5db284c715c18b239422e57bb89684e6a19f00, wlc/Num.xml, Masoretic words and morphology for 35:16–21
Open source ↗translation and translator notes
NET Bible: Numbers with translators' notes
Biblical Studies Press
eBible.org distribution of the NET Bible, source files dated 2026-08-08
Supports: Unit-bounded translation, syntax, lexical, ritual, legal, number, name, poetic, and selected textual notes; silence is not evidence.
Exact location: NET Bible Numbers PDF, complete 134-page PDF, translation and translator notes attached to 35:16–21
Open source ↗modern critical open study guide
Numbers Part 2
Yale Bible Study
Yale Divinity School, 2023 course edition
Supports: Moab movement, law, leadership transition, land, war, women, refuge, and compositional framing.
Exact location: Yale Bible Study, Numbers Part 2, complete two-page study guide sections on Balaam, Baal Peor, second census, women and inheritance, war with Midian, Transjordan, itinerary, boundaries, Levite and refuge cities, and final inheritance, applied to Numbers 35:16–21
Open source ↗modern jewish scholarly open legal and compositional study
Revising the Laws of Murder to Accommodate Blood Vengeance
TheTorah.com named scholarly contributor
TheTorah.com, 2022
Supports: Refuge-city adjudication, intent, blood vengeance, legal revision, due-process gains, and remaining ethical limits.
Exact location: TheTorah, “Revising the Laws of Murder to Accommodate Blood Vengeance,” complete comparison of Exodus, Numbers 35, and Deuteronomy 19 on murder, accident, asylum, avenger, witnesses, and legal development, applied to Numbers 35:16–21
Open source ↗