11 of the Strangest Passages in the Bible — and What They Actually Say

Rick Last updated 
image.png
image.png Download

UPDATED BY VCG ON 9/28/2026 @ 04:20 EST


Anyone can do this, but most won't.


ChatGPT - Library of Rickandria


LIBRARY OF RICKANDRIA PRESENTS

11 of the Strangest Passages in the Bible — and What They Actually Say


SCRIPTURE BREAKDOWN BY VCG
SEPTEMBER 2026



Abstract


The Bible is filled with passages that have become so familiar that readers hardly notice how unusual they are. Elsewhere, however, Scripture drops us into scenes that remain genuinely startling: a donkey speaks; a hand appears at a royal feast and writes judgment on a wall; Moses is hidden in a rock while the glory of God passes by; mysterious priestly objects called the Urim and Thummim are used to seek divine judgment; Ezekiel sees living creatures moving beside wheels covered with eyes; Revelation describes a lake of fire as “the second death”; and the book of Job confronts its suffering protagonist with Behemoth and Leviathan.


Those passages naturally invite explanation.


The danger is that an explanation can quietly become more certain than the biblical text itself.


This study therefore follows a deliberately cautious method. The wording of the King James Bible, Pure Cambridge Edition, is treated as the primary text for the study. Historical evidence, archaeology, manuscript studies, ancient-language research, and modern biblical scholarship are then brought alongside the text—not placed above it and not confused with it.


Our central question is simple:


What does Scripture actually say, what can reasonably be inferred from it, and where does interpretation begin?


The distinction matters because some of the Bible's strangest passages become clearer when read in context. Others remain mysterious even after serious study. In a few cases, archaeology gives us surprising external evidence. In others, the historical evidence warns us against explanations that have been repeated confidently for generations.


The goal is therefore neither to explain away the strange nor to make it stranger than it is.


The goal is to read carefully.



How We Are Reading These Passages


Before entering the individual texts, it helps to establish five different kinds of questions.


Scripture asks what the biblical text actually says.


Textual history asks how that wording has come down to us through manuscripts, translations, and textual traditions.


History and archaeology ask whether people, places, institutions, words, objects, or cultural practices can be illuminated by evidence outside the Bible.


Interpretation asks what the author or passage means and how one part of Scripture should be read in relation to another.


Psychology of reading asks what readers—including ourselves—may be tempted to do when we encounter ambiguity.


These questions overlap, but they are not interchangeable.


An archaeological discovery mentioning Balaam, for example, would not prove that Balaam's donkey spoke. It could establish that a Balaam son of Beor was remembered outside the biblical tradition.


Likewise, proving that a particular interpretation is ancient does not automatically prove that it is what the biblical author intended.


And discovering uncertainty does not automatically mean nothing can be known.


That distinction will guide the entire paper.



A Word About Mystery and the Human Mind


Strange texts exert a particular pull on us because human beings dislike unresolved patterns.


Psychologists use the expression need for cognitive closure for the desire to arrive at a definite answer rather than remain with uncertainty or ambiguity. Research associated with Arie Kruglanski and Donna Webster describes how a strong desire for closure can encourage people to “seize” upon an available explanation and then “freeze” around it rather than continuing to examine alternatives.


That does not mean that anyone who reaches a firm biblical conclusion is psychologically biased. Nor does psychology tell us whether a theological interpretation is true.


It simply gives us a useful warning.


When Scripture leaves a gap, the mind wants to fill it.


What did Jesus write on the ground?


What exactly were the Urim and Thummim?


What did Moses actually see?


What animal was the re'em?


What was the physical structure of Ezekiel's wheels?


Questions like these create an intellectual vacuum, and vacuums attract explanations.


Responsible study therefore requires a willingness to say three words that are often harder than they sound:


We don't know.


That is not unbelief.


Sometimes it is simply textual honesty.



1. The Urim and Thummim: Israel's Mysterious Instruments of Judgment


The Urim and Thummim are among the most intriguing objects in the Hebrew Bible because Scripture treats them as important while giving remarkably little explanation of what they physically were.


God tells Moses concerning Aaron's priestly breastplate:


“And thou shalt put in the breastplate of judgment the Urim and the Thummim...”

— Exodus 28:30


Numbers later says that Joshua is to stand before Eleazar the priest, who would:


“ask counsel for him after the judgment of Urim before the LORD.”

— Numbers 27:21


And late in Saul's troubled reign:


“the LORD answered him not, neither by dreams, nor by Urim, nor by prophets.”

— 1 Samuel 28:6


These passages establish something important.


Whatever the Urim and Thummim were, they were associated with the priesthood and with seeking judgment or direction from the LORD.


A scholarly overview in the Encyclopedia of the Bible notes that even ancient Greek translations varied considerably in how they rendered the terms, suggesting that knowledge of their exact nature had already become uncertain. Modern scholarly reconstructions therefore remain hypothetical.


Some researchers understand them as a form of sacred lot. Others have explored possible connections with ancient Near Eastern divinatory practices. A study of priestly divination in ancient Israel describes the Urim and Thummim as an officially sanctioned means of obtaining divine judgment while acknowledging that exactly how they operated remains unknown.


That distinction is crucial.


The Bible tells us their function more clearly than their mechanism.


What about David and the ephod?


David repeatedly “inquired of the LORD,” and in 1 Samuel 23 Abiathar brings an ephod to him. David asks whether Saul will come to Keilah and whether Keilah's inhabitants will surrender him.


It is reasonable to connect this priestly consultation with the kind of divine inquiry associated elsewhere with the Urim.


But the chapter itself does not say:


“David used the Urim and Thummim.”


We should therefore describe the connection as probable or possible rather than explicit.


That may sound overly cautious, but it illustrates the method of this entire study.


We are not trying to make the Bible less mysterious.


We are trying not to make our reconstruction part of the Bible.


