Ezra

This blog looks at Ezra's god scam. Before that technical changes in the BRB. Also, names updates to the Paleo Bible. Finally, a headline review, with what might be our expected use of a nuke.

BRB

The main technical change in the BRB app this week is the removal of the "Notes Mode" setting and content. Our goal for all of our apps is to keep our content out of the running flow of Bible texts. Asides will be used for such notes in the future. This change fixes presentation problems on small screens. Notes will eventually return as asides.

Since Tabernacles, Ryan has been continuing to update the BRB text with our latest understanding on the textual problems between Joshua and the various gods. We will look at one such example from Ezra below.

This week Ryan got a chance to finally start looking at this problem in the New Testament. With this week's update he is introducing an elegant fix to a strange problem. But this change is a little jarring. Let me explain.

Recovering Joshua

Perhaps the best way to think about the "divine name" problem is that the editors, so the 6 villains, were hiding references to Joshua. They were ultimately promoting their gods as a replacement for Joshua. This replacement starts with Solomon who puts in the Yahweh term instead of Joshua. Solomon built a temple to Yahweh. The term is still used by Jews and Zionist Christians. Sometimes the term in English is Jehovah.

By the time of Ezra, the ruling king is Persian. That kingdom has a "god of the skies." Ezra has power over the manuscript. He has a commission from a Persian king. So he ultimately plays manuscript games to feather and adjust the text so it conforms better to his boss, the king who pays Ezra's wages. This explains the diversity of divine names in the Old Testament.

So far, what I have just stated is review. What about the New Testament? What was Ananias doing? Did Ananias also have a god?

As soon as Ananias starts tampering the New Testament he is following in the footsteps of Solomon and Ezra. So his work is similar. Like Solomon and Ezra, Ananias is introducing a new god to the text. Most of Ananias' work is more subtle. Especially in the Gospels, his favorite trick was to copy around, and tweak, the otherwise inspired stories, similar to the way Chronicles copies Kings.

So after Ananias' work, we mostly end up with duplicate copies of events in Joshua's life. Some of those copies are inspired, some are not.

Markup

So Ryan has been working out changes in the BRB markup to cope with these issues. So far, this work has dealt with the edits of Solomon and Ezra. Dark green voice marks text by Joshua. Light green is attributed in some way to a god created by an editor.

The Filter related tags ride on top of this, but carry a different purpose. Filter tags mark text NOT in the Testimony. Filter tags also mark the likely villainous author.

Finally, there is markup that shows the likely chain of changes to the divine name. In particular how to get back to Joshua when Joshua is the likely inspired name.

Of course this is currently speculative. But this markup will get adjusted to conform to the audit. So specific examples will stop changing as the speculative nature of our work comes to a close.

New Testament

So Ryan has been looking at applying this same new markup to the problems with the New Testament text.

Most of this work is looking at duplicate passages. Those are the most common form of trouble in the Gospels. So when he selects the duplicate passage as being likely from Ananias, several tags start to apply.

The first is a Filter tag for Ananias. This marks that Ananias created this passage. The passage is thus not in the Testimony.

The dark green markup that was used for Joshua's voice, now changes to light green. This is exactly consistent with the recent Old Testament work. Now, in the New Testament, light green marks the voice of a god created by Ananias.

This is disorienting because we are used to having Joshua speak everything that is in his name in the New Testament. Though strange, this is still technically correct. Again, remember, this is currently speculative, but will be confirmed by audit.

So what happens to the name Joshua?

We spell this word the same as Joshua son of Nun. It is a reasonable English for the Aramaic, so Paleo spelling.

But what if the name Joshua ends up used in a light green, so Ananias, duplicate passage?

Or what if the name Joshua is used when describing some action that is the creation of Ananias?

Ultimately, this question is the New Testament version of the same problem going on with especially Solomon and Ezra's Old Testament edits. There is an implicit change in name. Ananias is not reporting on anything that the real Joshua actually said or did. It is thus incorrect to use Joshua in these Filter Ananias' passages.

