Shopping Cart
Your Cart is Empty
There was an error with PayPalClick here to try again
CelebrateThank you for your business!You should be receiving an order confirmation from Paypal shortly.Exit Shopping Cart


Torah & Bible Codes



view:  full / summary

The US Presidential Election 2008

Posted by Rabbi Matityahu Glazerson on January 6, 2011 at 5:40 PM

On November 4, 2008 the people of the United States will elect a president. The choice is Barack Hussein Obama or John McCain. The election is a particularly important election because of the global economic meltdown, the stock market crash, and the potential blowup of the mideast conflict. The next president will be burdened with one crisis after another. Problem solving strategies that were successful in the past will no longer work. Strength and having the right set of values will be most important.


One of two possible events will occur on November 4, 2008. Either Obama will be elected president or McCain will be elected president. Since there are only two possible events, we decided to put the same systematic and consistent effort to explore in Torah codes the possible event of Obama becoming president and the possible event of McCain becoming president. Our exploration is not in terms of a single table, but in terms of multiple coordinated tables, a network of tables. This kind of exploration has been done implicityl and incompletely with other historical events on which we have worked. These prior studies can be found on this website.


One of the events we explore will happen; one will not. We would like to understand what is the pattern in the coordinated Torah code tables that distinguish those tables associated with an event that happens from a potential event that does not happen. Our exploration, as it proceeds, will be publicly documented on our websites. We will be examining test statistics that measure the relatedness of networks of Torah code tables. Technical discussions of our research, as they are completed, will be found in our website under 'Science Behind The Codes' section. Sets of tables identified to be statistically significant networks of related tables will be shown on this website.


The Structure Of An Event


We begin by explaining the structure of an event and how it relates to a methodology for discovering Torah code tables related to an event.

A systematic Torah code exploration must proceed with some understanding of what are the components of an event and how these components relate to the Torah code exploration methodology.


In general, an event has a topic and who, what, where, when, and how components. The topic component usually coincides with one or more of the who, what, where when and how components. Each simple table is constructed using one or more key words from the topic component combined with one or more key words from one of the who, what, where, when, and how components not involved in the topic. More complex tables are constructed using key words from the topic component combined with key words from more than one of the who, what, where, when and how components.

To decide for any particular event exactly what these components are requires subjective choice, choices sometimes not even fully consciously recognized by the experimenter. Here we will be as complete and explicit about our a priori choices as possible.


The what component of this event is President. The where component of this event is the United States. The when component of this event is November 4, 2008. The when component has a subcomponent as the date, November 4, and a subcomponent as the year, 2008. The how component of an is the enabling means or instrument through which the event happens. For this event the means is being elected. For the Obama event the who component is Obama. For the McCain event the who component is McCain. We choose the topic component to be the who component and the what component.


This give us a structure by which to explore tables associated with these two possible events. Each table must have the key words of the topic: Who and what. Therefore, for this event we can construct the 15 possible categories of tables. These are listed in the table below. We will explore all 15 categories of tables. Each of these categories will have some key word set combination yielding a best table. That best table will have a p-value. It is this p-value that we will record.



Mumbai Coincidence

Posted by Rabbi Matityahu Glazerson on January 6, 2011 at 2:36 PM

The place where the Torah scroll was ripped is exactly the same pleace the code was found! Is this just coincidence?! To see it more clearly look at the illustrated table below!


As the terror event was unfolding in Mumbai the following table was discovered.


The( green) word that is found is the place BOMBAY as it was called for around 30 years before it was renamed MOMBAI. The red letters spell terror backwards. The dark grey letters(and one green letter above it) spell "in the house of chabbad". Just above the green letter are two other letters in hebrew speliing Rav.


The sentence in the Torah which one can see starts in the letter ר in the words of the sentence "רב בית חבד" meaning " Rabbi of the house of Chabad".

The place in the Torah where it was found is the book "VAYiKRA",portion ACHAREY,chapter 16,in the first verse which says "After the death of the two children of Ahron who were near G-D and died". According to our Rabbis in the Medrash,it teaches us that the death of righteous people atones for the nation.



Jonathan Pollard In Torah Codes

Posted by Rabbi Matityahu Glazerson on January 6, 2011 at 2:31 PM