What Scripture tells us


The Urim and Thummim belonged to Israel's priestly system and were associated with receiving judgment before the LORD.


What Scripture does not tell us


Their precise shape, material, internal construction, or method of operation is never clearly described.


Why it matters


Modern readers sometimes turn the Urim and Thummim into elaborate technological devices, prophetic gemstones, coded instruments, or lost supernatural machinery.


Those possibilities may be imaginative.


They are not statements of Scripture.


The biblical mystery is already interesting enough.



2. Balaam's Donkey: When the Prophet Cannot See and the Animal Can


Numbers 22 gives us one of the strangest reversals in biblical narrative.


Balaam is riding toward Moab when:


“the angel of the LORD stood in the way for an adversary against him.”


Balaam does not see the angel.


His donkey does.


Three times the animal responds to the danger, and three times Balaam strikes her.


Then:


“And the LORD opened the mouth of the ass...”

— Numbers 22:28


The donkey asks Balaam why he has beaten her.


Balaam answers.


Only afterward:


“the LORD opened the eyes of Balaam, and he saw the angel of the LORD standing in the way.”

— Numbers 22:31


The narrative's irony is difficult to miss.


Balaam is the visionary.


The donkey sees.


Balaam is the professional speaker of oracles.


The donkey speaks truth to him.


Balaam wishes he had a sword with which to kill the donkey.


The angel standing invisibly in front of him already has one.


The text eventually tells us that the animal's actions had saved Balaam's life.


The point is therefore deeper than “the Bible has a talking donkey.”


The episode overturns Balaam's status.


The famous seer cannot see until God opens his eyes.



The historical Balaam question


Here external evidence becomes unusually interesting.


At Tell Deir ‘Alla in modern Jordan, archaeologists discovered an Iron Age plaster inscription that repeatedly mentions a figure called Balaam son of Beor and describes him as a seer.


The inscription does not tell the biblical story.


There is no talking donkey, no Balak commissioning a curse against Israel, and no attempt to reproduce Numbers 22–24.


But the shared name and patronymic are striking.


Scholar Baruch Levine's work on the Deir ‘Alla inscriptions notes the appearance of Balaam son of Beor as a renowned seer outside the biblical tradition. The archaeological context has generally been dated around the early first millennium BCE, with the inscription commonly placed around the ninth or eighth century BCE.


What does that prove?


It demonstrates that a tradition concerning a Balaam son of Beor circulated in the Transjordanian world independently of the biblical text.


It does not prove every event in Numbers.


That difference between external attestation and verification of an entire narrative is exactly the kind of historical distinction a careful Bible study should maintain.



What the text says


God miraculously gives the donkey speech and later opens Balaam's eyes.


The chapter attributes the speech directly to the LORD's action.


What archaeology adds


A nonbiblical Iron Age inscription also remembers a Balaam son of Beor as a seer.


What archaeology cannot tell us


The inscription cannot verify the donkey episode.


Why the passage matters


Numbers is exposing the limits of human spiritual prestige.


The person who supposedly sees what others cannot see is rescued by an animal that sees what he cannot.



3. The Handwriting on the Wall: Belshazzar's Last Night


Daniel 5 opens in a royal banquet.


Belshazzar orders that vessels taken from the temple at Jerusalem be brought into the feast. The king and his guests drink from them while praising gods of gold, silver, brass, iron, wood, and stone.


Then the room changes.


A hand appears.


It writes on the wall.


Daniel eventually reads the inscription:


“MENE, MENE, TEKEL, UPHARSIN.”

— Daniel 5:25


Daniel interprets the words:


MENE — God has numbered the kingdom.


TEKEL — the king has been weighed and found wanting.


PERES — the kingdom is divided and given to the Medes and Persians.


Daniel then states that Belshazzar is killed that same night.


This is the origin of our expression “the handwriting on the wall.”


It means that judgment has already been announced even if the person receiving it has not yet accepted what is coming.



Belshazzar outside the Bible


For a time, Belshazzar was known primarily through Daniel and later traditions.


Cuneiform evidence changed that discussion.


The British Museum possesses a clay cylinder of Nabonidus that includes a prayer for Nabonidus and Belshazzar his son. Other Babylonian administrative texts also mention Belshazzar and officials associated with the crown prince.


The evidence identifies Belshazzar as a son of Nabonidus and a powerful royal figure who exercised authority during his father's reign.


That historical evidence is important—but again, precision matters.


It establishes Belshazzar's existence and royal status.


It does not independently establish the supernatural hand or Daniel's interpretation of it.


The British Museum itself describes Belshazzar historically as Nabonidus's son and royal regent.


This also means that the relationship between Daniel's royal terminology and known Neo-Babylonian history requires careful discussion rather than simplistic claims either that archaeology “proved Daniel” or that Belshazzar was entirely fictional.



What Daniel emphasizes


Daniel is not primarily interested in giving us a ghost story.


The point comes in Daniel's speech to the king.


Belshazzar knew what had happened to Nebuchadnezzar when pride overtook him, Daniel says, yet:


“hast not humbled thine heart.”


The strange handwriting therefore has a straightforward theological meaning.


The king has been judged.


The spectacle gets our attention.


Daniel's explanation tells us why it happened.



4. “Thou Shalt Not Seethe a Kid in His Mother's Milk”


Few biblical commandments have inspired more explanations from fewer words.


The law appears three times:


“Thou shalt not seethe a kid in his mother's milk.”

— Exodus 23:19; compare Exodus 34:26 and Deuteronomy 14:21


Why would God prohibit this particular act?


The biblical text does not say.


That has not stopped generations of interpreters from supplying reasons.


One popular explanation claims that boiling a young goat in its mother's milk was a Canaanite fertility ritual and that Israel was being commanded not to imitate pagan worship.


That explanation is often repeated as though archaeologists had discovered the ritual.


The evidence is much less secure.