So what divine name should be used for Ananias' New Testament edits?

Ryan had a flash of inspiration for what to do here. In these New Testament passages which are NOT headed for Testimony, the BRB now uses the name "Jesus." This is the Hellenized form of the name Joshua. There is a certain symbolic justice in selecting this name for use in non-inspired text.

For readers here who are still with me, and have not fallen out of your chair, this new name convention goes live when this blog goes out.

We are not yet all the way through our Tabernacles related New Testament reading. Ryan wanted the markup to catch up before we finish. More in future weeks.

Paleo Bible

Our general work load from Tabernacles has finally returned to something more normal. It has been about a month since I was able to really focus on the names lexicon problem with the Paleo Bible. I was finally able to return to this work this week. The Paleo Bible app now has the first installment of names loaded into the text. The link is given above.

This week all names have been loaded from Genesis to about Numbers 31. To see this in action you can look at Genesis 5 or 11 which are genealogies. Also Genesis 25, 36 and Numbers 26 have patches of names. Parts of Numbers 26 are almost completely filled in by the lexicon.

There are a few very high occurrence names that have also been added to the lexicon, but out of order. Joshua, Moses, David and Solomon are examples of the high occurrence names loaded out of order.

In terms of lexicon coverage, the lexicon now has 872 roots. It covers 10,956 different inbound forms for those roots. There remains 40,006 unique, but unknown, words in the inbound text.

In terms of manuscript coverage there are currently 692,427 inbound words in the manuscript. 534,312 of those words, so 77.17 percent, are found in the lexicon. 158,115 words, so about 22.83 percent, of the inbound manuscript have no lexicon entries.

These numbers shift around in unexpected ways because the lexicon itself identifies word breaks. So the total manuscript words climbs as the lexicon gets filled in.

Because the audit problem is so complex, it is important to keep the steps organized. Getting the lexicon and names annex filled is the current step. The overall goal here is to get an English word for all words in the running text. Once that is done, the recovery work can move on to other problems.

All of the names work is sorted by first occurrence. This provides a check on problems of missing or extra names when comparing texts. There are a few of those, examples follow. So names are getting loaded into the Paleo Bible text in their manuscript order. Names missing or out of order are at least being understood as to why they are missing or extra.

Lexicon Grouping

The most common problem I am currently dealing with is related to how words in the lexicon group together. Eventually, each lexicon entry will show a family of closely related words. Given the overall stats shared above, each lexicon entry will show off about 10 different forms. Of course, some are much more complex, and some are simple.

Names are headed for a names annex to a complete lexicon. That lexicon will also be sorted by the spelling of names related root words. Names have roots and suffixes like other regular words.

Perhaps the most common names related suffix is Yo-Wa. This ending turns a place name into the "ites" that live there.

So in the final lexicon, the root and this form need to merge. Sometimes these groups are already formed. Sometimes not. Once all names are loaded, a full alphabetization of all name related roots should provide a final review of what names belong in what lexicon entries.

Complicating this problem are frequent spelling variations on names. Added vowels, inconsistently applied, are everywhere. There are also common consonant transformations. Du and Re are often irregular.

These irregularly spelled roots should still be pulled together into single lexicon entries when the English is the same. This is done under the assumption that audit will remove the added vowels and fix spelling variations.

It is theoretically possible that what we know of as single English names are actually hiding different names. It is also possible that some names have more than 1 inspired spelling. This might be needed for ciphers. These are examples of issues that still need to be worked out.

Different Stories

Turns out, at times, the Aramaic just does not tell the same story. So at times there are discrepancies in the names lists. At times the Aramaic is not using a name at all, but regular vocabulary. This pattern is pretty common, which I did not expect.

If a story in Aramaic is using regular vocabulary, with the other parallel languages using names, we are probably seeing a sign of inspiration for the Aramaic version. This is a topic that will get more attention once we find audit passing passages that function this way.

It is also possible that someone in the translation chain out to English may have replaced a technical vocabulary word with a name in order to hide something frightening to Zionists. I have now looked at enough names to suspect there are games afoot in the English translation chain.

