What do you think?
Rate this book
The Bible Code #3
Bible Code III: Saving the World
The final predictions of the bestselling Bible Code series.
Saving the Word is the focus of this riveting new book about the Bible Code, a miracle proven real by modern science. For 3000 years a code in the Bible remained hidden. Now it has been unlocked by computer and may reveal our future. The code was broken by a world-famous Israeli mathematician, and then confirmed by a senior code-breaker at the top secret U.S. National Security Agency. And it keeps coming true.
Saving the Word is the focus of this riveting new book about the Bible Code, a miracle proven real by modern science. For 3000 years a code in the Bible remained hidden. Now it has been unlocked by computer and may reveal our future. The code was broken by a world-famous Israeli mathematician, and then confirmed by a senior code-breaker at the top secret U.S. National Security Agency. And it keeps coming true.
232 pages, Hardcover
First published October 1, 2010
6 people are currently reading
268 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 11 of 11 reviews
October 10, 2018
I’ve read all three and this was by far the worst. In the second book he’s talking about aliens encoding the Bible, because obviously there’s no God. In this book he actually refers to Obama as the Messiah and the savior of the world. It’s all BS. He brings up a code key in book two, doesn’t mention it again until the end of book three, and still doesn’t have it (because it’s in Jordan where he can’t get permission to dig.) it’s all hypothetical until he can get the proof there really is a key in an iron ark buried in Lisan. Don’t waste your money, nothing gets resolved in this 8 year old book. It’s basically unfinished and leaves the reader with frustration because he doesn’t follow up to let the reader know if any government actually acted on the Yemen base. But somehow Obama saved the world (yeah right!)
February 27, 2011
Drosnin steps out further, and translates readings and predictions for the future. His results are very thought proving and earthshattering. Well written, it is an fast snooth read. I thought the book was a little short...guess I just wanted more. I highly recommend! In my opinion it is by far the best of the series. Whether you believe in Bible Codes or not it is a fascinating read.
May 13, 2023
This is actually a review for all three volumes, since many of the comments apply equally well.
(1) Volume 1, p. 42: "Does the Bible code [...] present all the probabilities?" Drosnin found "Al Gore" crossing with the title "President" (page 188 of Volume 2). But then he went back and found "President Bush" crossed with "The Second".
It's like the short story "The Library of Babel" by Jorge Luis Borges, which centers around a library that has all possible books in it, and proves to be equally useless, because all outcomes are predicted; there's no indication that any of them is more likely.
Drosnin repeats this idea on page 102 of Volume 1: "The sealed book might hold all of our possible futures." Sentiments like this pop up throughout the book, but Drosnin doesn't appear to stop and realize that he's actually undermining his case. Another example is page 63 of Volume 3: "It reveals probabilities, nothing is set in stone."
Once we recognize that we can decide our future (which is what he says the Bible code is all about, on page xi of Volume 3), then the Bible code itself doesn't really matter. Once again, he doesn't realize that this undermines his case.
(2) Drosnin places great emphasis on words or phrases that cross each other. However, a good deal of the time, one of these is actual text from the Torah. In that case, you're only looking for a word or name or phrase that crosses that text and is vaguely relevant. This is not as improbable as is suspected. This is especially true of the "Pisgah" look-up described on page 63 of Volume 1.
(3) In books that make predictions, it's always a good exercise to go back and see how close the predictions (which had not yet then come true) were.
Volume 1, page 74: "If I were going only by the Bible code, I would have to say that Netanyahu, if elected, will not live out his term of office." Spoiler alert: Netanyahu is alive (as of me writing this review).
Volume 3, page 91: Drosnin notes that 2011, "New York", and "atomic" all appear next to each other. Unless I missed it, New York did not get nuked in 2011.
(4) The Bible code requires you to search for particular names, and only then do the correlations pop up. This is why so many hits for WWII appear on page 105 of Volume 1.
On page 202 of Volume 3, he talks about the 2012 election, saying "We must know the names of all the candidates to do a real search in the code." Well, there's a few names you could probably guess at. And I wonder what the Bible code says about Biden vs. Trump in 2024. (Since Biden already beat Trump once, Drosnin will probably weasel out by saying that that result had "contaminated" the possibility of finding out.)
(5) Drosnin doesn't remember his history. On page 111 of Volume 1, he points out that R. F. Kennedy's name appears close to the phrase "second ruler will be killed" [which is also plaintext in the Torah]. Spoiler: RFK never got to be President.
If someone predicts something that turns out not to happen, that makes them a false prophet. And the Bible itself doesn't have anything good to say about false prophets.
(6) Even the "facts" recovered from the Bible code are ambiguous. Page 138, Volume 1: "It is not clear if the code is stating a series of disasters, or a series of delays."
(7) A "string" of Hebrew letters can have more than one interpretation: On page 76 of Volume 2, Drosnin says that Lisan is a place name but also means "language". Once again, this multiplies the chances of a meaningful intersection.
(8) Drosnin asks (page 213, Volume 2): "Was it possible that the Bible was being encoded in real time?" That would imply that the Torah's text is changing. OTOH, it would justify the non-sequitur on page 36 of Volume 3. ("How can 'atomic' possibly be written in Hebrew?" "Israel has nuclear weapons.")
(9) Page 276 of Volume 2: Robert Aumann commented: "If McKay had counterfeited a hundred-dollar bill, that would not prove that all money was fake. It would only prove that McKay was a counterfeiter." (McKay found other crossing phrases in _War In Peace_.) Aumann has clearly missed the point. What McKay did was not proving that all money was fake, but that some money can be faked. And that includes the $100 (metaphorically, most likely) in your pocket.
Another non-sequitur is uttered by Eli Rips, the mathematician who discovered the Bible code: "I have only one reason to believe the world will survive. God's promise [...] after the Flood never to destroy the world again." (page 134, Volume 3). As he later notes, the promise was only to not destroy the world *with a flood*; all other possibilities are on the table.
(1) Volume 1, p. 42: "Does the Bible code [...] present all the probabilities?" Drosnin found "Al Gore" crossing with the title "President" (page 188 of Volume 2). But then he went back and found "President Bush" crossed with "The Second".
It's like the short story "The Library of Babel" by Jorge Luis Borges, which centers around a library that has all possible books in it, and proves to be equally useless, because all outcomes are predicted; there's no indication that any of them is more likely.
Drosnin repeats this idea on page 102 of Volume 1: "The sealed book might hold all of our possible futures." Sentiments like this pop up throughout the book, but Drosnin doesn't appear to stop and realize that he's actually undermining his case. Another example is page 63 of Volume 3: "It reveals probabilities, nothing is set in stone."
Once we recognize that we can decide our future (which is what he says the Bible code is all about, on page xi of Volume 3), then the Bible code itself doesn't really matter. Once again, he doesn't realize that this undermines his case.
(2) Drosnin places great emphasis on words or phrases that cross each other. However, a good deal of the time, one of these is actual text from the Torah. In that case, you're only looking for a word or name or phrase that crosses that text and is vaguely relevant. This is not as improbable as is suspected. This is especially true of the "Pisgah" look-up described on page 63 of Volume 1.
(3) In books that make predictions, it's always a good exercise to go back and see how close the predictions (which had not yet then come true) were.
Volume 1, page 74: "If I were going only by the Bible code, I would have to say that Netanyahu, if elected, will not live out his term of office." Spoiler alert: Netanyahu is alive (as of me writing this review).
Volume 3, page 91: Drosnin notes that 2011, "New York", and "atomic" all appear next to each other. Unless I missed it, New York did not get nuked in 2011.
(4) The Bible code requires you to search for particular names, and only then do the correlations pop up. This is why so many hits for WWII appear on page 105 of Volume 1.
On page 202 of Volume 3, he talks about the 2012 election, saying "We must know the names of all the candidates to do a real search in the code." Well, there's a few names you could probably guess at. And I wonder what the Bible code says about Biden vs. Trump in 2024. (Since Biden already beat Trump once, Drosnin will probably weasel out by saying that that result had "contaminated" the possibility of finding out.)
(5) Drosnin doesn't remember his history. On page 111 of Volume 1, he points out that R. F. Kennedy's name appears close to the phrase "second ruler will be killed" [which is also plaintext in the Torah]. Spoiler: RFK never got to be President.
If someone predicts something that turns out not to happen, that makes them a false prophet. And the Bible itself doesn't have anything good to say about false prophets.
(6) Even the "facts" recovered from the Bible code are ambiguous. Page 138, Volume 1: "It is not clear if the code is stating a series of disasters, or a series of delays."
(7) A "string" of Hebrew letters can have more than one interpretation: On page 76 of Volume 2, Drosnin says that Lisan is a place name but also means "language". Once again, this multiplies the chances of a meaningful intersection.
(8) Drosnin asks (page 213, Volume 2): "Was it possible that the Bible was being encoded in real time?" That would imply that the Torah's text is changing. OTOH, it would justify the non-sequitur on page 36 of Volume 3. ("How can 'atomic' possibly be written in Hebrew?" "Israel has nuclear weapons.")
(9) Page 276 of Volume 2: Robert Aumann commented: "If McKay had counterfeited a hundred-dollar bill, that would not prove that all money was fake. It would only prove that McKay was a counterfeiter." (McKay found other crossing phrases in _War In Peace_.) Aumann has clearly missed the point. What McKay did was not proving that all money was fake, but that some money can be faked. And that includes the $100 (metaphorically, most likely) in your pocket.
Another non-sequitur is uttered by Eli Rips, the mathematician who discovered the Bible code: "I have only one reason to believe the world will survive. God's promise [...] after the Flood never to destroy the world again." (page 134, Volume 3). As he later notes, the promise was only to not destroy the world *with a flood*; all other possibilities are on the table.
February 13, 2021
Je suis rentrée en une journée dans une épopée surréaliste, autour de la Bible. Ce livre au-delà d'un jeu de code s'apparente surtout pour moi à une revue de notre monde contemporain. Un monde qui va à vau l'eau et qui semble devenir hautement incontrôlable.
Bien écrit dans tous les cas.
Bien écrit dans tous les cas.
July 12, 2018
Pure Crap.
December 29, 2015
This is the worst of the Bible Code books because the author tries too hard to predict the future. Furthermore, hindsight has proved that MOST of Drosnin's predictions, based on the code, were completely wrong. He was WAAAAY off! It's a shame that Drosnin makes this book so much about his own interpretations, because there really is a code in the Bible (this fact has been verified by mathematicians, professional codebreakers, and scientists). The main thing that Drosnin needs to realize is that no one has figured out how to read the code accurately, so predictions are hit and miss (mostly miss). Of course, when you use the code to verify events that have already occurred there is no problem. Drosnin's other weakness is that he doesn't understand the nature of Biblical prophecy. Drosnin claims that prophecies tell of possible futures that might not occur if people make different choices. This is not the case. The key to understanding Biblical prophecy is to realize that most prophecies are narrative descriptions of what will happen no matter what. The only exceptions are prophecies that specifically use "if-then" statements. Otherwise, a prophecy always comes true and cannot be changed by human beings.
October 2, 2008
I read the book a long long time ago I was just interested because a friend said I should read it but I didn't actually like it up to the end. Maybe because I was skeptical about the contents and have my own opinions regarding the matter...about the signs of the bible and the end of the world. For some people they might be interested in knowing how the world will end and how the past is showing us the signs. It tells that if you look carefully in the bible there are a lot of hidden codes that can predict what will happen in the future. But as a non-believer i think it's full of S*#$! to believe in those kind of predictions. Well i may offend those who believe but i am entitled to my own opinion.
I believe in the God, but not everything that is written in the bible. I have my own mind to believe whatever it is I want to believe in. For me everything happens for a reason codes doesn't have to do with it.
I believe in the God, but not everything that is written in the bible. I have my own mind to believe whatever it is I want to believe in. For me everything happens for a reason codes doesn't have to do with it.
November 8, 2011
Third in the Bible Code series, predicts Obama as either good guy or caude of World War 3. Interesting, but not much meat.
March 28, 2012
read it in 3 hours.
October 3, 2012
I read this book several years ago. I found the topics interesting. I still was not quite sure about the code and how it is found. Fairly convincing though.
A decent read.
A decent read.
March 19, 2009
Bunk!
Displaying 1 - 11 of 11 reviews