A scholarly discussion of the prohibition notes that an Ugaritic text once thought to describe such a ritual is damaged and does not securely establish the alleged practice.


Other explanations have proposed that the law expresses compassion, that it symbolically separates life from death, that it guards the proper order of creation, that it has something to do with firstfruits and agricultural obligations, or even that the expression may have been idiomatic rather than a literal cooking instruction. The sheer variety of proposals tells us something important: there is no universally demonstrated explanation.


Even the Hebrew verb traditionally rendered “seethe” or “boil” has received renewed linguistic examination, though the ordinary sense of cooking remains well established.



What about kosher separation of meat and dairy?


Rabbinic Jewish tradition eventually developed extensive dietary regulations separating meat and dairy from this command.


That development belongs to the history of Jewish interpretation and halakhah.


It should not be confused with the literal wording of the Torah.


The Torah says not to cook a kid in its mother's milk.


Later Jewish interpretation asks how broadly that prohibition should be applied.


Those are related questions, but they are not identical.



What we can responsibly say


The command is genuine, repeated, and evidently important enough to occur in several legal contexts.


Its original rationale is not explicitly supplied.


A pagan ritual explanation is possible, but it should not be presented as an established historical fact.


Sometimes responsible exegesis ends with:


We know the command. We do not know the reason with certainty.


That is a better conclusion than converting an attractive theory into revelation.



5. Moses Sees God's “Back Parts”


Exodus 33 may contain the most startling anthropomorphic language in the Torah.


Moses asks:


“I beseech thee, shew me thy glory.”

— Exodus 33:18


God replies:


“Thou canst not see my face: for there shall no man see me, and live.”

— Exodus 33:20


Moses is placed in a cleft of the rock and covered while God's glory passes by.


Then comes the strange line:


“thou shalt see my back parts: but my face shall not be seen.”

— Exodus 33:23


What exactly does that mean?


The text does not explain what Moses physically perceived.


That silence matters because the same chapter has already said:


“the LORD spake unto Moses face to face, as a man speaketh unto his friend.”


Yet only a few verses later Moses is told that he cannot see God's face and live.


The language therefore cannot simply be flattened into a single literal visual description.



Anthropomorphic language


Biblical scholars use the word anthropomorphism when human features or actions are attributed to God.


The Hebrew Bible speaks of God's face, hand, arm, eyes, ears, feet, and even nostrils.


Interpreters have long debated how those expressions should be understood.


A recent close study of Exodus 33 describes the passage as revolving precisely around the tension between divine presence, metaphor, corporeality, and the impossibility of directly comprehending God. Broader scholarship on divine anthropomorphism in the Pentateuch likewise demonstrates that there is no single uncontested theory explaining all such language.


So saying “this is anthropomorphic language” identifies the phenomenon.


It does not by itself solve it.



Something else happens in Exodus 34


Immediately after Moses is permitted this limited encounter, the LORD passes before him and proclaims his name and character:


“The LORD, The LORD God, merciful and gracious, longsuffering, and abundant in goodness and truth...”


The narrative therefore moves from Moses asking to see God's glory to God proclaiming who he is.


That may be one of the passage's most important interpretive clues.


Moses wants sight.


The revelation ultimately emphasizes God's name and character.



What the text says


Moses experienced an extraordinary manifestation of God's glory.


The KJV calls what he was permitted to see God's “back parts.”


What it does not say


It does not provide an anatomical description.


Interpretation


Some readers understand the language more literally, others as accommodation or metaphorical description of divine manifestation.


The passage itself establishes a limit: Moses receives genuine revelation, but not unrestricted sight of God.



6. Jesus and the Woman Taken in Adultery


John 7:53–8:11 is simultaneously one of the most beloved stories about Jesus and one of the most important textual questions in the New Testament.


The KJV includes it.


Our Pure Cambridge Edition reads:


“He that is without sin among you, let him first cast a stone at her.”

— John 8:7


And after the accusers leave:


“Neither do I condemn thee: go, and sin no more.”

— John 8:11


The episode is sometimes presented as Jesus confronting an Old Testament law of execution and replacing it with a new law of compassion.


That summary is much too simple.



First, read the Mosaic law carefully


Deuteronomy 22:22 does not say that only the woman involved in adultery should die.


It refers to both parties.


That immediately raises a question in John 8:


Where is the man?


The law also required more than an accusation for capital judgment. Deuteronomy 17:6 requires two or three witnesses, and verse 7 requires the hands of the witnesses to be first upon the condemned person.


John explicitly tells us that the question was a trap:


“This they said, tempting him, that they might have to accuse him.”


So the legal setting is already compromised.


Jesus is not merely asked an abstract question about whether adultery is sinful.


He is placed inside a staged accusation.



Then there is the manuscript question


The KJV contains the passage without brackets.


But the history of the Greek manuscripts is complicated.


Many of the earliest surviving Greek witnesses to John do not contain John 7:53–8:11 in this location. Other manuscripts include it, sometimes at different places.


New Testament scholar Chris Keith describes the conclusion that the passage was not originally part of the Gospel of John as close to a scholarly consensus while noting that questions about its earlier tradition and historical origin remain debated.


The NET Bible's extensive textual note similarly lists early manuscripts that omit the account and later manuscript traditions that preserve it at several locations.


There are also scholars who defend its traditional inclusion or argue for a stronger claim to Johannine authenticity, so the discussion should not be misrepresented as though no dissent exists.


For a KJV study, the correct approach is not to pretend the passage is absent.


It is in the KJV.


We study it as part of the KJV text while acknowledging honestly that its manuscript history is unusual.



What did Jesus write on the ground?


We do not know.


The text never tells us.


Suggestions have included the sins of the accusers, parts of the law, names, Jeremiah 17:13, legal testimony, or simply an intentional refusal to engage with the trap immediately.


Any of those may be suggested.