Translation vs. Transliteration

In most cases, when translating between languages, words which are used as names are transliterated. Transliteration is the consistent use of some system of letter substitution going on when names are moved between different languages.

For example, the conventional English version of some name will generally match what is going on in Paleo. I used Philip as an example in a previous blog. The subtle differences in that example become humorous, they are not serious.

The same goes on across ancient languages. Since Hebrew and Aramaic are both Semitic languages, the Paleo alphabet forms of names used in both of these languages is nearly always the same. Abraham, for example, is Wa-Ba-Re-Fe-Mo. This Paleo spelling is the same when coming from both Hebrew or Aramaic.

So when we see a word which is a name in one language, but then translated as a technical vocabulary word in the other, we know a game is afoot. As I crawl through the list of names, which I have intentionally sourced in a modern English text, I can see modern games afoot in this space. Zionists are still hiding stuff from English readers. There must be frightening topics for modern Zionists which are now hidden from readers in English texts.

Let me give a soft example that most readers here might recognize. This one is not particularly scary.

Nephilim vs. Giants

My first main English translation of the Bible was the NIV. This is the text that I had read through about 19 times before getting into our current work. In the NIV, in the time before Noah, there were Nephilim in the land.

In other versions of the text, say the KJV, there were giants in the land. Since I knew only Nephilim, anyone preaching about giants in the land was strange. Steve Quayle, for example, has an extensive video collection of hunting for skeletons of giants. He links his giants to that pre-flood story. Of course, for years, he looked to be using some secret knowledge to think his giants work was from the Bible. Actually, his work was just based on KJV English.

The Aramaic, so Paleo, for those Nephilim, Giants, is Ge-Ne-Ba-Re-Wa. This is NOT a transliteration of Nephilim. So there is a Zionist game afoot here somewhere. Why would the KJV era translators treat this as a technical word, but modern translators need to change this to a name?

I cannot say for sure what this word means. We need to be through audit. We need all inspired occurrences. We need to see how else it is used. But, the root is known. Ge-Ne-Ba is "nab" in English. It is one of the commandments. Don't gather seed in another's tent. Don't take something not yours.

If we add a Re, so head, so authority, this forms something like what gangsters, or central bankers, do as a group. The Wa ending is just "the." That those criminals saw themselves in this story may be what was so frightening that it would be hidden with a name.

Other Strange Names

This pattern is showing up with more mundane examples. In English we have sub-cultures that name things using common words. Summer camps for children are this way. "Purdy Creek," so "Pretty Creek" is an example. A common practice with railroad maintenance workers is name features of their rights-of-way this way. "Dead Man's Curve" or "Petticoat Junction" are a couple examples of this sort of naming convention.

It appears that this style of name creation was also going on in some of the accounts we read about in scripture. It flashed by fast this week, so I cannot give a cite, but the place name "mound of the testimony" is an example.

This looks like a very common pattern with Aramaic alone. This is something that we need to better study. It is new to us. So, when a name in Paleo is not transliterating into English, I am generally leaving those names out of the names annex. These words will be picked up as technical terms and get translated into English in the normal way. This process will leave behind the details that are needed to study this problem.

LORD, Lord, lord

I would guess that most readers of this blog grew up in a church tradition that used a text ultimately based on the KJV. Modern examples include the NIV, ESV and so on.

Those textual traditions cover over a series of pretty serious original manuscript problems using various forms of the world "Lord." Typically, this word is capitalized in 3 different ways.

There is only 1 way to speak this word. So in the minds of most church goers, these words are essentially all the same. They are not. These are clues into a crime scene investigation. It allows the translators to feign ignorance of their crime. They do use different spelled words for different underlying terms. But, they are covering up a mess and playing mind games in the heads of their Christian readers.

Greek, Hebrew and Aramaic

Making this crime scene even worse are the variations between the 3 different manuscript traditions as passed by history. Constantine's Christianity from 313 AD was based on Greek. Christianity, as we know it now, starts in Greek. In the Orthodox branches of Christianity, it remains mostly in Greek.

