Did Jesus Make a Crucial Historical Blunder in the Gospel of Mark?
Mark 2:26. Jesus mentions David eating consecrated bread “in the days of Abiathar the high priest.” Bible scholars point out a problem. The historical record shows Ahimelech, not Abiathar, was the high priest when this happened. How could Jesus mix up such a simple detail? Today, we’re discovering why this apparent mistake actually reveals something fascinating about ancient Jewish expression and the truthfulness of Scripture.
The Problem in Mark 2:26
Welcome back to Word for Word, I’m Austin Duncan, and today we’re tackling a passage that’s caused more than its fair share of headaches for Bible students, seminary professors, and late night internet debaters alike. If you’ve spent any time looking up supposed contradictions in the Bible, this one almost always shows up near the top of the list. It lands in the top five on skeptic websites, in “Bible errors” listicles, and in debates between Christians and atheists. And honestly, I get why. On the surface, it looks like a clean catch. It looks like Jesus, or Mark, or maybe both, got a simple historical detail wrong.
And if that were true, the implications would be enormous. We’re not talking about a minor copyist issue tucked away in an obscure genealogy. We’re talking about Jesus Himself, the Son of God, apparently misidentifying a priest in a story He uses to make a theological argument. If Jesus can’t get a basic Old Testament detail right, why should we trust Him on anything else? That’s the logic critics use, and on the surface, it sounds compelling.
But today I want to show you something. I want to show you that this passage, far from being a weakness in the biblical record, is actually a showcase for how precise, culturally rich, and theologically loaded the New Testament really is. The deeper you dig into Mark 2:26, the stronger it gets. And by the time we’re done, I think you’ll agree that what looks like a stumble is actually a very strong example of ancient communication working exactly as it was meant to.
So let’s lay it out plainly before we go any further.
In Mark chapter 2, Jesus is in a confrontation with the Pharisees. His disciples have been walking through grain fields on the Sabbath, plucking heads of grain and eating them, and the Pharisees are outraged. They see this as a violation of Sabbath law. In response, Jesus reaches back into the Old Testament and brings up the story of David. He says, “Have you never read what David did when he was in need and hungry, he and those with him: how he went into the house of God in the days of Abiathar the high priest, and ate the showbread, which is not lawful to eat except for the priests, and also gave some to those who were with him?”
That’s a brilliant argument. Jesus is making a powerful point about mercy and human need taking priority over ceremonial regulation. But critics have zeroed in on five words: “in the days of Abiathar the high priest.” Because when you go back to 1 Samuel 21, the priest who gave David the bread wasn’t Abiathar. It was Ahimelech, Abiathar’s father.
So the question becomes, did Jesus make a mistake? Did Mark get it wrong? And if either of them did, what does that mean for the reliability of the entire New Testament?
That’s what we’re going to work through today. And I think by the end of it, you’ll see that this supposed error isn’t an error at all. It’s actually a window into how ancient Jewish people communicated, how language works across cultures and centuries, and why the Bible continues to hold up under intense scrutiny.
If you were with us last week in Episode 57, where we looked at the mustard seed question, then you know we’ve been in a stretch of episodes dealing with alleged mistakes in the New Testament. And I love these episodes because they force us to do the very thing good Bible study requires. We slow down, we look carefully, and we refuse to settle for the easy answer when a better one is waiting beneath the surface.
That’s what we’re doing today. And yes, we’re going to get into some Greek, some Aramaic, some history, and some ancient literary convention. But I’ll keep it clear and accessible. Because when you see how this puzzle fits together, it doesn’t just resolve one tricky verse. It gives you a stronger framework for handling difficult passages in general.
A supposed contradiction that falls apart under careful examination isn’t a weakness of Scripture. It’s a testimony to its depth.
The Story Jesus Is Referring To
David arrives at Nob
Before we can understand what Jesus said in Mark 2, we need to understand the story He’s referring to. So let’s go back to 1 Samuel 21 and set the scene.
David, the future king of Israel, is on the run. King Saul has turned against him. Saul’s jealousy has curdled into murderous rage, and David has fled for his life. He isn’t traveling with an army. He isn’t surrounded by his mighty men. He’s essentially a fugitive, running with a handful of companions, and he’s desperate.
He arrives at a place called Nob. Nob was a priestly city. It sat near Jerusalem in the hill country of Benjamin, and it functioned as a religious center for Israel during that period. The tabernacle equipment and the sacred bread were kept there, and the priests who served the Lord operated from that location. After the destruction of Shiloh, Nob appears to have become a major center for priestly activity. So this wasn’t just some random stop on David’s escape route. It was a sacred place.
The priest in charge there was a man named Ahimelech, the son of Ahitub. When David shows up, Ahimelech is startled. The text says he came trembling to meet David, which tells you something about the political climate. Having the king’s son in law show up unannounced, alone, in a time of upheaval, that wasn’t a casual visit. Ahimelech knew something was wrong.
David asks for food, and Ahimelech tells him there’s no ordinary bread available. The only bread on hand is the consecrated bread, the bread of the Presence, which by law was reserved for the priests. Leviticus 24 explains that twelve loaves were placed before the Lord every Sabbath, representing the twelve tribes of Israel. When fresh loaves replaced them, the old loaves were to be eaten by Aaron and his sons in a holy place. This was sacred bread.
But Ahimelech gives it to David anyway, after confirming that David’s men have remained ceremonially clean. David takes the bread, and the moment becomes a striking example of how mercy and human need can intersect with ceremonial law. That’s exactly the point Jesus is drawing on centuries later.
And the Old Testament text is clear. 1 Samuel 21 identifies the priest as Ahimelech. He’s the one who speaks to David. He’s the one who provides the bread. He’s the one presiding at Nob. There’s no real ambiguity there.
The massacre at Nob and Abiathar’s escape
What happens next matters a lot.
In 1 Samuel 22, Saul learns that Ahimelech helped David. He’s furious. He summons the priests of Nob, accuses them of conspiring against him, and orders their execution. Doeg the Edomite carries out the slaughter, killing eighty five priests. It’s one of the darker moments in the Old Testament.
But one priest escapes. Abiathar, the son of Ahimelech, survives and flees to David. 1 Samuel 22:20 tells us exactly that. From that point on, Abiathar becomes deeply connected to David’s story. He brings the ephod with him, which means he brings the priestly means of seeking the Lord’s guidance. He becomes David’s priest, companion, and advisor through the wilderness years.
When David hides in caves, Abiathar is there. When David moves from place to place, Abiathar follows. When David inquires of the Lord, Abiathar is often the priestly link in that process. He isn’t a minor figure. He becomes one of the defining priestly figures in David’s life.
And when David becomes king, Abiathar rises with him. He serves alongside Zadok as one of the leading priests in the kingdom. Even later, when his story ends painfully under Solomon, Abiathar remains one of the most recognizable priestly names connected to David.
So here’s the simple timeline.
Ahimelech was the priest who gave David the bread at Nob.
Ahimelech was then killed by Saul.
Abiathar, Ahimelech’s son, escaped and joined David.
Abiathar later became the priest most closely associated with David’s reign.
The father gave the bread. The son became famous.
Watch where the story changes hands
The whole issue becomes clearer when the sequence is seen as a visual shift, not just as two names on a page.
Event actor to remembered priestly era
The critical move is not between right and wrong. It is between one scene and the larger narrative span that follows it.
The whole scene begins in danger and need.
Sacred space becomes the setting.
This is the event level detail in 1 Samuel 21.
The story does not stop with the bread scene.
The priestly line now moves into David’s wilderness story.
His name becomes tied to David for years.
The son now carries the stronger narrative association.
And that’s why the wording in Mark 2:26 raises eyebrows. But it also sets up the key question. Not just, “Did Jesus say the wrong name?” but, “What did that phrase mean to the people who first heard it?”
The Language in Mark 2:26
The Greek phrase itself
This is where things get especially interesting, because it’s the part casual critics often skip.
The Greek phrase in question is ἐπὶἈβιαθὰρ τοῦἀρχιερέως. Most English translations render it, “in the days of Abiathar the high priest.” That translation is fine, but it can sound more precise to modern ears than the original phrase necessarily was. When we hear “in the days of Abiathar the high priest,” we often read it like a timestamp. We hear it the way we’d hear someone say, “during the presidency of Lincoln” or “while Queen Elizabeth was on the throne.” We assume it means Abiathar was actively serving as high priest at the exact moment David entered Nob.
But that isn’t the only way the phrase can work.
Break the phrase apart, and the pressure starts to ease
Hover the Greek phrase pieces. This is not a flat English sentence living in a vacuum. It lives inside a first century language world.
epi Abiathar archiereos
The phrase itself becomes clearer when its pieces are treated like living parts of one expression.
Can point to a broader period, not only a narrow timestamp.
The better known priestly name in David’s larger story.
Can identify who a person is known as, not only one earlier moment.
The saying likely came through Aramaic before it appeared in Greek.
Readout
The phrase becomes less brittle when read in its own world.
ἐπὶ
This is where modern readers often over-tighten the sentence. The phrase can work as a broader historical locator.
It does not have to behave like a camera timestamp.
The issue shifts from “wrong name” to “what kind of reference is this line making?”
The Greek preposition ἐπὶ with the genitive is flexible. It can mark time broadly. It can mean something like “in the time of,” “during the era associated with,” or even, in some contexts, function as a reference marker tied to a known section or figure. In other words, it doesn’t always function like a modern stopwatch.
Similar kinds of references elsewhere
We actually see similar flexibility elsewhere in Scripture.
In Luke 3:2, Luke refers to the ministry of John beginning “in the high priesthood of Annas and Caiaphas.” But strictly speaking, Caiaphas held the office at that point, while Annas had already been removed from it years earlier. And yet Annas still marked the period because he remained highly influential and widely recognized.
Acts 11:28 uses a similar kind of broad marker with Claudius.
Romans 11:2 may be even more interesting. Paul refers to “the passage about Elijah.” The Greek construction there has led some scholars to suggest that Mark 2:26 may even mean something like “in the section about Abiathar,” that is, in the scriptural passage associated with the Abiathar story.
Now, I don’t think we have to insist that’s the only explanation. But it is a real possibility. And it shows that the language is more flexible than critics often allow.
Why modern readers hear it too narrowly
This is one of those places where our instincts can mislead us. We often approach ancient texts expecting modern journalistic precision in every phrase. But ancient speakers weren’t giving AP style fact sheets. They were using living language inside shared cultural memory.
Think of how we talk today.
If someone said, “Back in the days of Vince Lombardi, the Packers were building something special,” nobody would stop and say, “Well actually, this specific game you mentioned happened just before his official tenure began.” The name identifies the era. Or if someone tells a story and says, “Back when I was working for Dr. Johnson,” even if the exact event happened during the interview stage just before the official start date, we still understand the point. The name marks the chapter.
That’s how people speak. And Jesus was speaking to real people, in a real moment, using real language.
The pressure changes when readers move from surface reading to fuller context
Drag the slider. This is not about replacing Ahimelech. It is about understanding why Abiathar can still carry the larger reference.
Event precision versus narrative association
The more context comes into view, the less the objection feels like a clean contradiction.
The event actor in the one scene at Nob.
The priestly name tied to David’s larger remembered story.
Readout
The scale is not deciding who gave the bread. It is showing why the reference works the way it does.
Surface pressure
At first glance, the objection feels strong because readers are looking only at the event actor in 1 Samuel 21.
The Aramaic World Behind the Greek
There’s another angle here that matters. Jesus likely wasn’t speaking Greek in this conversation. He was likely speaking Aramaic, and Mark later recorded the saying in Greek for his audience. That matters because the Aramaic background can help explain how the phrase was heard. Some scholars, including Maurice Casey, have argued that the underlying Aramaic expression would have naturally conveyed a broader association, something like “in the days of Abiathar, the great priest,” where the title identified the person by the role for which he was most widely known. In that case, the phrase wouldn’t mean, “Abiathar was actively presiding at that exact second.” It would mean, “You know the period I’m talking about, the Abiathar period of David’s life.”
That’s important. Titles in ancient speech often functioned descriptively, not as tiny chronological claims pinned to a single moment. If I refer to “King David as a shepherd boy,” I’m not confused about when he became king. I’m identifying him by the name or role people know.
So the Greek in Mark isn’t some strange wording that created a problem. It may actually be a faithful rendering of how Jesus’ original Aramaic statement would have worked in normal speech.
Every translation carries interpretation with it. And every interpretation has to account for the world that produced the words.
Why Abiathar Would Be the Name People Recognized
Ahimelech mattered, but Abiathar became the defining figure
Another factor is simple name recognition.
Between Ahimelech and Abiathar, which name would have carried more weight for a Jewish audience? Almost certainly Abiathar. Ahimelech appears at a pivotal moment, yes, but he disappears from the story almost immediately because Saul has him killed. Abiathar stays with David across the long arc of David’s life. When people thought about David and priestly association, they thought about Abiathar. That means naming Abiathar in a quick reference makes good sense. It’s not confusing. It’s clarifying.
Albert Barnes made a similar point long ago with an analogy. He noted that we might speak of “General Washington” at an event that occurred before Washington actually held that title, because we identify him by the role he later became famous for. That isn’t deception. It’s normal speech. And really, we do this all the time. We talk about “President Lincoln” debating in the 1850s, even though he wasn’t president then. We say “the Apostle Paul” when referring to Saul before his missionary career. We use the best known identifier because that’s how people understand who we mean.
Jesus may be evoking the whole David narrative
There’s also a deeper reason Abiathar may be the better name in context.
Jesus isn’t merely citing a random incident. He’s invoking the David story as a whole. David is the rejected but anointed king. Jesus is the true rejected and anointed King. David has a priestly companion linked to his wilderness suffering and eventual reign. That companion is Abiathar. So invoking Abiathar may carry more narrative weight than invoking Ahimelech. Ahimelech fits the narrow event. Abiathar fits the whole arc. And Jesus’ argument is about more than one isolated detail. It’s about what the David story means.
The Father and Son Connection
There’s still more to think about. Abiathar may not have been the officiating priest who handed David the bread, but he almost certainly belonged to that same priestly household and community. He was Ahimelech’s son. He was already part of the priestly line. He later escaped from Nob itself. So it’s at least plausible that he was present in some capacity when these events unfolded, even if the text doesn’t explicitly say so.
Now, we shouldn’t lean too hard on that, because the text doesn’t directly state his presence in 1 Samuel 21. But it does remind us that the story isn’t about two isolated names with no relationship to each other. It’s about a father and son in the same priestly family, at the same priestly center, in the same chain of events.
And that matters because critics often frame this as if Jesus confused two totally unrelated people. He didn’t. The connection between Ahimelech and Abiathar is immediate, familial, and narrative.
The Old Testament Itself Shows Some Name Complexity
There’s another fascinating wrinkle. In a few places in the Old Testament, the names Ahimelech and Abiathar appear in ways that have sparked discussion among interpreters. For example, 2 Samuel 8:17 and related passages create questions about the father son order or the way the names are presented. Scholars have long debated whether those reflect scribal transposition, family naming patterns, or something else.
We shouldn’t overstate that. It doesn’t mean the names were interchangeable in every setting. But it does mean this priestly family line is not handled in a way that supports the hyper simplistic objection critics often make.
At minimum, it shows that the tradition surrounding these names was close, linked, and discussed. So again, the issue is not as neat and tidy as “Jesus used the wrong guy’s name and everyone should have noticed.”
What the Manuscripts of Mark Actually Show
This part matters a lot.
If “Abiathar” in Mark 2:26 were an obvious blunder, you’d expect the manuscript tradition to reflect more discomfort with it. You’d expect early scribes to correct it aggressively. You’d expect a strong stream of manuscripts replacing “Abiathar” with “Ahimelech.”
But that isn’t what we find.
The earliest and strongest manuscript tradition preserves “Abiathar.” There are a few later adjustments and omissions, which is exactly what you’d expect if later scribes, reading the text more mechanically, tried to smooth out what they thought was a problem. But the strongest evidence points to “Abiathar” as the original reading.
And that’s important.
The earliest readers of Mark were far closer than we are to the language, to Jewish patterns of speech, and to the Old Testament story world. If they preserved the reading rather than correcting it, that strongly suggests they didn’t hear it as a blunder.
Augustine, centuries later, also took it in that broader sense, as a general reference to Abiathar’s time rather than a narrow statement that Abiathar was the priest actively presiding in that exact scene.
When the earliest tradition leaves a phrase intact, it’s often a clue that the problem is more modern than ancient.
What Jesus Is Actually Doing in the Passage
This may be the most important piece.
Jesus is not engaged in an Old Testament trivia contest. He’s in a confrontation over the Sabbath. The Pharisees are accusing His disciples, and Jesus answers by reaching into Israel’s story and drawing out a theological point.
David, God’s anointed king, was in need. He and his men were hungry. He received bread ordinarily reserved for priests, and the point of the story is that human need and covenant purpose mattered more than the rigid way the Pharisees were reading things. Then Jesus moves from David to Himself. That’s the real punch of the passage.
The citation is doing more than citing
This visual shows why Jesus reaches for David here. The story is not only precedent. It is pattern.
Parallel bridge
The line about Abiathar sits inside a much larger move. Jesus is bringing David’s story into the room because it helps interpret His own ministry.
Rejected king
David is the anointed king, yet he is moving through opposition and danger.
Rejected Messiah
Jesus stands under scrutiny and opposition even as His true authority is present.
Followers in need
Hunger and hardship frame the story at Nob.
Disciples under accusation
Need and Sabbath controversy frame the story in Mark 2.
Sacred bread in sacred space
The issue involves priestly setting and consecrated bread.
Sacred law in living context
The issue becomes how the Sabbath should be read in the presence of God’s anointed one.
Mercy is not denied
The moment does not end in divine condemnation.
Mercy is the point
Jesus is not relaxing holiness. He is showing the heart and authority that govern it.
He isn’t saying merely, “David did something unusual, so my disciples can too.” He’s saying, “If you understood what David’s story meant, you’d understand what’s happening in front of you right now.”
And here’s where Abiathar becomes especially loaded. Abiathar is not just a random priestly name. He is David’s priest, David’s companion in rejection, David’s link to priestly legitimacy during the years before the throne. That means the reference may be doing more than locating an event. It may be evoking a whole world of associations between David’s rejected kingship and Jesus’ own ministry. In other words, Abiathar brings the David narrative with him in a way Ahimelech does not. That doesn’t prove the point all by itself. But it helps explain why this wording is not clumsy. It’s fitting. Jesus’ words are doing more theological work than a flat surface reading can catch.
How Scholars Have Approached the Passage
Serious interpreters across the centuries have not treated this as some impossible problem.
Albert Barnes argued that the statement is perfectly understandable once we recognize that Abiathar was the better known priestly figure associated with David and that the phrase need not mean he was the officiating priest at that precise instant.
Charles Ellicott made a similar case, noting that the more prominent name can naturally function as the identifier for the period.
William Lane treated the wording as a historical reference marker that orients the hearer to the broader section of Israel’s story.
R. T. France discussed the possibility that the phrase may even point to the passage associated with Abiathar, which would make the whole objection collapse immediately.
Maurice Casey and others have highlighted the importance of the Aramaic background, showing how the phrase could naturally carry a broader, more descriptive force than modern readers often assume.
Now, scholars don’t all land on the exact same explanation. That’s worth saying plainly. But that actually helps the case rather than hurting it. Why? Because there isn’t just one plausible answer. There are several plausible answers, all grounded in real linguistic, historical, and literary evidence. The question was never whether there’s a responsible explanation. The question was whether we were willing to look for one.
Responding to the Skeptic Carefully
I want to say this clearly and kindly.
A lot of modern criticism of Mark 2:26 works by assuming the most rigid modern reading of the phrase and then declaring the Bible guilty when it doesn’t fit that assumption. But that’s poor method. Ancient texts have to be read as ancient texts. Jewish texts have to be read with Jewish habits of speech in mind. And sayings of Jesus have to be read in the kind of oral, relational, culturally rich environment in which they were first delivered. It’s like criticizing a poem because it doesn’t read like a legal contract. You’ve imposed the wrong expectations from the start. Now, that doesn’t mean questions are bad. Questions are good. Questions often lead us deeper. Asking, “Why does Mark say Abiathar?” is the right question. But stopping there and treating the difficulty as a proof of error is lazy. A question is a doorway, not a conclusion. And really, that’s a pattern you see again and again in alleged contradictions. They look devastating from a distance. But once you step closer, slow down, and do the work, they usually turn out to be much more about our assumptions than about any failure in the text itself.
Charge, evidence, context, verdict
This visual treats the objection like a case file. It feels stronger at first than it does after the evidence is laid out.
Exhibit board
The objection often sounds airtight until language, narrative flow, and audience recognition are brought into the room.
Jesus or Mark got the priest wrong
Ahimelech gives the bread in 1 Samuel 21, yet Mark 2:26 names Abiathar.
Event level is clear
The objection is not invented. Ahimelech is the priest in the immediate scene.
Language range matters
The phrase can act more like a broad historical locator than a narrow timestamp.
Name recognition matters
Abiathar becomes the priestly figure most associated with David’s long story.
The argument is larger
Jesus is making a Sabbath and kingship argument, not offering a detached footnote.
What About the Historical Setting and Archaeology?
The broader Davidic setting is well grounded historically. The Tel Dan Stele gives us an early extra biblical reference to the “House of David,” which is a major piece of evidence that David was not a later literary invention. The Dead Sea Scrolls also confirm the antiquity and transmission of texts like Samuel long before the time of Jesus. As for Nob itself, scholars have proposed possible locations, but its exact identification remains debated. So it’s better not to build too much on any single archaeological claim about the site. Still, the overall framework matters. Jesus is drawing from Israel’s remembered history, not from some floating myth detached from place and tradition. That matters because the passage in Mark is rooted in a real narrative world. This is not Jesus citing folklore carelessly. He is appealing to Israel’s Scriptures and Israel’s history in a precise, meaningful way.
What This Teaches Us About Reading the Bible
Context matters more than we think
If all we’ve done today is solve a puzzle, we’ve missed the larger point. This passage teaches us something about how to read the entire Bible.
Scan it layer by layer, not only at the surface
This is the reusable method. It turns one hard passage into a reading habit your audience can carry into the next one.
Diagnostic scan
The issue usually changes shape when the text is examined in layers instead of at first glance only.
Readout
The stages rotate on their own so the visual keeps moving even if the reader does nothing.
Slow down
Most alleged contradictions feel strongest when they are read quickly, emotionally, and without context.
Context isn’t optional. It’s everything. We live in a world of fragments, headlines, clips, and sound bites. We skim. We react. We move on. But the Bible wasn’t written to be skimmed like a feed. It was written in languages, cultures, and literary forms that reward patient reading.
When we ignore that, difficult passages can look worse than they are. When we respect it, the text begins to open.
Difficult passages often deepen understanding
This is one of the great surprises of Bible study. The passages that trouble us often become the passages that teach us the most.
If Mark 2:26 had never bothered anyone, many of us never would have looked carefully at how ἐπὶ works, how ancient Jewish time references functioned, how Aramaic may stand behind Mark’s wording, or how the David and Abiathar connection strengthens Jesus’ argument.
The difficulty pushed us deeper. And deeper study made the passage stronger, not weaker.
That happens a lot in Scripture.
The Bible can handle scrutiny
This matters for people carrying real questions.
Maybe you’ve read something in Scripture that confused you. Maybe someone sent you a video listing “contradictions in the Bible.” Maybe you’ve had a doubt you were afraid to say out loud. Hear me clearly. The Bible is not fragile. It does not need protection from honest questions. It can stand up to them.
Mark 2:26 has been examined for centuries. And the more closely people look, the less it looks like an error and the more it looks like a passage that has to be heard the way it was originally spoken.
Truth doesn’t fear examination. It rewards it.
Humility has to run both ways
Skeptics can be premature when they declare the Bible guilty before doing the work. But Christians can also be unhelpful when they act threatened by the question itself. The best response is neither panic nor smugness. It’s humility. It’s being willing to say, “That’s a good question. Let’s look closely.” And when we do, the text often proves far more coherent than the surface reading suggested.
How to Explain This to Someone Else
If someone asks you, “Doesn’t Mark 2:26 prove Jesus got the priest’s name wrong?” here’s a simple path you can follow.
Start by affirming the question. It is a fair question. It deserves a real answer.
Then explain the story. Ahimelech gave David the bread. Abiathar was his son. Abiathar escaped, joined David, and later became the priest most closely associated with him. So the two names are directly connected in the narrative.
Then explain the language. The phrase translated “in the days of” can work more broadly than a modern timestamp. It can refer to an era or a known historical frame of reference.
Then give a common sense illustration. We do this kind of thing in our own speech all the time. We identify a period by the person most associated with it. We use later titles for earlier events. That isn’t deception. It’s normal communication.
Then, if the conversation allows, show the bigger point. Jesus is not fumbling a detail. He’s evoking the David story in a way that strengthens His argument about the Sabbath and about His own identity.
The goal isn’t to win a fight. The goal is to remove a barrier. Because behind many Bible objections is not just a debater looking for points. Sometimes it’s a real person trying to figure out whether this book can be trusted. And yes, it can.
Wrapping Up
So, did Jesus make a crucial historical blunder in the Gospel of Mark?
No. He didn’t. What He did was use a perfectly normal ancient way of locating an Old Testament event within the era associated with Abiathar, the priest most famously connected with David’s story. He used the name His audience would recognize, the name that carried the broader narrative weight, and the name that made His theological point hit harder. Mark recorded it faithfully. The manuscript tradition preserved it. The early church wasn’t troubled by it. And careful study shows that the supposed contradiction dissolves once we read the passage on its own terms instead of forcing modern assumptions onto it.
Mark 2:26 isn’t a crack in the foundation of biblical reliability. It’s a reminder that Scripture rewards careful reading. It shows us that language lives inside culture, that ancient communication doesn’t always sound like modern reporting, and that difficult passages often become clearer, not murkier, the more carefully we study them.
That’s the thread I want you to hold onto, not just for this verse, but for every verse that makes you stop and think. The Bible wasn’t written to be easy. It was written to be true. And true things, when you put in the work to understand them, prove themselves worth the effort. You can trust every word of it, not because you’ve shut your brain off, but because you’ve brought it fully to the text. If you’ve got questions about today’s topic, drop them in the comments. I read every single one. If this episode helped you, share it with someone who’s wrestling with the same issue. And if you haven’t subscribed yet, I’d love to have you join us for the rest of this journey.
I’m Austin Duncan, and this has been Word for Word.