None should be preached as though John told us.



Mercy without calling evil good


Another detail gets lost when the story is reduced to “Jesus refuses judgment.”


His final command is:


“go, and sin no more.”


The woman's conduct is not reclassified as morally acceptable.


The accusers are exposed.


Condemnation does not proceed.


The woman is shown mercy.


And she is still called away from sin.


The story holds those elements together.



7. Jesus Curses a Fig Tree When “the Time of Figs Was Not Yet”


Mark does something curious with the fig tree.


Jesus approaches it because he is hungry.


The tree has leaves.


He finds no fruit.


Then Mark adds:


“for the time of figs was not yet.”

— Mark 11:13


Jesus answers the tree:


“No man eat fruit of thee hereafter for ever.”

— Mark 11:14


The next morning:


“they saw the fig tree dried up from the roots.”

— Mark 11:20


At first glance the episode seems unfair.


Why curse a tree for lacking fruit when Mark himself says it was not the season?


That question has troubled interpreters for a very long time.



Look at what Mark puts in the middle


The fig-tree story is interrupted.


Jesus curses the tree.


Then he enters Jerusalem and acts against the commercial activity in the temple.


Then the narrative returns to the fig tree.


This literary arrangement—one story wrapped around another—is often called intercalation, or informally a “Markan sandwich.”


That structure strongly encourages the reader to interpret the tree and temple scenes together.


George Guthrie's study of Mark 11 argues that the fig tree and the temple action should be read in light of one another and places the passage against prophetic texts concerning judgment, exile, and restoration. Esther Miquel similarly emphasizes the literary relationship between the two scenes.


That makes a symbolic judgment interpretation quite plausible.


A leafy tree promises something that is not there.


The temple likewise appears alive with religious activity immediately before Jesus pronounces judgment upon what is occurring there.



But scholarship is not unanimous


A good research paper should not hide disagreement.


Philip Esler has challenged the standard symbolic-temple reading, arguing that Mark may have inherited the fig-tree story and that its final function may be more closely related to Jesus' subsequent teaching about faith and prayer.


So we should distinguish between two levels of certainty.


Certain: Mark deliberately narrates the fig tree, temple action, and withered tree in sequence.


Interpretive: Exactly what symbolic significance Mark intends the fig tree to carry.


The temple judgment reading has substantial literary support.


It remains an interpretation.



8. The Lake of Fire and the “Second Death”


Revelation 20 contains imagery that has shaped Christian thinking about final judgment for centuries.


At the great white throne, the dead are judged.


Then:


“And death and hell were cast into the lake of fire. This is the second death.”

— Revelation 20:14


The next verse says:


“And whosoever was not found written in the book of life was cast into the lake of fire.”

— Revelation 20:15


The phrase “second death” also appears elsewhere in Revelation, including Revelation 2:11 and 21:8.


Interestingly, it is Revelation itself—not later theology—that directly connects the “second death” with the lake of fire.


Scholar J. David Woodington notes that “second death” is distinctive language within Revelation and that the text explicitly equates it with the lake of fire.



“Hell” needs careful handling here


The KJV says:


“death and hell were cast into the lake of fire.”


The underlying term translated “hell” in Revelation 20:13–14 is Hades.


That creates an important distinction.


The lake of fire is not simply another name for the Hades from which the dead have just been delivered.


Death and Hades themselves are cast into it.


So language such as “after people leave hell they go to the second death” can become misleading unless the terminology is carefully defined.


Revelation presents a sequence in which the dead are raised, judgment occurs, Death and Hades surrender their dead, and then Death and Hades themselves are abolished in the lake of fire.



What does the imagery ultimately mean?


Here Christian interpretations divide.


Traditional eternal-conscious-punishment readings emphasize passages such as Revelation 20:10, where the devil, beast, and false prophet are described as tormented “day and night for ever and ever,” along with other New Testament judgment texts.


Conditionalist or annihilationist readings emphasize the terms death, destruction, and second death, arguing that the final fate of the wicked is ultimately death rather than endless conscious existence.


Other approaches emphasize the heavily symbolic and apocalyptic character of Revelation.


The text unquestionably uses severe final-judgment imagery.


What should not be done is to pretend that one phrase settles every later theological question without interpretation.


A scholarly study of Revelation 20:11–21:8 emphasizes the narrative progression: the dead are judged, Death and Hades are thrown into the lake, the lake is identified with the second death, and those absent from the book of life share that final judgment.



The strangest detail may be overlooked


Death dies.


John personifies Death and Hades as defeated powers.


Whatever one's theology of final punishment, Revelation's vision is not merely about God tormenting enemies.


It culminates in the abolition of death itself.


That prepares for the declaration in the following chapter:


“there shall be no more death.”


9. Melchizedek: The Man With No Recorded Beginning or End


Melchizedek appears suddenly in Genesis 14.


Abram has returned from battle when:


“Melchizedek king of Salem brought forth bread and wine: and he was the priest of the most high God.”

— Genesis 14:18


He blesses Abram.


Abram gives him tithes.


Then the Genesis narrative moves on.


Psalm 110 later makes the extraordinary declaration:


“Thou art a priest for ever after the order of Melchizedek.”

— Psalm 110:4


Hebrews develops that statement extensively in connection with Jesus Christ.


Then comes the line that has generated centuries of speculation:


“Without father, without mother, without descent, having neither beginning of days, nor end of life...”

— Hebrews 7:3


And yet Hebrews continues:


“but made like unto the Son of God.”


That final phrase deserves careful attention.


Melchizedek is described as being made like unto the Son of God.


Hebrews does not simply say:


Melchizedek was Jesus Christ.



Is Hebrews reasoning from Genesis' silence?


One influential scholarly explanation is that Hebrews is using a form of interpretation based upon what Genesis does not record.


Genesis provides no genealogy for Melchizedek.


No father.


No mother.


No birth.


No death.