By around 400 AD, the Latin western church received a Latin OT based in Hebrew. Zionism was taking over. Jewish bankers were now ruling the church. The church was the front for the Jewish banking cartel that still rules most of the world.

Money and politics drove the west. That unholy alliance drove theology.

By around 1600 AD, the English wanted more of a cut. Usury was legalized, and an authorized text of the Bible appeared in English. It was personally approved by the king. His PR team explained he was an ancient language scholar. LORD, Lord and lord were still perfectly fine. Nobody wanted this secret to leak out. Anyone in ministry could wave away any questions about what that capitalization was hiding.

Lurking behind this entire western manuscript stack was the Assyrian Church of the East. They carried around Aramaic versions of both Testaments. This church tradition remains the ongoing victim of various genocides. The Armenian genocide was the largest and most well known. Zionists and their friends have been removing Christians across West Asia for the century since Armenia. Those Christians can dispute much of western Christian theology. Though they still do not have a clear view to the problem. They are just a serious threat.

Breaking Through

So over Tabernacles, Ryan and I first saw through this entire stack of manuscript related troubles. Joshua, so Jesus, is the only supernatural agent in the inspired text. He was the agent in the Garden of Eden. He has been active in the affairs of people ever since. He tends to care about people, especially families, of faith. He is actively raising souls to make them able to live forever. The first major harvest of souls appears to have been at the time of Moses. There was another such harvest late in the first century. Joshua willing, there will be another in our generation too.

The claimants to Joshua' position are called "gods." Gods are imaginary. They are created in the imaginations of men. Not just any men, but men who have carried political power for most of history. They invented various gods down through history. Their primary purpose is to give kings an apparent right to rule.

Joshua himself is involved in this process too. But not as a sign of favor, but as a sign of ignorance and rebellion. This is the point of Samuel's speech involving the problem of asking for a king. Gods, as an idea, spring up around kings since those kings want some apparent right to rule.

So fights between kings becomes fights between gods. We might say this slightly differently. Kings frame their own fights as fights between their fictional gods. The victorious king gets to promote his fictional god as the god that gave him the victory.

This general view of the world of living under gods, and not Joshua, is the context for various stories in the text. The Book of Daniel explains a dream where we learn of a series of successive kingdoms that will follow Nebuchadnezzar's kingdom. They are all ultimately heirs of Nebuchadnezzar's Babel.

That dream ends with a "10 toed" kingdom that is most likely the European Union and its children, the nations using Anglo bankers. The effective prophetic seat of the government for that kingdom is London. This is why the king recently visited his subjects in the US Congress. The reserve currency for that kingdom is clearly the USD, and that is also based in the USA.

Watching out for gods, so pretenders to Joshua's standing authority, is now becoming something of a spectator sport. We can see it in world headlines. We can also see it in parts of the text. Any use of LORD, Lord or lord in the text is going to be trouble. It is going to mark some sort of battle of the gods on the way to the world we know now.

One of those strange stories is in the Book of Ezra. In this blog I want to introduce you to the problems of Ezra.

Book of Ezra (KJV)

The link here is to the KJV version of the Book of Ezra in our Bible Reader app. This app is linked off Paleo.In. That app contains a series of versions that help to see the various forms the Bible has taken across time.

The KJV is interesting because it is the reference text that nearly all other English language translations have conformed to for the past 400+ years. The Bible purchasing public always wants something they know. There has never been a successful gap since the KJV where some non-conforming translation could materially diverge and still remain commercially viable. The ASV and RSV tried but failed.

Purpose

The Book of Ezra provides the origin story for the temple that was the stage prop for events during Passion Week in the New Testament. As readers of the New Testament, we need to know where that place came from. Ezra explains.

A secondary purpose of this book is to provide the commissioning letter for Ezra. This man is one of the 6 villainous editors. In particular, Ezra was commissioned to setup the distributed synagogue system that runs far away from the temple itself. Christians also know this as the local church system.