Jonathan Pollard was a civilian American Naval intelligence analyst. His history of how he became an intelligence analyst is interesting can be found here. In 1983-1984, Pollard discovered that information vital to Israel's security was being deliberately withheld by certain elements within the U.S. national security establishment. Indeed it was the case that Israel was legally entitled to this vital security information according to a 1983 Memorandum of Understanding between the two countries. The information being withheld from Israel included Syrian, Iraqi, Libyan and Iranian nuclear, chemical, and biological warfare capabilities - being developed for use against Israel. It also included information on ballistic missile development by these countries and information on planned terrorist attacks against Israeli civilian targets.

When Pollard discovered this suppression of information and asked his superiors about it, he was told to mind his own business, and that Jews get nervous talking about poison gas; they don't need to know. He also learned that the objective of cutting off the flow of information to Israel was to severely curtail Israel's ability to act independently in defense of her own interests. Pollard was painfully aware that Israeli lives were being put in jeopardy as a result of this undeclared intelligence embargo. He did everything he possibly could to stop this covert policy and to have the legal flow of information to Israel restored. When his efforts met no success, he began to give the information to Israel directly.

 The story of his capture has been told very clearly . He and his wife have created a website with his side of the story . Our purpose here is to bring out in Torah codes one part of the Pollard story that is perhaps least written about: the relationship between Jonathan Pollard and Rabbi Mordechai Eliyahu.

 Rabbi Mordechai Eliyahu. When Jonathan was arrested in 1985, HaRav Mordechai Eliyahu was already the Chief Rabbi of Israel for two years. Anne Pollard, Jonathan Pollard's former wife, writes that when the spy case broke with all of its attendant hysteria and hyperbole, Rabbi Eliyahu ignored the slander and smear and took a more insightful look at the events. The Rav felt certain that there had to be enormous messirut nefesh (selfless devotion to the Jewish people) that lay behind what Jonathan had done for Am Yisrael. He determined that he must meet Jonathan face to face to investigate further.

 During the years until Rabbi Eliyahu's death (June 7,2010), Rabbi Eliyahu maintained close contact with Anne Pollard and visited Jonathan Pollard in prison on most of his visits to the US. Rabbi Eliyahu held that Jonathan's release is also the key to the release of all of Israel's captives and MIAs. Once Jonathan is out, all the captives are all out! Once they are all out, we are all in Redemption! In the same way that Joseph's name became Yehoseph, Joseph with an additional ה, Rabbi Eliyahu wanted for Jonathan Pollard to change his name from Jonathan, יונתן, to Yehonatan, יהונתן, with an additional ה. And indeed in Rabbi Eliyahu's study, Jonathan was referred to as Yehonatan.

For us the interesting part of this story is that Rabbi Eliyahu always referred to Jonathan as Joseph the Tzaddik of our generation, יוסף הצדיק של דרנו. Just as biblical Joseph was wrongly imprisoned for 12 years, so was Jonathan Pollard wrongly imprisoned. When biblical Joseph was let out of prison, he became the most important person in Egypt after the Pharaoh.

Rabbi Eliyahu's son is Rabbi Shmuel Eliyahu and is the chief rabbi of Safed. Rabbi Shmuel Eliyahu has called Jonathan Pollard the Tsaddik who is the foundation of the world.

Because of this story, it was natural to look for ELSs of the key words Jonathan, J. Pollard, prisoner, jail, and Joseph to see if they all came together in a compact table. What is surprising is that they do. And the verses running through the last two rows of the table are indeed from the story of Joseph and his imprisonment.

 This is a table showing the most compact meeting of the terms relating Jonathan Pollard to biblical Joseph. With expected number of ELSs set to 10, the probability of a monkey text from the ELS random placement monkey text population having as a compact table of all the ELSs shown is less than 1/100,000. The table spans the verses from Genesis Chapter 36 verse 21 through Genesis Chapter 39 verse 22.

                                                             The possibility table for the experiment.

The cylinder size is 922. With expected number of ELSs set to 10, had all the key words been a priori, the probability of a monkey text from the ELS random placement monkey text population having as a compact table of all the ELSs shown is less than 1/10,000. The table spans the verses from Genesis Chapter 33 verse 7 through Genesis Chapter 40 verse 16.

The cylinder size is 154. With expected number of ELSs set to 10, had all the key words been a priori, the probability of a monkey text from the ELS random placement monkey text population having as a compact table of all the ELSs shown is 3.5/10,000. The table spans the verses from Genesis Chapter 36 verse 21 through Genesis Chapter 41 verse 26.


Finding by Rabbi Glazerson