No predecessor.


No successor.


That literary presentation allows Hebrews to use Melchizedek typologically in its argument about Christ's enduring priesthood.


Gard Granerød argues that Hebrews 7's additional claims about Melchizedek can be understood through precisely this kind of argument from scriptural silence.


That reading does not mean Melchizedek literally had no biological parents.


It means Genesis narratively presents him without genealogy.



But Melchizedek had already become mysterious before Hebrews


Second Temple Jewish literature demonstrates that Melchizedek attracted speculation before or around the emergence of Christianity.


The Dead Sea Scroll text commonly called 11QMelchizedek presents an exalted eschatological Melchizedek figure involved in liberation and divine judgment.


Even scholars disagree about exactly how the figure should be classified. Some describe him as an angelic or heavenly intermediary; others see more complex divine associations.


That historical evidence is valuable because it shows that Hebrews was not written in an intellectual world where Melchizedek was simply an obscure ancient king.


He had become the subject of serious theological reflection.



What can we conclude?


Genesis calls him king of Salem and priest of the most high God.


Psalm 110 speaks of an eternal priesthood “after the order of Melchizedek.”


Hebrews uses him to explain the priesthood of Christ.


That is explicit.


Whether Melchizedek himself was an ordinary ancient king, a uniquely appointed priest, an angelic being, or a pre-incarnate appearance of Christ belongs to interpretation.


And here the wording of Hebrews should restrain us.


Melchizedek is “made like unto the Son of God.”


Christ is not said to be made like Melchizedek in identity.


Rather, Melchizedek serves Hebrews' larger argument concerning Christ.


The mystery points beyond itself.



10. Ezekiel's Wheels Full of Eyes


Few chapters in the Bible have inspired more paintings, diagrams, mystical systems, and technological theories than Ezekiel 1.


The prophet sees a storm, fire, brightness, four living creatures, wings, faces, wheels, a firmament, a throne, and an overwhelming manifestation of divine glory.


The wheels are described:


“their appearance and their work was as it were a wheel in the middle of a wheel.”

— Ezekiel 1:16


Their rims are:


“full of eyes round about them four.”

— Ezekiel 1:18


Ezekiel 10 revisits the vision and makes an important identification.


The living creatures are cherubims.


The wheels and creatures move together, and the chapter repeatedly associates the entire vision with the departing glory of the LORD.



Did Ezekiel see a spacecraft?


That interpretation became particularly popular in modern technological culture.


It is easy to understand why.


Wheels.


Movement in every direction.


Fire.


Noise.


A radiant figure.


Something descending from the sky.


But interpretation should begin with Ezekiel's categories before replacing them with ours.


At the conclusion of chapter 1, Ezekiel says:


“This was the appearance of the likeness of the glory of the LORD.”


That is the narrator's own identification of what the vision means.


Whatever physical imagery contributes to the description, Ezekiel presents the event as a throne vision of divine glory.



The throne-chariot tradition


Scholars often describe the vision as a throne-chariot vision.


Dale Launderville's study connects Ezekiel's mobile throne imagery with older temple symbolism, particularly the cherubim associated with God's royal presence, while emphasizing the extraordinary mobility of the vision.


That mobility makes theological sense in Ezekiel's historical setting.


Ezekiel is among exiles.


Jerusalem and its temple stand far away.


A God whose throne can move in every direction cannot be contained by one earthly location.


Later Jewish traditions developed Ezekiel's vision extensively, eventually producing what is commonly called Merkabah or chariot mysticism. A recent study of Ezekiel's reception shows that later apocalyptic texts continued to elaborate the wheels, eyes, throne, living beings, and chariot imagery.



“Eyes” and modern reconstruction


We should also avoid assuming that the word “eyes” necessarily gives us a mechanical blueprint.


Eyes in visionary literature can suggest perception, awareness, watchfulness, animation, or simply visual features that Ezekiel experienced as eye-like.


The text calls them eyes.


That fact should be preserved.


But turning every eye into a camera sensor is no longer exegesis.


It is technological analogy.


The difference is important.



11. Behemoth, Leviathan, and the KJV “Unicorn”


The final group brings us into the Bible's strange zoology.


And it is here that readers often become most confident precisely where the evidence is least certain.



Behemoth


God tells Job:


“Behold now behemoth, which I made with thee; he eateth grass as an ox.”

— Job 40:15


The creature is enormously strong.


Its bones are compared to brass and iron.


It lies among reeds and marshland.


It is untroubled by a raging river.


And:


“He moveth his tail like a cedar.”

— Job 40:17


Readers have proposed the hippopotamus, elephant, dinosaur, extinct mammal, mythological monster, or a poetic creature assembled from recognizable animal features.


Modern biblical scholarship has often identified Behemoth with the hippopotamus, although the identification remains debated and does not account neatly for every feature of the poem.


A recent Oxford Handbook of Biblical Monsters discussion notes both the long history of the hippopotamus identification and the literary function of Behemoth as an overwhelming creature through which Job confronts the limits of human control.


That final point may be more important than getting the zoological label exactly right.


God's question is not:


“Job, can you correctly classify Behemoth?”


It is:


Can you master what I have made?



Leviathan


Then God turns to Leviathan.


“Canst thou draw out leviathan with an hook?”

— Job 41:1


The description grows increasingly fantastic.


Leviathan has terrifying teeth and tightly joined scales.


Smoke comes from its nostrils.


Its breath kindles coals.


Weapons are ineffective against it.


The creature is portrayed as beyond human domestication and control.


Across the Hebrew Bible, however, Leviathan is not portrayed exactly the same way in every passage.


Psalm 104 places Leviathan in the sea among God's creatures.


Isaiah 27 describes Leviathan with explicitly dragon- and serpent-like imagery in a judgment oracle.


Psalm 74 uses Leviathan in cosmic-victory imagery.