The Book of Ezra explains Ezra's personal ties to government funding, both for the building project as well as providing pay for those who work there. Similar ties to the Church have existed across most of European history. You can still easily see ties between the government and church in Russia.

American experience is slightly different. Generally speaking the government has stayed away from close ties to church. The "separation of church and state" has been a simple principle, easy for anyone to understand.

In practice, the US Government has been mostly run by Jews or their gentile cousins Freemasons. Keeping government funds out of church was a way to minimize the influence of Christians over the state. From the side of Freemasons, keeping out the moral and the people of faith was a useful thing. This is ultimately the source of the "Epstein class" rule of Congress. This is also why no amount of voting will alone ever fix problems in the government.

In any case, having the government be the ultimate backstop for most of Christianity has probably provided for the survival of the New Testament to our day. The king defended the KJV text by the force of arms. Ezra starts that process.

Ezra (ASV)

So until this past Tabernacles we have not had a sufficient mental framework for understanding the strange problems of the "divine names."

Some English language translations have attempted to nudge their readers beyond the LORD, Lord, lord family of problems. Perhaps the best known was the 1901 ASV. The link here is to the Book of Ezra in the ASV in our Bible Reader app.

If you look at that text, even verse 1 has a reference to "Jehovah." This is a hint at the "Yahweh" term found in the Hebrew at this location. This ASV was attempting to remove the LORD, Lord, lord triplet and expose at least some English vocabulary to allow readers to see 1 layer down.

The use of Jehovah, a stand in for Yahweh, is probably the most important reason why the ASV was not commercially successful. It was exposing a fundamental rift between the Christian New Testament and the Zionist Old Testament.

Ezra (BRB)

So the link here goes down 1 more layer. This time to the Ezra in the BRB. It has been checked against the Aramaic. Our BRB text treats Mo-Re-Yo-Wa, as the English word "Master." Alternative treatment is possible, but it would be even more strange to English readers.

Our theory of inspiration goes something like this. The inspired form of this book began in Paleo. It was transliterated to Aramaic. So far, so good. Aramaic readers could now read Paleo texts.

Scribes were later forced to change public Aramaic texts in order to conform it to edits going on in Hebrew. Some generation of those scribes changed out Solomon's Yahweh for Master. This would be following the public conventions on acceptable divine names. Some scribes probably knew the work of the editors and did not want to follow precisely along.

But, there are clues in Ezra that allows a reasonable stab at what the various god names might have been in the original text. Ryan has gone and made an estimation of that set of names. It tells an interesting story.

The book begins with an inspired introduction. It explains how Ezra's temple to Yahweh in Jerusalem was built as the response of a prophetic word given through Jeremiah. This was the end of a 70 year interval which was also tracked in Daniel.

This is a very strange introduction. Why would Joshua grant the construction of such a temple?

Joshua is in control of the world. He remains in control, even over evil men. They are following Joshua's own general plan for history. Evil men cannot escape that plan, no matter how much they may want to escape the plan.

The story then shifts down to the detailed story of the reconstruction of the temple to Yahweh that was done in Ezra's day.

There are a series of letters recorded in the Book of Ezra that deal with the details. It ultimately ends with the commissioning letter of Ezra himself. Ezra is the 5th villainous editor, the last in the Old Testament.

God vs. Elohim

If you read through Ezra you will find divine name transformation details provided in square brackets. An example is in Ezra 1:2. Let me quote it in full. "Cyrus, king of Persia, says: All the kingdoms of the land the Master [Yahweh], the God [Elohim * God] of the skies, has given me.

In Aramaic, we have one more odd complexity. Master, in Aramaic, is usually covering for the name Yahweh in Hebrew. So you can see the Master term followed by [Yahweh] in the BRB. Ryan is suggesting the audit will pass with Yahweh at that location, not Master.

Then there is the term "God." In brackets Ryan indicates [Elohim * God] which means Hebrew sees this as "Elohim" the name of a specific god. But in English it should be considered the generic "god" term.

