In the back corridors of skeptic websites—Skeptic’s Annotated Bible, Infidels.org, EvilBible.com—you’ll find numbered lists of “Bible contradictions.” Many believers have encountered these lists and felt their confidence shaken. Others have dismissed them without examination, which does no service to truth.
The passages before us today—2 Samuel 23:8 and 1 Chronicles 11:11—appear on nearly every such list:
These are the names of the mighty men whom David had: Josheb-basshebeth a Tahchemonite, chief of the captains, he was called Adino the Eznite, because of eight hundred slain by him at one time. — 2 Samuel 23:8 (NASB)
These constitute the list of the mighty men whom David had: Jashobeam, the son of a Hachmonite, the chief of the thirty; he lifted up his spear against three hundred whom he killed at one time. — 1 Chronicles 11:11 (NASB)
One text says David’s chief warrior killed 800 men; the other says 300. One calls him “Josheb-basshebeth”; the other “Jashobeam.” The skeptic’s conclusion? The Bible can’t get its own story straight.
But is that conclusion warranted? Or does a careful examination of the evidence point somewhere else entirely?
The Challenge Stated Fairly
The objection deserves its strongest formulation:
If the Bible is inspired by an omniscient God, why do parallel accounts of the same event disagree on basic facts—the hero’s name and the number of enemies killed?
This isn’t a trivial question. If Scripture cannot accurately preserve the details of a military exploit, why should we trust its claims about salvation, resurrection, or eternity?
The stakes are genuinely high. We’re not dealing with interpretive differences or theological nuance—we’re dealing with apparent factual discrepancy between two biblical texts describing the same event.
Where We Stand
Before proceeding, transparency about our theological commitments:
We approach Scripture as God’s written Word—inspired, authoritative, and sufficient. But inspiration pertains to the original autographs, not to every manuscript copy made over subsequent centuries. The discipline of textual criticism—carefully examining manuscript evidence to understand transmission history—is not an attack on Scripture’s reliability but a tool for understanding it.
God sovereignly ordained that His Word would come to us through human instruments and historical processes. Understanding those processes illuminates rather than undermines our confidence in what Scripture actually says.
The Skeptic’s Case
Let’s hear the objection at its strongest, as its proponents present it:
The Masoretic Text of 2 Samuel 23:8 reads that “Josheb-basshebeth, a Tahchemonite, chief of the captains” killed 800 men at one time. The parallel in 1 Chronicles 11:11 names “Jashobeam, a Hachmonite, chief of the thirty” who killed 300.
Critics observe:
- The names differ substantially (“Josheb-basshebeth” vs. “Jashobeam”)
- The tribal identification differs (“Tahchemonite” vs. “Hachmonite”)
- The title differs (“chief of the captains” vs. “chief of the thirty”)
- The casualty count differs by 500 (a 167% variance)
From this, skeptics conclude that these “contradictions” prove the Bible is unreliable, perhaps even demonstrating multiple authorship with no divine oversight. The compilation websites treat this as exhibit A in their case against inerrancy.
Why This Objection Resonates
We should acknowledge why many find such objections persuasive.
First, there’s an emotional dimension. People often approach Scripture hoping to find fault—not from mere intellectual curiosity, but from a desire to escape its claims on their lives. The heart is not neutral territory.
Second, our culture runs on soundbites. “800 vs. 300—contradiction!” fits a tweet. The careful work of textual criticism does not. Skeptical lists exploit this asymmetry, presenting apparent problems without context and relying on readers not to investigate further.
Third, many Christians have been taught a “dictation” model of inspiration that imagines God directly penning every letter, bypassing human involvement entirely. When faced with evidence of scribal transmission, this fragile model shatters—though it was never the historic Christian understanding to begin with.
Scripture itself acknowledges that human hearts suppress truth in unrighteousness (Romans 1:18). The issue is not merely intellectual but moral. We want certain conclusions to be true, and we find evidence that supports what we want.
Clearing the Ground: What Kind of Problem Is This?
Before examining solutions, we must identify what kind of problem we’re facing. This is not a theological contradiction (different doctrines), an ethical contradiction (different moral standards), or even a historical contradiction (different events). This is a textual transmission issue—a question about how ancient manuscripts were copied and preserved. The distinction matters enormously. A contradiction in the original autographs would be one thing. Variations introduced during copying over centuries are quite another. No serious scholar—secular or religious—claims the manuscript tradition is identical to the autographs in every detail. The question is whether we can identify what the original said and whether variations affect the substance of the message.
What the Evidence Actually Shows
The Name: Scribal Corruption, Not Competing Traditions
The name “Josheb-basshebeth” (יֹשֵׁב בַּשֶּׁבֶת) in 2 Samuel 23:8 is linguistically bizarre. It translates roughly as “he who sits in the seat”—not a plausible Israelite personal name. Scholars across the theological spectrum recognize this as a textual corruption.
What happened? The evidence points to a well-documented scribal practice called the “Baal-to-bosheth” substitution. During the early monarchic period, names containing “Baal” (meaning “lord” or “master”) were common and religiously neutral. But as worship of the Canaanite deity Baal threatened Israelite monotheism, later scribes substituted “bosheth” (meaning “shame”) for “Baal” in personal names.
This is not speculation—we can trace it directly:
- Saul’s son “Ish-baal” (1 Chronicles 8:33) becomes “Ish-bosheth” in 2 Samuel 2:8
- Gideon’s alternate name “Jerub-baal” (Judges 6:32) appears as “Jerub-besheth” in 2 Samuel 11:21
The Septuagint (the Greek translation of the Hebrew Scriptures, dating to the 3rd-2nd century BC) provides crucial evidence. Several Greek manuscripts of 2 Samuel 23:8 read Iebosthe or Isbaal, suggesting the original Hebrew name was indeed “Ishbaal” or something similar. “Josheb-basshebeth” appears to be a further corruption—the consonants of a “bosheth” name misread or misdivided in later copying.
The Chronicles text preserved “Jashobeam” (meaning “the people return”)—a standard Israelite name following normal onomastic patterns.
Far from demonstrating scribal carelessness about Scripture, this actually shows us scribes wrestling with theological concerns (eliminating Baal-names) and the inevitable challenges of copying texts by hand over centuries. We can trace the corruption and identify the original reading.
The Missing Verb: A Clearer Case of Copying Error
The Samuel text contains another telltale sign of corruption. It includes the phrase “he was Adino the Eznite” (הוא עדינו העצני)—a person who appears nowhere else in Scripture and whose name has no clear etymology.
But look at the parallel in Chronicles: “he lifted up his spear” (הוא עורר את חניתו).
Place these phrases side by side in Hebrew script, and the connection becomes apparent. The consonants are strikingly similar. What happened? A copyist working with a worn or damaged manuscript misread the consonantal text. The verbal phrase describing what the hero did was corrupted into a nonsense name describing who he was.
This explains why 2 Samuel 23:8 reads oddly even in translation—it lacks a main verb! The sentence makes grammatical sense only when we recognize “Adino the Eznite” as a scribal misreading of “he lifted up his spear.” This isn’t harmonization imposed from outside. It’s what the internal evidence demands. Ancient translations wrestled with the same difficulty; the Latin Vulgate attempted to make sense of “Adino” by treating the words as common nouns rather than a name.
The Numbers: How Numerals Were Transmitted
What about 800 versus 300? Several factors contribute to numerical variations in ancient manuscripts:
Method of notation: Hebrew numerals were written as full words, not symbols. The words for “three” (שָׁלֹשׁ) and “eight” (שְׁמוֹנֶה) both begin with the letter shin (ש). A single faded letter, a smudge, or damage to a manuscript could lead a copyist to mistake one for the other.
Stroke-based systems: Some ancient texts used stroke-based numerical notation similar to Egyptian Hieratic. Misreading grouped strokes was an easy error.
Different stages of tradition: Chronicles was compiled in the post-exilic period (around the 4th century BC) and appears to have followed a Hebrew text tradition similar to what we find in the Dead Sea Scrolls—often more accurate than the ancestor of our Masoretic Text of Samuel.
The Dead Sea Scrolls have revolutionized our understanding here. Fragments like 4QSamᵃ frequently align with the Septuagint against the Masoretic Text of Samuel, proving that many Septuagint variants weren’t translation errors but reflected an older, sometimes better-preserved Hebrew text.
A striking parallel: In 1 Samuel 17:4, the Masoretic Text records Goliath’s height as six cubits and a span (over 9 feet), while 4QSamᵃ and the Septuagint record four cubits and a span (under 7 feet). The evidence suggests numerical expansion occurred in some strands of the Samuel tradition.
The 800/300 discrepancy likely arose the same way—natural manuscript variation in a text with a particularly difficult transmission history, not contradictory original accounts.
The Broader Picture: Samuel’s Troubled Transmission
Here’s context the skeptic websites don’t provide: Textual scholars across the theological spectrum recognize that the Masoretic Text of 1-2 Samuel is in notably poor condition compared to other biblical books.
This isn’t a defensive Christian claim—it’s a scholarly consensus spanning secular and religious critics. The Samuel manuscripts show evidence of:
- Haplography: Scribes accidentally omitting text when their eyes jumped between similar phrases
- Misreading of archaic letter forms: The transition from Paleo-Hebrew to square Aramaic script created opportunities for confusion
- Worn exemplars: The scroll most copied seems to have been damaged before it became the standard
The Chronicles text, compiled later with access to different source manuscripts, often preserves readings that help us understand what the Samuel originals said.
None of this threatens biblical reliability. It’s simply honest acknowledgment of how ancient texts were transmitted—and evidence that careful scholarship can recover original readings.
A Word About Authorial Intent
There’s another dimension worth noting: the books of Samuel and Chronicles had different purposes.
The author of Samuel, writing during or after the Babylonian exile, compiled a “warts-and-all” history. He included David’s adultery, his census sin, and the moral ambiguity of his reign. The warrior list in 2 Samuel 23 forms part of an appendix emphasizing David’s dependence on his men. Notably, Uriah the Hittite appears at the end—a pointed reminder of David’s greatest failure.
The Chronicler, writing for post-exilic Jews rebuilding their identity, focused on David as temple-preparer and covenant king. He placed the warrior list immediately after Jerusalem’s capture, framing these men as foundational supporters of a unified kingdom.
Different purposes; same historical core. Neither author invented a warrior or fabricated exploits. But they organized and emphasized material according to their audiences’ needs.
What About Inerrancy?
Does any of this compromise biblical inerrancy? Not at all—if we understand what inerrancy actually claims.
Inerrancy pertains to the original autographs, not to every subsequent copy. The Chicago Statement on Biblical Inerrancy (1978) explicitly acknowledges: “We affirm that copies and translations of Scripture are the Word of God to the extent that they faithfully represent the original.”
The existence of textual variants was known to the church fathers, the Reformers, and every serious student of Scripture throughout history. Augustine, writing in the 4th century, attributed numerical discrepancies in parallel Old Testament passages to scribal error, not original contradiction.
The discipline of textual criticism exists precisely because we take Scripture’s original text seriously enough to work at recovering it. We don’t have to pretend manuscript transmission was flawless to affirm that what the prophets and apostles actually wrote was true.
The Irony of the Skeptic’s Position
There’s a significant irony in citing this passage as evidence against biblical reliability.
The skeptic’s argument assumes we should expect perfect transmission—that an inspired book should have arrived in our hands unchanged through 3,000 years of hand-copying. But why should anyone expect this? The biblical authors were inspired; the countless scribes who copied their work were not.
More to the point: the very fact that we can identify these variations and trace their origins demonstrates the robustness of the textual tradition, not its unreliability. We have so many manuscripts that we can compare them, spot copying errors, and work backward toward the original text.
Contrast this with most ancient literature, which survives in a handful of manuscripts copied centuries after the original. We have thousands of Hebrew and Greek manuscripts, early translations in multiple languages, and quotations in ancient writers—a wealth of evidence that allows us to reconstruct original readings with high confidence.
What Remains Unchanged
Whether the original text recorded 300, 800, or even both (as a record of two separate exploits—some scholars’ suggestion), the theological substance remains untouched:
- David’s kingdom was established by extraordinary warriors
- God granted remarkable victories to His anointed king
- The Davidic line pointed forward to a greater Son who would conquer not 300 or 800, but all the enemies of God’s people through His death and resurrection
The gospel does not hang on whether Jashobeam killed exactly 300 or 800 Philistines. But our confidence in Scripture’s reliability grows, not shrinks, when we discover that apparent contradictions dissolve under careful examination.
An Invitation
If you’ve encountered lists of “Bible contradictions” and found yourself troubled, you’re not alone. But I’d encourage you to apply the same scrutiny to the skeptic’s claims that you’d apply to any other argument.
Ask: Does this objection account for the evidence of textual transmission? Does it acknowledge that “contradiction” and “copying variation” are different categories? Does it engage with the actual scholarly literature, or does it present soundbites hoping you won’t investigate?
The Bible has endured far more rigorous criticism than internet lists. It emerges, again and again, as a text whose reliability can be tested—and trusted.
We welcome honest questions. If you’d like to explore further, consider Brotzman and Waltke’s Old Testament Textual Criticism: A Practical Introduction, or Emanuel Tov’s Textual Criticism of the Hebrew Bible. The evidence is there for those willing to examine it.
This article is the first in a series addressing apparent contradictions compiled by skeptic websites. Our aim is not triumphalism but truth—engaging objections honestly and showing that careful examination strengthens, rather than undermines, confidence in Scripture.