So the word participates in both zoological and mythopoetic worlds.


Scholars have variously connected the Job description with crocodiles, whales, large marine animals, and ancient Near Eastern chaos-monster traditions. Michael Fox argues that the identity and rhetorical role of Behemoth and Leviathan cannot simply be reduced to embodiments of evil and proposes a whale background for Leviathan in Job.


Other scholars give greater weight to mythic-chaos associations.


The debate itself is instructive.


The text does not provide a modern species label.



The KJV “unicorn”


Then we come to one of the most famous translation controversies.


Job asks:


“Will the unicorn be willing to serve thee, or abide by thy crib?”

— Job 39:9


The KJV uses unicorn in several passages for the Hebrew word commonly transliterated re'em.


Modern English readers naturally picture a horse-like creature with one horn.


That does not necessarily tell us what a seventeenth-century Bible translator—or an ancient Greek translator—imagined.


The translation has a long history.


The ancient Greek Septuagint rendered the Hebrew term with a Greek word meaning “one-horned,” and the Latin tradition also used terms that eventually influenced English “unicorn.”


Modern lexicographical traditions frequently identify re'em with a wild bovine, often the aurochs or wild ox. The older International Standard Bible Encyclopedia, for example, discusses the KJV “unicorn” under the Hebrew re'em and notes the later “wild ox” rendering.


There is also a significant ancient linguistic connection between Hebrew re'em and Akkadian rīmu, a term used of a powerful wild bovine or aurochs.


Another clue comes from the Bible itself.


Deuteronomy 33:17 speaks of the animal's horns in the plural.


Job 39 portrays it as immensely strong, undomesticated, and unwilling to perform the agricultural work of a domestic ox.


That profile fits a large wild bovine better than the modern fairy-tale unicorn.



But note what we are—and are not—saying


The KJV says unicorn.


That is a fact about the English translation.


The Hebrew says re'em.


Determining the zoological referent of re'em is a historical-linguistic question.


Those statements are not contradictory.


A serious KJV study does not need to pretend that “unicorn” has always meant exactly what a child's fantasy book means by it today.


Nor does acknowledging the Hebrew term somehow erase the KJV wording.


Translation history is part of Bible study.



What These Eleven Passages Have in Common


At first these stories appear almost random.


Priestly objects.


Talking animals.


Royal judgment.


Dietary laws.


Divine appearances.


A disputed Gospel passage.


A cursed tree.


Apocalyptic fire.


A mysterious priest.


Living wheels.


Monsters.


But several patterns begin to emerge.


One is the limit of human perception.


Balaam cannot see the angel.


Job cannot master Behemoth or Leviathan.


Moses cannot endure unrestricted sight of God.


Ezekiel repeatedly reaches for phrases such as “appearance” and “likeness” because the vision strains ordinary description.


Another pattern is judgment.


Belshazzar is weighed.


The fig tree withers.


Revelation's dead stand before the great white throne.


The mysterious Urim participates in judgment.


Another is mediated revelation.


Priests inquire before God.


Moses receives only what God permits him to see.


Daniel must interpret the writing.


John receives a vision.


Ezekiel sees symbols.


Hebrews interprets Melchizedek through earlier Scripture.


And finally there is a repeated warning about human control.


Human beings do not control revelation.


They do not control God.


They do not control Leviathan.


They do not control the timing of judgment.


They do not even always control the meaning of the texts they inherit.


The Bible's strange passages repeatedly place the reader in the position of Job:


You are being shown something.


But you are not being shown everything.



Things the Bible Never Tells Us


Some questions remain unresolved not because scholars have failed to try hard enough, but because the biblical text never supplies the information.


We do not know what the Urim and Thummim looked like.


We do not know what Jesus wrote on the ground.


We do not know precisely what Moses perceived when he saw what the KJV calls God's “back parts.”


We do not know the original rationale for the prohibition against cooking a kid in its mother's milk.


We do not know with certainty which modern species, if any, should be identified with every detail of Behemoth and Leviathan.


We do not possess Ezekiel's drawing of the wheels.


We do not have Melchizedek's genealogy.


That last example is almost humorous in its appropriateness.


The absence of Melchizedek's genealogy becomes part of Hebrews' argument.


Sometimes what Scripture does not tell us matters.



Common Claim vs. What the Text Actually Establishes

Common claim

What can actually be established

The Urim and Thummim were magical gemstones that lit up to spell answers.

Scripture associates them with priestly judgment but never explains the mechanism.

David definitely used the Urim and Thummim every time he consulted the ephod.

The association is plausible; not every narrative explicitly names them.

Balaam is purely fictional.

An independent Iron Age inscription refers to a Balaam son of Beor as a seer, although it does not verify the biblical events.

Archaeology proved Daniel 5 exactly as written.

Cuneiform evidence independently confirms Belshazzar as an important Babylonian royal figure, not the supernatural event.

Archaeology proved that pagans boiled goats in milk as a fertility ritual.

The often-cited Ugaritic evidence does not securely establish that claim.

Moses literally saw God's human-shaped back.

Exodus uses bodily language, but the precise nature of the manifestation is not explained.

Jesus simply overturned Moses' adultery law in John 8.

The legal situation is already irregular, the passage presents a trap, and Jesus ends by calling the conduct sin.

No manuscript problem exists in John 7:53–8:11.

The story has a complicated textual history and is absent from many early Greek witnesses.

The fig tree was simply punished for failing to produce fruit.

Mark deliberately places the temple action between the two halves of the fig-tree episode, strongly inviting symbolic interpretation.

“Second death” simply means the same thing as Hades/hell.

Revelation depicts Death and Hades themselves being thrown into the lake of fire, which it calls the second death.

Hebrews explicitly says Melchizedek was Jesus.

Hebrews says Melchizedek was “made like unto the Son of God.”

Ezekiel says he saw a spacecraft.