There are people who name their pet cat "Cat" or their pet dog "Dog." This is fun, but confusing to anyone not in the know. (A dog named this way will strangely answer to anyone using the generic, probably not fair to the dog.)

In any case, something like this appears to be going on with some uses of the term "god." At times the term appears to be used as a specific god's name, Elohim, and at times the term used as a generic god term.

This is probably a natural outworking of a battle of the gods. At some point some powerful group used their name for god as the generic term for the category itself. That group was "Elite." They named themselves as a group after their god, El or Elohim.

Remember, this is all imaginary. It is the result of the battle between kings who were using false gods as giving them their right to rule.

This is why Joshua is not a god at all.

Which God?

But with this setup, you can now read through the story of Ezra and see the development of an interesting plot.

The entire temple building project in Jerusalem is commissioned by a Persian king. That Persian king followed the "god of the skies." The skies are over all. So from the Persian king's perspective all other gods are below the skies. So the god in Jerusalem is a lesser god. The group in Jerusalem was only following "Yahweh God."

This becomes a major plot complication. The Jews in Jerusalem are out to build a house to their god. They were fooling the king in Persia who has commissioned and provisioned the temple under different terms.

The Book of Ezra contains letters sent back and forth that started and stopped the building project. The battle is theological. Which god rules?

The Jewish answer appears to be the adoption of the generic term "god" as the "1 true god." Thus they retake theological control over Persia by slight of hand and by defining "Elohim" as the singular god.

The Book of Ezra seems to be the place where the inspired text is attempting to show how these ideas came to be.

Christians fall prey to the same linguistic slight of hand. The 1 true god ends up as the "father god." So there is a developmental chain out from Jehovah/Yahweh to Elohim to the fully generic god. Jesus ends up as the son of that father god.

This is the mess we all grew up in.

Interested readers can pick through the Book of Ezra's various letters in order to get some idea as to how the Jews absorbed the "god of the skies" back under themselves. This is generally the same theological process that was used by Ananias when editing the New Testament.

Headlines

Interesting headlines this week came out of Yemen, Iran and Russia. The war situation in Yemen appears to be the current best fit for our ongoing watch date.

We are currently in the replay of the reign of Azariah/Uzziah. Both names are used for him. It ends 2026-10-02. He had leprosy and lived in seclusion. His story maps the plague of boils that start with a fire from a furnace.

We have been tracking references to use of nuclear weapons because Japan was the last use of such weapons. Nuclear fallout creates leprosy/boils in the victims.

This week the war situation in Yemen has shifted to Ansar Allah's favor. They have mostly driven out Saudi mercenaries from much of western Yemen. Ansar Allah has mostly regained the coastal cities along the Red Sea and will be able to better enforce a blockade against Saudi oil transiting that passage.

Ansar Allah has also been very successful at targeting Aramco oil facilities across Saudi Arabia. Some of the fires have been historically massive. So the fire from a furnace into the air, for the expected plague, is matching this war very well. Perhaps better than anything seen with Iran.

There was a headline a few months ago where Trump agreed to supply the Saudi's with nuclear technology, so there is a match to nukes in Saudi Arabia. This is tying the Japan/Nuke part of the story to Saudi Arabia.

Ansar Allah has been under blockade from Saudi Arabia for about 12 years. So the king in seclusion is also a match.

This story ends on 2026-10-02, so there are still a few more weeks before this is over. Continue to watch this venue. The Saudis are Zionists, a fancy name for Pharaoh. This identification is NOT like Iran. This detail may matter to the general flow of these stories. Pakistan has a new defense pact with Saudi Arabia. Unclear if this would be brought into play.

Also of note, on the Zionist side of this war, the Israelis may have used a nuke in Lebanon in this week. The link for that is at the bottom of the blog.

Watch Dates

There are no other known dates until 2026-10-02 when we watch the end of the current king's reign. Jotham begins on 2026-10-03.

Shop Work

Shop work this week has been loading names into the lexicon for the Paleo Bible text.

