The Bible Code

From RationalWiki
(Redirected from Bible Code)
Jump to navigation Jump to search
Light iron-age reading
The Bible
Icon bible.svg
Gabbin' with God
When my critics find a message about the assassination of a prime minister encrypted in Moby Dick, I'll believe them.
—(They did. He didn't.) Michael Drosnin. Newsweek, Jun 9, 1997

The Bible Code is a 1997 book by Michael Drosnin. The concept of Bible codes, also known as Torah Codes, is based on the idea that hidden messages are contained in sacred texts.

The Bible Code method[edit]

Australian atheist entertainer John Safran proving conclusively beyond a shadow of a doubt that Vanilla Ice was involved in the U.S. World Trade Center attacks by utilizing Drosnin's scientific methods.

To extract this code requires a would-be code-seeker to count every nth character (where n is a non-zero integer[note 1]) in a text until you run across a sequence that contains a specified keyword. This particular technique is known as the Equidistant Letter Sequence (ELS) formula. The ELS formula has been likened to arranging the letters of the document into a grid n characters wide, and then treating them like the "word search" puzzles seen in newspapers, circling vertical words as they are discovered. When presented, many of the codes are shown in such a grid, with the necessary words interlinking, crossing each other, or pointing to each other.

Its proponents insist that, if the original text in its original language is used, the words so discovered constitute a "hidden message" that was planted in the text by its authors (and, by extension, a hidden message from God if the work is supposed to be divinely inspired). The original language of the Torah is biblical Hebrew. Biblical Hebrew uses an abjadWikipedia style alphabet, which means that every character is a consonant.[note 2] The reader must fill in the appropriate vowel sounds based on context and tradition. The name "Sarah", for instance, is spelled with only the Hebrew-alphabet equivalents of S, R, and H. This makes finding words somewhat easier than in a language that requires vowels by reducing the size of the word being looked for and increasing the odds of it being found randomly. For example, if I wanted to show that the Torah predicted the Holocaust by finding an ELS containing the name "Hitler", I would only need to search for "HTLR".[note 3]

In 2002, Drosnin predicted atomic holocaust due to war in Palestine in 2006. [1] After clearly failing, in 2007 he wrote another book claiming that Al-Qaeda has nuclear capacity and it can strike in 2011. [2] In 2011, Osama bin Laden was killed without any revenge nuclear attack.

Preposterous woo in its purest form[edit]

This is, of course, pure woo on the same level as uncovering backward masking in rock songs or retroactively applying the prophecies of Nostradamus to recent events. Drosnin claims to have applied the algorithm to War and Peace and found nothing, but some have since applied the same computer algorithm to find hidden codes in other books such as Moby Dick,[3] The Lord of The Rings series, and the lyrics of Vanilla Ice.[4] Naturally, prophecies, codes, and other secrets were also discovered in these non-religious texts. Beyond the fact that practically any sequence of words can be found in a sufficiently long text such as the Bible, the problem is that no "prophetic" sequence of words has ever been discovered until after the events foretold have transpired. In these cases, none of the prophecies can be said to have predictive value, but rather retroactively shoehorned.

Recently, Drosnin has shied away from using it predictively. However, he has stopped short of publicly admitting that it's a proven statistical certainty that if you look in the right way, you can find anything in anything.[5]

I don't think the code makes predictions. I think it reveals probabilities. so I can't say what will happen in the next five years. also it is not a crystal ball – you can't just ask the Bible to tell you about tomorrow or next year. You can only find what you know how to look for – you must have some idea of what you're looking for.

Nonetheless, the book was a best seller, and Michael Drosnin has so far managed to milk the material for no fewer than two sequels and many TV documentaries (although most now are made to refute the "code"). In the best example of "retroactive prophecy shoehorning", The Bible Code (published in 1997) did not "predict" the September 11th terrorist attacks on the World Trade Center, while The Bible Code 2 (published in 2002) did.[note 4] Must be because you need to "have some idea of what you're looking for", clearly.

Insane codes found by Bible Code Wisdom in the English translation of the Bible[edit]

Was Jesus jewish and did he have the ark of the covenant?

Could aliens and UFO's be in the bible?

Do skeptics think the antichrist is a myth?
—Bible Code Wisdom, just asking questions[6]

"Bible Code Wisdom" was a webshite that provided an online Bible code search function using a magic "ELS decoder grid." The site claimed that insight on virtually any subject could be found in the Bible by using its software. Analysis of this bullshit reveals several interesting results:

Alas, the site's "ELS decoder grid" almost certainly predicted its own demise, as it dropped off the internet in April 2018 and was replaced by a spam farm.

See also[edit]

External links[edit]


  1. Obviously, because counting every 2-and-a-halfth letter is kinda difficult.
  2. Some can also indicate vowels, especially long vowels. (See the Wikipedia article on Matres lectionis.) But no such context exists when characters are plucked independently from the text.
  3. It also helps that the Hebrew script has two characters that can be transliterated as 'T' (Taw ת and Teth ט) and two characters that can be transliterated as H (He ה and Heth ח).
  4. Although Moby Dick "predicted" it as well - see Moby Dick predicted the "War on Terrorism".