Ezekiel identifies the vision as the appearance of the likeness of the glory of the LORD.

The KJV “unicorn” proves Scripture describes a modern fantasy unicorn.

“Unicorn” translates Hebrew re'em, whose ancient linguistic and contextual associations point toward a powerful wild bovine.


Why Strange Passages Attract Strange Explanations


There is a recurring pattern in popular Bible interpretation.


A biblical text leaves an unexplained detail.


The reader feels the discomfort of uncertainty.


An explanation appears.


The explanation fits several features.


The explanation becomes memorable.


Eventually the explanation is repeated without the words “perhaps,” “possibly,” or “one interpretation is.”


Then, after enough repetition, people remember the explanation as though it had been in the verse.


Psychology can help us understand this process without telling us whether any particular theological claim is true.


Need-for-closure research shows that ambiguity can increase the desire for a stable answer, while a strong desire for closure can reduce the amount of further information a person consults.


Biblical interpretation therefore benefits from deliberately slowing down.


Ask:


Where exactly does the verse say that?


Is this statement from the biblical text?


Is it historical evidence?


Is it a translation decision?


Is it a scholarly reconstruction?


Is it church tradition?


Is it a modern theory?


Is it simply possible?


Those questions do not destroy faith.


They destroy category confusion.



Seven More Strange Passages Worth Studying


The number eleven is useful for this paper, but Scripture certainly does not stop being strange here.


Genesis 6:1–4 — The Sons of God and the Nephilim


The “sons of God” take wives from the “daughters of men,” and the passage mentions “giants” in the KJV. Interpretations include heavenly beings, royal rulers, descendants of Seth, or other ancient categories. The expression “sons of God” elsewhere in the Hebrew Bible can refer to heavenly beings, which is why the supernatural reading has significant historical support.


1 Samuel 28 — Saul and the Woman at Endor


Saul, unable to receive an answer through dreams, prophets, or Urim, seeks a woman with a familiar spirit and asks for Samuel to be brought up. The passage raises difficult questions because the figure speaks as Samuel and predicts Saul's death.


2 Kings 2:23–25 — Elisha and the Bears


Young people mock Elisha, he curses them in the name of the LORD, and two she-bears come from the wood and tear forty-two of them. The text is short enough that almost every attempt to reconstruct their age, motives, injuries, or social setting necessarily goes beyond what the passage explicitly states.


2 Kings 6:1–7 — The Floating Axe Head


A borrowed iron axe head falls into water. Elisha cuts a stick, casts it into the water, and “the iron did swim.”


No explanation is supplied.


Isaiah 20 — Isaiah Walks Naked and Barefoot


God commands Isaiah to remove his sackcloth and footwear, and the prophet becomes a living sign concerning Egypt and Ethiopia. The prophetic message is not merely spoken; Isaiah's own body becomes part of the prophecy.


Ezekiel 4 — Ezekiel's Enacted Siege


Ezekiel constructs a model of Jerusalem, lies on his side for extended periods, weighs his food, measures his water, and cooks under conditions deliberately intended to symbolize coming judgment.


Biblical prophecy can be theatrical.


Matthew 27:52–53 — Saints Rise After Jesus' Resurrection


Matthew says graves were opened, many bodies of saints arose, entered the holy city after Christ's resurrection, and appeared to many.


The Gospel provides no names, no later biographies, and no explanation of what happened to them afterward.


It is one of the New Testament's briefest and strangest resurrection notices.



Research Summary

Passage

Strange element

What Scripture explicitly says

Historical / scholarly context

What remains uncertain

Exodus 28; Numbers 27; 1 Samuel

Urim and Thummim

Priestly means of judgment/inquiry

Comparable to sacred divinatory procedures; mechanism lost

Physical form and exact operation

Numbers 22

Talking donkey

The LORD opens the donkey's mouth and Balaam's eyes

Deir ‘Alla independently attests Balaam son of Beor as a seer

Historicity of the miracle cannot be tested archaeologically

Daniel 5

Writing hand

Divine judgment announced against Belshazzar

Cuneiform records attest Belshazzar as Nabonidus's son and royal figure

The supernatural event is outside ordinary historical verification

Exodus 23; 34; Deuteronomy 14

Kid in mother's milk

The practice is prohibited

Many explanations proposed; supposed Canaanite ritual evidence is uncertain

Original rationale

Exodus 33

God's face/back

Moses receives limited manifestation of glory

Extensive debate concerning biblical anthropomorphism

What Moses visually experienced

John 7:53–8:11

Woman taken in adultery

Jesus frustrates a trap, refuses condemnation, commands no more sin

Complicated manuscript history

Original textual location and what Jesus wrote

Mark 11

Fig tree

Jesus curses it; it withers; temple action sits between

Strong literary case for symbolic relation to temple, but alternatives exist

Full significance of “not the season”

Revelation 20–21

Second death

Lake of fire identified as second death

Major debate over nature of final punishment

How apocalyptic imagery corresponds to final reality

Genesis 14; Psalm 110; Hebrews 7

Melchizedek

King-priest used as pattern for Christ's priesthood

Second Temple Judaism also developed exalted Melchizedek traditions

His complete historical identity

Ezekiel 1; 10

Wheels full of eyes

Throne vision associated with divine glory and cherubim

Connected with temple/throne imagery and later Merkabah tradition

Precise visualization of wheels and eyes

Job 39–41

Unicorn, Behemoth, Leviathan

Powerful, untamable creatures under God's rule

Linguistic, zoological, and mythopoetic interpretations vary

Exact identification of several creatures


The Larger Lesson: Strange Does Not Mean Meaningless


One of the easiest mistakes to make when reading unusual biblical passages is to assume that the mysterious detail must be the main point.


Often it is not.


The donkey is remarkable.


But Numbers is interested in Balaam's blindness and God's control of revelation.


The handwriting is spectacular.


But Daniel is interested in pride and judgment.