Headline Review

The following caught my attention this week.

Trump's Men to Putin

The link here is to a PressTV post on Telegram with a pic of Trump's team arriving in Moscow to meet Putin. They would spend several hours with Putin and then travel to Kiev.

$100B Bribe

There was virtually no western media coverage of what was discussed when Trump's men met Putin. The link here is to John Helmer on with Nima to discuss what was known about the deal from Russian sources in Moscow.

Key points: Trump offered Russian oligarchs a very complex $100B bribe to stop the war in Ukraine. This would be giving the Russians back a little of their current frozen assets. The deal is structured in such a way to give the Trump family a massive financial windfall. This is why the Trump family are doing this and not normal diplomats.

My opinion: Though it would be called a peace agreement, in reality this would be a chance for the west to rearm and restart the war a few years from now. The Russians would be utterly foolish to accept. BUT, the timeline might want a break until prophetic dates in 2028 or 2029 or beyond.

Iran Targeting US Carrier

September 4, 2026, the IRGC targeted a US Aircraft Carrier with new long range missiles. Different accounts describe either a hit or at least how the US side needed to flee the region.

Iran is at least demonstrating they have air superiority, enough to prevent the US from operating near Iran.

Ukraine Map?

The New York Times, that great bastion of absolute truth, has published a map of what Putin will demand of the west to end the war in Ukraine. Mostly nonsense. But it does show what others have discussed about what Russia might want. Note how Kiev ends up in the center of a runt Ukraine. This city is probably to be fought over until the world burns down.

Japanese Fighting Words

The Japanese don't like Russian boundary artwork. This post by the Japanese Prime Minister has details. Japan looks to be readying the basis for some future war against Russia. Japan does not see itself as defeated, instead Japan is just waiting for history to allow the war with Russia to continue.

AFD Victory

The link here is to one of many posts on Telegram by Lord Bebo dealing with the recent election in Germany. This post has a graphic showing mail-in ballots as a percentage by each party. Mail-in ballots are going to be the German equivalent of ballot stuffing in the USA. You can see every party except AFD had more mail-in ballots than real voters. Zionists rule Europe just like the USA.

Saudi Nukes

Part of the prophetic story of Saudi involves their use of nuclear tech. This link details their setup to the IAEA in order to get that started. More of the prophetic matches for this month.

Fire From Furnace

For the record, a pic of fire in Saudi Arabia from Ansar Allah missiles. An example of more of the prophetic matches for what looks like our current set of headline matches.

Japanese Bond Sales

This is a link to a Youtube video detailing September 8, 2026, sales by Japan of $88B in US Bonds. Japan is the most likely country to cause a contagion that might spread through US Bond markets. This appears to have been an outright sale, and not just putting bonds on deposit with the US Treasury.

Netanyahu Knew October 7

Everyone suspected that Netanyahu knew about the October 7, 2023, attacks on Israel from Gaza. Now a book is out with details. The link here to a TASS post on Telegram provides some details that the UAE knew about and warned Netanyahu about 10 days ahead. It also cites the book where this is now published.

Rust on USS Abraham Lincoln

This is a followup. What originally looked like rust on the USS Abraham Lincoln was a heavy build up of algae. It was cleaned off by Thailand based port services. This post has some video from the local cleaning crew.

M4.1 Quake in Lebanon

The link here is to a brief Youtube video with a clip of an Israeli explosion in Lebanon. It was reported to have happened September 10, 2026. But, this happened at night, so the day break is disputable for charting.

1,100 tons of explosives were said to have been used. The shock measured as a 4.1 M earthquake. Hal Turner was the first I saw to report this. There are many other reports across the Internet.

No one is reporting the obvious. Israel used at least 1 nuke. This was the TNT equivalent of 1,100 tons of explosives. Israel did not use 500+ truck loads of bombs to create a quake of this size.

Israel looks to be using Lebanon to threaten nukes against Iran.

This is our first likely documented use of nukes in this prophetic window. We still have until October 2 for more.

More Later,

Phil