The wheels are unforgettable.


But Ezekiel tells us that he is seeing the glory of the LORD.


Leviathan is terrifying.


But God asks Job who can control him.


Melchizedek is mysterious.


But Hebrews is interested in Jesus Christ.


The lake of fire is terrifying.


But Revelation proceeds into a world where death itself is gone.


The strange detail attracts us to the passage.


The surrounding Scripture tells us where to look after we arrive.



Scripture, History, Interpretation—and Humility


Historical research can genuinely illuminate the Bible.


The Deir ‘Alla inscription tells us something important about the ancient memory of Balaam.


Babylonian records demonstrate that Belshazzar was a real royal figure.


Ancient-language study helps explain how the Hebrew re'em became the KJV “unicorn.”


Manuscript research forces us to deal honestly with the textual history of John 7:53–8:11.


Literary analysis helps us notice that Mark deliberately wraps the temple incident inside the fig-tree story.


Second Temple texts show that Melchizedek was already the subject of speculation beyond Genesis.


None of those discoveries makes interpretation unnecessary.


They make better interpretation possible.


At the same time, historical scholarship has limits.


Archaeology cannot excavate Balaam's donkey speaking.


A cuneiform tablet cannot measure Moses' experience of divine glory.


Textual criticism cannot tell us what Jesus wrote in the dust when no surviving text tells us.


Psychology cannot decide whether Ezekiel actually saw a supernatural vision.


Those questions belong to different domains.


Confusing the domains creates bad arguments in both directions.


Faith should not be disguised as archaeology.


And archaeology should not be asked to answer theological questions it cannot answer.



Conclusion: Let the Mystery Remain Where Scripture Leaves It


The Bible's strangest passages reward careful reading because they force us to confront the difference between curiosity and knowledge.


Curiosity asks:


What were the Urim and Thummim really?


What species was Leviathan?


What did Jesus write?


Was Melchizedek secretly somebody else?


Were Ezekiel's wheels machinery?


What exactly did Moses see?


Knowledge asks a second question:


What evidence do we actually have?


Sometimes the answer is more than we expected.


An ancient inscription really does mention Balaam son of Beor.


Babylonian records really do mention Belshazzar.


The literary structure of Mark really does connect the fig tree with the temple.


The manuscript history of John 8 really is complicated.


At other times the evidence simply ends.


And when it ends, our certainty should end with it.


That principle is particularly appropriate for a study of Scripture.


The King James translators themselves warned against excessive certainty where the underlying text presented genuine difficulty. In The Translators to the Reader, they defended marginal alternatives in difficult passages and wrote that where matters remained uncertain, modesty was preferable to dogmatism. They even quoted the principle:


“It is better to make doubt of those things which are secret, than to strive about those things that are uncertain.”


That is a remarkably useful rule for strange Bible passages.


Read closely.


Compare Scripture with Scripture.


Study the history.


Examine the languages.


Consult archaeology where archaeology can speak.


Take manuscript evidence seriously.


Listen to competing interpretations.


Recognize the mind's desire to turn uncertainty into certainty.


And then make one final distinction:


Where Scripture speaks clearly, let it speak clearly.


Where interpretation is strong, call it interpretation.


Where evidence is uncertain, say so.


And where Scripture leaves a mystery unresolved, do not make speculation speak with the authority of revelation.


“Prove all things; hold fast that which is good.”

— 1 Thessalonians 5:21


External Sources and Further Research

Subject

External source

Urim and Thummim

Encyclopedia of the Bible — Urim and Thummim

Priesthood and divination

Korean Journal of Old Testament Studies — Urim, Thummim, Ephod and Ark

Balaam and Deir ‘Alla

JSTOR — Baruch Levine studies of the Deir ‘Alla inscriptions

Belshazzar

British Museum — Nabonidus cylinder naming Belshazzar

Milk-and-meat prohibition

TheTorah.com — Prohibition of Meat and Milk: Its Origins in the Text

Exodus 33 and God's face

Scandinavian Journal of the Old Testament — The Face of God

Divine anthropomorphism

JSTOR — Forming God: Divine Anthropomorphism in the Pentateuch

John 7:53–8:11 textual history

SAGE — Recent and Previous Research on the Pericope Adulterae

John 7:53–8:11 manuscript evidence

NET Bible — John 7:53–8:11 textual note

Fig tree and temple

Cambridge University Press — The Tree and the Temple

Alternative fig-tree interpretation

SAGE — The Incident of the Withered Fig Tree in Mark 11

Second death

SAGE — Crafting the Eschaton: The Second Death and the Lake of Fire

Melchizedek and Hebrews

Biblica — Melchizedek in Hebrews 7

Melchizedek at Qumran

SAGE — Michael or YHWH? Identifying Melchizedek in 11Q13

Ezekiel's throne vision

Catholic Biblical Quarterly archive — Ezekiel's Throne-Chariot Vision

Ezekiel's later reception

SAGE — Reception of Ezekiel's Throne Vision

Behemoth

Oxford Academic — Behemoth, Oxford Handbook of Biblical Monsters

Behemoth and Leviathan

Biblica — Michael V. Fox, Behemoth and Leviathan

KJV “unicorn” / re'em

NET Bible Dictionary — Wild Ox / re'em

Psychology of interpretive closure

PubMed — Kruglanski & Webster, Motivated Closing of the Mind

Ambiguity and information seeking

Social Cognition — Effects of Ambiguity and Need for Closure



LIBRARY OF RICKANDRIA
SCRIPTURE BREAKDOWN BY VCG
SEPTEMBER 2026


4CHAN THREAD & POST BREAKDOWNS – Library of Rickandria


VCG PAPER PROJECTS – Library of Rickandria


11 of the Strangest Passages in the Bible — and What They Actually Say


11 of the Strangest Passages in the Bible — and What They Actually Say – Library of Rickandria