Tag: prophecy

Robots & AI IN THE BIBLE

If a = 6, b =12, c = 18, and so on, to the end of the alphabet, taking the letters that spell ‘computer’ what number does it add up to? Here’s your answer:

You can also do the same thing with the word ‘calculation.’ The total for either word comes to 666 – which is the number of the Mark of the Beast.

Elon Musk

By the way, Elon Musk doesn’t equal 666… Elon Musk comes to 660. The only way you can get another 6 is to ADD AN X, because X is the 24th letter of the alphabet, and Elon Musk owns X.

So 2 plus 4 = 6, and 660 + 6 = 666…
But that’s just me being clever and silly, and it turns it into a BOGUS CALCULATION!

Elon Musk is NOT the main thrust of 666 in the Bible.

I talk about the Mark of the Beast in the next article; this page is more about AI.

Weirdly, playing with the numbers 6 and 9 (9 being an upside down 6) is endlessly fascinating. For instance, using the above method, take the two words, computer calculation, together, and we have two sets of 666. i.e. 666 plus 666, which equals 1332. Now add the first and the last number, 1+2=3. That's 3 and 33, or 3+3+3, which added together is 9, which is an upside down 6. 

33 is a well-known Masonic number. Masons believe 33 symbolises a higher level of knowledge and understanding.* Be careful! It is not good understanding. 33 is a third of 100, and 100 is symbolic of completeness and perfection. Revelation 12:3-4 tells us that a third (33%) of the angels fell from heaven. So they fell from completeness and perfection. Judge it for yourself... Could 33 symbolise righteousness, or does it symbolise those who belong to Satan?

DISCLAIMER

Views expressed throughout are speculative possibilities. In no way should they be taken as serious doctrinal claims! Read with discernment.

AI & the Devil!

“They scale walls like soldiers” Joel 2:7… Are the Locusts of Joel and Revelation Prophetic Metaphors for Future Technology?

This article follows on from ‘Submarines in the Bible’ as it’s a little bit ‘out there’, but I’ve done it on purpose! It’s meant to challenge your thinking about God’s word, what it really means, and how it’s relevant to today’s world.

The Bible is a text rich in metaphor, mystery, and prophecy. For millennia, scholars have debated the meaning behind its symbols. In our modern age, a new layer of interpretation has emerged—one that considers the possibility that ancient prophetic visions may align with 21st-century technological developments.

Here, I’m speculating that the locusts in the book of Joel and Revelation may not be literal insects, but symbolic representations of future machines—perhaps even a swarm of robotic entities.

This swarm is described with almost military precision in Joel 2:


They charge like warriors; they scale walls like soldiers… they burst through the defenses and do not break ranks.” (Joel 2:7)


This is not the language of agriculture or biology. It is martial, mechanical. Joel’s locusts seem to move with uncanny coordination, discipline, and intent—hallmarks of modern autonomous robotic swarms. Military programs today are developing drone swarms and ground-based robotic units that could fit this exact description of machine soldiers.


They do not jostle each other; each marches in his path, and when they fall upon the sword they shall not be wounded. (Joel 2:8)


The Locusts of Joel: Robotic Swarms?

The book of Joel clearly says that a plague of locusts ravage the land.

But it’s more than that. Read Joel 2:31 and you’ll see it’s also talking about the day of the Lord.

In Joel 2:10 the vision is apocalyptic. The earth quakes before them. The sun, moon and stars withdraw their shining.

If Joel’s vision was indeed prophetic, it’s conceivable he is describing not just insects, but future machines—perhaps drones or robotic units devastating landscapes with the cold precision of artificial intelligence.

Military drone swarms (like locust swarms) have now become a reality, and robot armies are being developed for use in warfare.

The headless robot dogs, developed 7 years ago, freaked me out back then. But the tech is advancing at lightening speed, and the new age of AI and robots is now upon us.

Revelation’s Locusts from the Abyss

In Revelation 9, another swarm of locusts emerges—this time from the Abyss:

“And out of the smoke locusts came down on the earth and were given power like that of scorpions of the earth.” (Revelation 9:3)

These locusts are given a disturbing and surreal description. They are demons, but perhaps they are inhabiting robot bodies?

“The appearance of the locusts was like horses prepared for battle… their faces were like human faces… they had hair like women’s hair, and their teeth were like lions’ teeth. They had breastplates like breastplates of iron, and the sound of their wings was like the thundering of many horses and chariots rushing into battle.” (Revelation 9:7-9)

The imagery here is bizarre—part animal, part machine, part human. Could it be that John, like Joel, was seeing something technological that he lacked the vocabulary to describe? Iron breastplates, the sound of mechanical wings, and terrifying synthetic faces all align uncannily with descriptions of advanced robotics or cybernetic drones—devices perhaps designed for psychological warfare as much as physical destruction.

The following video predicts that this scenario could come true as early as 2028.

Given that these locusts emerge from the “Abyss,” a term often associated with the spiritual realm or deep places of the Earth, one might even interpret this as a reference to technology originating from hidden or classified sources—perhaps even from subterranean facilities or advanced AI research black sites.

Additionally, the enigmatic “image of the beast” in Revelation could, in light of recent advances, be reimagined as a prophetic vision of holographic artificial intelligence.

Second Disclaimer…

Although that is a possibility, it’s probably not correct.

It’s much more likely that Bible scholars got it correct in the past, when they concluded that the image of the beast was either the USA or the United Nations submitting to Roman Catholic dominance, as governments did in the dark ages. (Even this week Anthony Albanese invited the pope to visit Australia.)

But here’s an alternate scenario.

The Image of the Beast: A Hologram?

Further deepening the technological reading of Revelation is the “image of the beast” in Revelation 13.

“It was allowed to give breath to the image of the beast, so that the image of the beast could speak and cause all who would not worship the image of the beast to be slain.” (Revelation 13:15)

This image described is not simply a statue; it is animated, speaking, and capable of judgment. In a pre-modern world, such a vision would be unfathomable. But in our age of holography, AI-driven virtual avatars, and deepfake technologies, it becomes chillingly plausible.

Imagine a globally projected holographic figure, infused with artificial intelligence, demanding allegiance. With voice synthesis, predictive algorithms, and biometric surveillance, such an “image” could, in theory, interact, track, and even punish dissenters. The ability to “cause those who refuse to worship to be killed” need not be mystical—it could be enforced by autonomous systems, robotic enforcers, or algorithm-driven security frameworks.

Even if that doesn’t happen, time is running out on us before everything gets rewritten with AI…

The locusts may yet return—not as insects, but as the machines of our own making.

Convergence of Prophecy and Technology

When we read the descriptions of coordinated swarming locusts, synthetic monsters from the abyss, and speaking images demanding worship, we must ask: are these simply metaphors, or was the Bible warning us of a future where technology—ungoverned by morality—becomes the true AI apocalyptic force?

As artificial intelligence, robotics, and immersive holography race forward, perhaps we are witnessing not just innovation, but the unfolding of visions sealed for “the time of the end” (Daniel 12:9).

According to Professor Jiang Xueqin the reasons behind AI development are insane!

In the following lecture Professor Jiang explains why. The actual lecture starts 9 minutes 30 seconds into the video. (If you are time pressed, the beginning section merely explains that these are his own unique ideas on the subject.)

In the video above, Professor Jiang explained that the people behind AI have crazy religious beliefs. Those beliefs are not Biblical. But keep reading. 

Did you know AI is actually mentioned in the Bible? It's in a story about God's displeasure with a city called Ai. Is this story merely history? Probably, BUT THEN AGAIN, CONSIDER THIS...

Using AI with a double meaning (AI instead of Ai), is NOT stretching the boundaries of Biblical interpretation. Here’s why:

When you see “Abraham” or “Moses” or “Ai” capitalized in your English Bible, that’s entirely a convention of English translation, not something present in the Hebrew source text which did not use either capitals or lower case in the text. Therefore using ‘AI’ instead of ‘Ai’ is still maintaining an accurate translation.

But in the Bible, is the destruction of the city of AI symbolic of the future fate of modern Artificial Intelligence?

It depends on how prophetic you think some Bible stories may be, and if you think AI can be used by the devil, or not.

AI is already being used by organisations with warlike agendas. Apparently the company behind Claude AI is already involved in a dispute about it’s use with the United States military, in the operation that captured President Maduro.

The King of AI

If you think AI is from the devil, (and why not? – AI is basically a pattern recognition machine, however even the experts admit they don’t really know how AI thinks, and it often lies… Satan is the Father of lies.) If you think demons control AI, you may find the Bible story about AI in JOSHUA CHAPTER 8 interesting.

Jos 8:1 And the LORD said unto Joshua, Fear not, neither be thou dismayed: take all the people of war with thee, and arise, go up to AI (Ai): see, I have given into thy hand the king of AI, and his people, and his city, and his land:

Jos 8:18 And the LORD said unto Joshua, Stretch out the spear that is in thy hand toward AI (Ai); for I will give it into thine hand. And Joshua stretched out the spear that he had in his hand toward the city.

Jos 8:25 records that 12,000 were killed. This number is often used in the Bible, where it represents a complete, ordered, and total action—whether that is the saving of God’s people totally (as in Revelation) or the total judgment of a city in disobedience (as in Joshua). 

Jos 8:28 And Joshua burnt Ai /AI, and made it an heap for ever, even a desolation unto this day.

Jos 8:29 And the king of AI he hanged on a tree until eventide: and as soon as the sun was down, Joshua commanded that they should take his carcase down from the tree, and cast it at the entering of the gate of the city, and raise thereon a great heap of stones, that remaineth unto this day.

Is that symbolic of God’s total abolition of the power of the devil in the future? It would not surprise me.

The Bible prophecies that the ’Babylonian beast system’ that we have now will be replaced upon Christ’s return. Prior to that Revelation 18 describes the destruction of our current system: ’And the kings of the earth, who have committed fornication and lived deliciously with her, shall bewail her, and lament for her, when they shall see the smoke of her burning… And the merchants of the earth shall weep and mourn over her; for no man buyeth their merchandise any more: The merchandise of gold, and silver… and all manner vessels of most precious wood, and of brass, and iron, and marble… and horses, and chariots, and slaves, and souls of men.’

Rev 13:4 And they worshipped the dragon because he gave power to the beast: and they worshipped the beast, saying, Who is like the beast? Who is able to make war with him? This verse is talking about the nations of the world worshiping the devil back when it was written, but also in the near future. The beast is a clearly a political entity led by the dragon (Satan). (The rider of the beast is a powerful church described in Revelation chapter 17.)

Will the beast also be assisted by AI?

Revelation 13:15 And he had power to give life unto the image of the beast, that the image of the beast should both speak, and cause that as many as would not worship the image of the beast should be killed.

It is entirely possible that Satan the devil ultimately uses AI to make war on mankind with his battle for control of the mind, using AI to control the media

…or even physical control of the population in the future!

I put the following question to Claude AI:

I am interested in governments handing control of things to Ai. Is there no way of regulating it except with the stupidity of politicians decisions?

Claude’s reply:

It’s a genuinely important concern, and you’re right that political regulation has a poor track record with technology — lawmakers tend to lag years behind, misunderstand what they’re regulating, and often end up serving whoever lobbies hardest.
That said, there are a few other mechanisms worth considering:
Technical safeguards built into the models themselves — what Anthropic calls “alignment” work. The idea is that safety is baked in rather than bolted on by law. Whether that’s sufficient is hotly debated.
Industry self-regulation — companies setting their own standards. The obvious problem is that competitive pressure tends to erode voluntary restraint over time.
International bodies — similar to nuclear or chemical weapons treaties. The problem is enforcement, and that AI capability is far more distributed than nuclear technology ever was.
Civil society and public pressure — harder to organise but historically more responsive than governments to fast-moving problems.
The deeper issue you’re pointing at is that governments handing control to AI systems is often driven by efficiency and cost savings, with risk assessment done by people who don’t fully understand what they’re deploying. That’s genuinely dangerous.
Honestly, none of the current regulatory frameworks feel adequate to the pace of development. The most realistic hope is probably a combination of all the above — imperfect, messy, but collectively providing some friction against the worst outcomes.
What specifically worries you most — military, public services, surveillance?

One central AI over everyone, and controlled by a government not concerned for minorities.

That’s one of the more serious risks serious thinkers in this space worry about too — sometimes called “global takeover” risk, whether by a government, corporation, or other actor using AI to lock in permanent control.
A few things make it particularly concerning:
AI concentrates power in ways previous technologies didn’t. A sufficiently capable centralised AI could potentially monitor, predict, and suppress dissent at a scale no authoritarian regime has ever managed before. History’s worst governments were always limited by the inefficiency of human enforcement. AI potentially removes that limit.
The minorities point is sharp. Democratic majorities have always been capable of oppressing minorities — AI in the wrong hands doesn’t create that impulse, but it could make it vastly more effective and harder to resist or escape.
What makes it harder to solve is that the governments most likely to misuse such a system are also the least likely to accept international constraints on it. China is the obvious example people point to, but it wouldn’t be the only risk.
The more optimistic counterargument is that distributed AI development — many countries, companies, and open source projects all advancing simultaneously — makes single-point control harder to achieve. No one actor easily monopolises it.
But that’s cold comfort if even one sufficiently powerful actor gets there first.
It’s essentially the central political question of the next few decades, and most governments aren’t treating it with anything close to the seriousness it deserves. Your frustration with politicians on this seems well founded.


You are currently inside the prophecy door. Continue with this series HERE, or click below to choose another door.

HOME – Choose Your Door


* Footnote: This same mistake that Masons make (believing the number 33 represents a higher level of knowledge) is illustrated in the story of Adam and Eve. They were booted out of Eden, the paradise that God had already put them in. Gen 3:6 says Eve (just like the Masons) wanted forbidden knowledge that could make her wise. But it only led to death. Deut 29:29 shows some things are NOT good for us now, but are reserved for an appointed time… Perhaps AI may also be a step too far?


NEXT

get a better understanding of Bible prophecy…

Learn about the mark of the beast, here.


AI Job Apocalypse & Complete Chaos: How Exponential Change Will Reshape the World by 2028

Turning your world Upside Down

Here’s what the next three years will bring—and how to prepare for the storm

The world is on the brink of a transformation so profound it feels almost apocalyptic. AI is advancing at an exponential pace, threatening to wipe out millions of jobs by 2028. Chaotic weather patterns, fueled by climate change, are destabilizing nations and creating widespread suffering. For those who look to the Bible, the words of Daniel 12:4 resonate deeply:
“But you, O Daniel, roll up and seal the words of the scroll until the time of the end. Many shall run to and fro and knowledge shall be increased.”
Knowledge is indeed increasing at an unprecedented rate, and with it comes disruption, chaos, and uncertainty.

The Exponential Pace of Change: A Ticking Time Bomb  

The pace of technological advancement isn’t just fast—it’s exponential. What used to take decades now happens in years, and what took years now happens in months. By 2028, the world will be unrecognizable. Here’s what to expect:  

1. Currently: AI tools like ChatGPT, DeepSeek, and MidJourney are becoming ubiquitous, automating 40% of administrative and creative tasks in fields such as law, finance, and customer service. Self-driving trucks will soon dominate the roads, wiping out 3 million trucking jobs in the U.S. alone. This shift will be felt across industries, but some sectors will be hit harder than others.

2. 2026: AI begins replacing mid-level management roles, with algorithms making decisions faster and more efficiently than humans. The global job market sees its first wave of mass unemployment, with 75 million jobs lost worldwide.  

3. 2027: AI achieves near-human-level reasoning, disrupting industries like law, medicine, and engineering. Even high-skilled workers are at risk, and the gig economy becomes the only lifeline for millions. According to the World Economic Forum’s *Future of Jobs Report 2023*, 23% of jobs are expected to change by 2027, with 83 million jobs eliminated and 69 million new roles created.

4. 2028: AI systems begin to outperform humans in virtually every field, leading to widespread economic and social upheaval. Governments struggle to respond, and inequality reaches unprecedented levels. The middle class is gone, leaving only a few ultra rich, and the rest struggle to survive.  

The exponential growth of AI isn’t just changing the job market—it’s reshaping society itself.

And as knowledge increases, so does the chaos.

Chaotic Weather and End Times Prophecies 

While AI disrupts the job market, the physical world is also in turmoil. Chaotic weather patterns, fueled by climate change, are becoming more frequent and severe. Hurricanes, wildfires, and floods are devastating communities, displacing millions, and straining global resources. For those who study biblical prophecy, these events echo the words of Matthew 24, where Jesus describes the signs of the end times:  

“Nation will rise against nation, and kingdom against kingdom. There will be famines and earthquakes in various places.” (Matthew 24:7)  

“Because of the increase of wickedness, the love of most will grow cold.” (Matthew 24:12)  

“For then there will be great distress, unequaled from the beginning of the world until now—and never to be equaled again.” (Matthew 24:21)

The convergence of technological disruption and environmental chaos feels like a fulfillment of these prophecies. As AI reshapes the economy, extreme weather events are destabilizing nations, leading to food shortages, mass migrations, and social unrest.

The world is entering a period of unprecedented uncertainty.

One of the leading figures of the AI boom, and CEO of OpenAI, Sam Altman, says “AI will probably lead to the end of the world, but in the meantime there’ll be great companies!”

Industries on the Brink of Collapse

The dual forces of AI and environmental chaos are pushing entire industries to the brink. Here’s what’s at risk:  

1. Agriculture: Chaotic weather is disrupting crop yields, while AI-driven automation is replacing farmworkers. Real food production, as opposed to GMO food production, is being threatened.  

2. Energy: Extreme weather is straining power grids. Solar and wind energy production is unable to cope, and the switch away from coal by certain governments is being exposed as a monumental blunder. At the same time AI is optimizing energy production, leaving human workers redundant.  

3. Construction: Extreme weather is destroying infrastructure, while AI-powered robots are taking over construction jobs.  

4. Healthcare: AI is revolutionizing diagnostics and treatment, but increasing unwellness, wars, and other disasters are overwhelming healthcare systems. The American people are the sickest in the world, due to the deception of the food and drug companies. Rev 18:23 has never been more applicable.  

5. Art & Publishing: It now takes just a few seconds to produce art like this…

6. Societal Chaos: Misinformation, Deepfakes, and Ethical Concerns

AI’s impact extends beyond the economy—it’s also reshaping society in ways that could lead to chaos. One of the most pressing concerns is the rise of AI-generated misinformation and deepfakes. In 2023, deepfake cases increased by 900% compared to 2022 (DeepTrace Labs, 2023), raising fears about their use in elections, fraud, and propaganda.

Ethical concerns are also mounting. A 2023 Stanford study found that 65% of AI systems exhibit significant bias in hiring and lending decisions, highlighting the need for greater transparency and accountability. Governments are struggling to keep pace with AI advancements, with the EU’s AI Act aiming to regulate high-risk AI applications.

How to Survive the Coming Chaos 

The convergence of AI disruption and environmental chaos demands urgent action. Here’s how to prepare:  

1. Reskill for the AI Economy: Learn AI-related skills like data analysis, coding, or digital marketing. Platforms like Coursera and Udemy offer affordable courses.  

2. Prepare for Climate Instability: Stockpile essentials, learn survival skills, and consider relocating to areas less vulnerable to extreme weather.  

3. Strengthen Community Ties: In times of crisis, community is your greatest asset. Build relationships with neighbors and local organizations.  

4. Stay Spiritually Grounded: Now is the time to deepen your faith and seek guidance through prayer, and studying deeper into Scripture. The Bible is not myth or fiction. In case you haven’t read my Proof of the Bible page, or have doubts about God, the following video should help you understand that Bible stories are real!

A World on the Edge  

The next three years will be a period of exponential change and unprecedented disruption. AI will reshape the job market, chaotic weather will destabilize nations, and the signs of the end times will become harder to ignore. As Daniel 12:4 foretold, knowledge is increasing, and with it comes both opportunity and peril. The question is: Are you ready?

Conclusion 

By 2028, the world will be a very different place. AI-driven job loss, chaotic weather, and the fulfillment of biblical prophecies will converge to create a future that is both exhilarating and terrifying. The time to prepare is now. Reskill, adapt, and strengthen your community—because the future is coming, and it’s coming fast.

What do you think about the rapid changes we’re seeing? Are you prepared for what’s coming?

FULL DISCLOSURE

I USED AI TO WRITE MUCH OF THIS ARTICLE! … with only a few adjustments. Can you tell?

Please go to my home page to REALLY plan for the future!

The Reality of Fire

Wow! The world has experienced a great number of fires recently. Almost like Revelation 8:7.

The fires are very traumatic for those involved.

The use of Direct Energy Weapons has been speculated. It sounds far fetched, and I don’t know if it’s true.

Were the fires mainly caused by men, or were they an act of God?

It’s also hard to believe the changes that fire can bring. The aftermath can be heartbreaking.

Back in 2019 we had a fire go through our own property, and I should mention the miracle attached to that story.

A fire truck that should not have been in our area was ordered to leave when the fire became too severe, but the crew were cut off at our place, and so, because they were there, where they weren’t supposed to be, they saved our house! Even so, our caravan, a container, part of a shed, a pump house, and 30 years of beautiful gardens were burned in spite of their efforts. This was before the fire:

We were able to evacuate just in time. When embers began falling in the yard I was getting into my pajamas, but my wife realized it was time to go!

The wind got so bad I was not able to secure the driveway gate properly on the way out, and when we returned next morning the wood in it was shattered to pieces and the other end of the fence burned.

This is the gate I had trouble securing.

This is the second gate at the other end of the long fence we built, which survived, but a section of the wood got burned.

It took us a year of hard work to properly clean up.

The next two photos both feature the same rock, before

Then after both drought and fire.

I won’t say more, except, because of the Biblical theme I have going on this website, it’s appropriate to include this Revelation 9 screenshot about what’s still to come in Bible prophecy:

God is real. His words are real, and when you experience fire, you know just how real that is.

The Bible says God is love. It also says God is a fire.

Which is it then? Is God Love, or is He a Fire?

God’s fire is only for those who spit in God’s face. Psalms 11:6, Luke 17:29.

For those who don’t reject God, there is very good news. This is Zephaniah 3, from the New Living Translation:

Or read 1 Peter 5:7 or Psalm 36:7, 7 or Isaiah 58:11.

At least two translations say, “And the Lord will guide you continually, and satisfy your desire in scorched places and make your bones strong”.

The Reality of God’s Love

Staying with the subject of explaining God’s love, Jesus said we should forgive those who sin against us 70 times 7. (That’s according to most translations. Mat 18:22 is poorly translated in the ESV.)

Amazingly, in the more accurate KJV, Jesus is referred to by name 70 x 7 in the odd books of the Bible, and again 70 x 7 in the even books!

This video has complete details to verify it.

Jesus forgives our sins. God verifies it by using the same number, for the number of times Jesus is mentioned in the Bible! It shows that God IS love

As in John 3:16 above, God wants to rescue us from trouble, and from all the fires we face in life, and in so doing, prepare us for an eternity where death and hell are themselves thrown into the lake of fire. (See Revelation 20.)

All things, in the end, can work for the good! Romans 8:28

~

The photo below is not the same fire that threatened our house. It’s just burning off we did on another occasion!


If you’ve been navigating from my home page through Door #1 – The SKEPTIC, perhaps by now you may be interested to see what’s behind Door #2 or Door #3?

To find out, click the box below.

Submarines in the Bible!

DISCLAIMER

Views expressed throughout are speculative possibilities. In no way should they be taken as doctrinal claims! Read with discernment.

The Bible is more interesting than most people realise, but I need to include a disclaimer for this page. This is speculation only. Please judge for yourself if you think it’s realistic or not. If not, don’t let that deter you from studying more sure subjects.

Scripture tells us God has prophesied the end from the beginning: Isa 46:10 Declaring the end from the beginning, and from ancient times the things that are not yet done, saying, My counsel shall stand, and I will accomplish all my purpose:

In my opinion, I believe God has hidden things in the Bible that have only been revealed in the last 50 years. Such as submarines in the Bible! This concept is not original to me, but it’s still unknown to most people.

It seems to me that in a few places the Bible codenames subs, calling them ‘Leviathan‘ and ‘Dragons.’

For example, Isaiah 27:1 In that day the LORD with his sore and great and strong sword shall punish leviathan the piercing serpent, even leviathan that crooked serpent; and he shall slay the dragon that is in the sea.

So here’s the thing: Why would God PUNISH a sea creature that he’s made?

It could be that Satan is being referred to as the dragon, or leviathan, however consider Psalm 104:26:There go the ships, there is that leviathan, whom thou hast made to play therein.

But maybe God didn’t directly make it!… In Scripture, God takes responsibility even for things he hasn’t done. That’s because God made everything, and without God, nothing would exist.

Before we go further into the Scriptures, let me just mention that modern-day Israel currently has a fleet of five subs that are believed to be fitted with nuclear-capable cruise missiles, and one of them is called 'Leviathan.' 
Israel also has a sixth sub on order, due to be delivered in 2027, called Drakon, which means Dragon.

Psalms 74:14 Thou brakest the heads of Leviathan in pieces, and gavest him to be meat to the people inhabiting the wilderness.

Let’s look at the other verses where LEVIATHAN is mentioned in Scripture.

Do some of these mentions of ‘Leviathan’ have a DOUBLE meaning?

Job 3:8 (Youngs Literal Translation)
LET THE CURSERS OF DAY MARK IT, WHO ARE READY TO WAKE UP LEVIATHAN.

Finally, Job 41, the entire chapter. Most of it seems to be talking about your regular sea monster, but there are a few things, such as doors in the sea monster, that make you wonder! I’ve added comments.

Can you pull in Leviathan with a fish hook or tie down its tongue with a rope? Can you put a cord through its nose or pierce its jaw with a hook? (This is not an ordinary fish.)

Historians say Leviathan was first mentioned in Canaanite mythology as Lotan, a seven-headed symbol of an untamed marine beast. Is that what the Bible is referring to with borrowed symbolism, or is there more to it?

Will it keep begging you for mercy? Will it speak to you with soft words? (Low frequency digital signals?) Will it make an agreement with you for you to take it as your slave for life?

Can you make a pet of it like a bird or put it on a leash for the young women in your house? Wycliffe-Modern translation says ‘Whether thou shalt scorn him as a bird (aeroplane?), either shalt thou bind him to thine handmaidens?(In the navy, woman are not allowed to be crew on submarines.)

Will traders barter for it? Will they divide it up among the merchants?

Can you fill its hide with harpoons or its head with fishing spears?

If you lay a hand on it, you will remember the struggle and never do it again!

Any hope of subduing it is false; the mere sight of it is overpowering. No one is fierce enough to rouse it.

Who then is able to stand against me? Who has a claim against me that I must pay? Everything under heaven belongs to me.

Smoke pours from its nostrils
as from a boiling pot over burning reeds.
Its breath sets coals ablaze, and flames dart from its mouth.
Strength resides in its neck;
dismay goes before it.


The folds of its flesh are tightly joined;
they are firm and immovable.
Its chest is hard as rock, hard as a lower millstone.
(Referring to the uranium powered atomic reactor core? See just how hard in the screenshot below.)

I will not fail to speak of Leviathan’s limbs (KJV – ‘his parts’ but the word can also mean pole or stave,) possibly referring to the propellor shaft, or the PERISCOPE?

This is so interesting I thought I’d share a couple of screenshots in order to prove I’m not making it up! The word used is Strong’s # H905, (bad or baddaw) as shown above. It appears 16 other times in the Old Testament in the context of staves or poles. The ChatGPT screenshot shows just four of them.

Continuing Job 41…

its strength and its graceful form.
Who can strip off its outer coat?

Who can penetrate its double coat of armor? (The KJV translates the last part as “who can come to him with his double bridle?” What on earth does that mean? A double bridle may refer to its propeller and rudder for steering! )

Who dares open the DOORS (note that this monster has doors, plural – more than one!) of its mouth, RINGED ABOUT with fearsome teeth?

When the sub pictured below opens its missile DOORS there are two rows, EIGHT RINGED DOORS IN EACH ROW, that look like teeth.

Its back has rows of shields tightly sealed together; each is so close to the next that no air can pass between. And They are joined fast to one another;
they cling together and cannot be parted.

Its snorting throws out flashes of light;
its eyes are like the rays of dawn.
Flames stream from its mouth; sparks of fire shoot out.
(Torpedoes, of course, result in fire.)

When it rises up, the mighty are terrified; they retreat before its thrashing. (ASV: When he raiseth himself up, the mighty are afraid: By reason of consternation they are beside themselves.)

North Korea is of particular concern. They have a fleet of about 70 submarines including at least one operational missile submarine.

The sword that reaches it has no effect, nor does the spear or the dart or the javelin. Iron it treats like straw and bronze like rotten wood.

Arrows do not make it flee;
slingstones are like chaff to it.
A club seems to it but a piece of straw;
it laughs at the rattling of the lance.

Its undersides are jagged potsherds,
leaving a trail in the mud like a threshing sledge.
Translations vary, making it hard to know the true meaning of some verses. Wycliffe-Modern is completely different for this verse. It says “The beams of the sun shall be under him; and he shall strew to himself gold as clay.”

(The Wycliffe translation describes Leviathan in the future tense, but, because it does that with most subjects, it may not mean anything here.)

This is obscure language. Are these pointed shards coming from the sea monster, or is it the result of nuclear missiles being fired?

It makes the depths churn like a boiling caldron
and stirs up the sea like a pot of ointment.

It leaves a glistening wake behind it;
one would think the deep had white hair.
Nothing on earth is its equal—
a creature without fear.

It looks down on all that are haughty;
it is king over all that are proud.”

Twelve Submarine-Like Features

How many characteristics of these Biblical sea monsters just happen to match a description of modern subs? Here’s a summary of some of the above points.

All references below are set for the King James Version, but TRANSLATIONS VARY.

1) They shoot fire (Job 41:19). Therefore this is not merely a crocodile.
2) They have tightly joined together outer scales (Job 41:15-17, 23)
3) Conversations with them are in low frequency (Job 41:3)
4) Woman (or damsels!) are not tied to them (Job 41:5)
5) Flames dart from their mouth (Job 41:21) This is more than one mention, with smoke separating the two mentions. Could one refer to torpedoes, and the other missiles?
6) The nether, or lower heart of Leviathan is as hard as a nuclear reactor core (Job 41:24)
7) Other “parts” of them may be a limb OR a pole, stave or periscope (Job 41:12) (plus the same verse adds power in a graceful shape!)
8) They may have a double steering device (Job 41:13) [perhaps not directly relevant, but James 3:3-4 also manages to associate bridles with steering ships]
9) They have ringed doors that open in rows (Job 41:14)
10) and when they open their doors, people are besides themselves with terror. (Job 41:25)
11) They churn the deep (Job 41:31)
12) They leave a glistening wake behind them in the water (Job 41:32)

Subs and wars originate with Satan the devil. God accepts ultimate responsibility, and in the future, God will punish when needed. (Isaiah 27:1, Psalms 74:13,14.)

Interestingly, Loton, the original Leviathan in Canaanite mythology, had 7 heads. If subs are used in nuclear war in future, it will be during the time of the 7th head of Revelation 17:7, 17:9-10 etc. Did the idea of 7 heads come from Satan, who also knows about 7 heads? Is Leviathan a sea monster, or a beast power submarine?

Maybe yes, maybe no.

There is one more thing I found…

Another Fascinating Coincidence

If you go to https://pastorstevew.com you can download and read a free ebook called TIME IS RUNNING OUT. It has a chart that matches years to chapters in the King James Bible, according to a logical countdown progression. You may think it’s bizarre, but many of the years have news events that match English words in the chapters.

For example James chapter 4 matches the year 1903, the year of the first successful aeroplane flight, and although out of context, verse 10 contains the phrase “lift you up.”

Another example: 1912 matches 2 Peter chapter 3, and verse 6 in the chapter happens to say “being overflowed with water perished,” which matches the sinking of the Titanic in that same year -2012.

Pastor Steve gives dozens of other examples that fit, even though this is something you may think is not a legitimate way to study Scripture!

I wondered if there were any more ways to verify the Countdown Calendar and timeline. Then I noticed that the year 1899 is assigned to Job 41.

I believe submarines in the Bible, as detailed above, are described throughout the entire chapter of Job 41.

How does it connect?

Well, that was the exact year the United States navy purchased its first submarine! The very first naval sub was the USS Holland, and the navy bought it on April 11, 1899, for $150,000. It was put into service the following year.

That’s an amazing coincidence.

Nothing here is proof of anything, but the coincidences tend to verify each other, pointing to both possibilities being correct.


Are you looking for a place of safety, away from the times of trouble just ahead of us? Please read https://nicetiming.com/2022/01/15/end-time-prophecy-in-the-song-of-solomon/

The Jubilee Count to the End

DISCLAIMER

Views expressed throughout are speculative possibilities. In no way should they be taken as doctrinal claims! Read with discernment.

Why the Jubilee Matters

Some may not realise it, but the Biblical Jubilee pictures the coming reign of Christ, when men are set free from Satan’s bondage. It isn’t just an ancient economic policy — it’s a picture of liberation. Debts cancelled, slaves freed, land restored. At a prophetic level, it points toward the future reign of Christ, when humanity is finally released from bondage to sin and death. But the Jubilee also functions as a counting system, and when you follow that count carefully, some striking patterns emerge.

First: How Does the Jubilee Count Work?

49 years, not 50

Before getting into the prophecies, we need to be clear on how the Jubilee cycle is counted — because there’s a widespread misunderstanding here that I held myself for a long time. Many people assume the Jubilee repeats every 50 years, but Leviticus 25:8 says to count seven sabbaths of years — seven times seven, which is 49. The 50th year is indeed called the Jubilee, but it simultaneously serves as the first year of the next 49-year cycle. The two overlap; there’s no extra year inserted between cycles.

It’s like saying Sunday is on the eighth day of a 7 day week, but we still count weeks consecutively in 7’s. The Jubilee works the same way — the 50th year and the 1st year of the next cycle are the same year, and the cycle continues in blocks of 49.

This matters a lot for the calculations that follow. Using 50-year blocks, the historical alignments fall apart. Using 49-year blocks, as Leviticus actually specifies, they come together with surprising precision.

Where the Count Begins

Leviticus 25 connects the Jubilee system to Israel’s entry into Canaan. But that doesn’t pinpoint to a precise year, although it could be the crossing of the Jordan River, which biblical chronology places at approximately 1406 BC. Or it may refer to complete conquest of the land. But from the entry, every 49 years mark a Jubilee boundary.

Daniel 9:25 — A Possible Second Layer

Most readers are familiar with Daniel 9:24–27 in some form. It describes 70 “weeks” — periods of seven years, totalling 490 years — concerning Israel and Jerusalem, culminating in the Messiah. The standard interpretation understands this as fulfilled in Jesus: his ministry confirming the new covenant, and the temple sacrificial system being rendered obsolete when the curtain tore at his death. That reading is coherent and compelling.

24 Seventy weeks (or periods of seven - Strongs H7620) are determined upon thy people and upon thy holy city, to finish the transgression, and to make an end of sins, and to make reconciliation for iniquity, and to bring in everlasting righteousness, and to seal up the vision and prophecy, and to anoint the most Holy.

25 Know therefore and understand, that from the going forth of the commandment to restore and to build Jerusalem unto the Messiah the Prince shall be seven weeks, and threescore and two weeks: the street shall be built again (twice), and the wall, even in troublous times.

26 And after threescore and two weeks shall Messiah be cut off, but not for himself: and the people of the prince that shall come shall destroy the city and the sanctuary; and the end thereof shall be with a flood, and unto the end of the war desolations are determined.

27 And he (the Messiah) shall confirm the covenant with many for one week: and in the midst of the week he shall cause the sacrifice and the oblation to cease, and for the overspreading of abominations he shall make it desolate, even until the consummation, and that determined shall be poured upon the desolate.

But verse 25 may contain an additional layer worth noticing. It describes a decree to restore and rebuild Jerusalem, followed by a countdown to the Messiah. One Hebrew word in the verse — translated variously as “again” or “a second time” — carries connotations of repetition or doubling in other Old Testament passages (see Exodus 22:4, 22:7, 22:9 and 2 Kings 2:9). This raises the possibility that the verse hints at not one but two rebuildings of Jerusalem, each launching its own 490-year countdown.

My next question is, does Daniel 9:25 match a Jubilee count?

The Hebrew reads “[There shall be] weeks seven and weeks sixty and two again”

The Hebrew construction may allow a nuance of repetition or doubling, because the word translated ‘again’ (H8147) can mean ‘second time’ or ‘double’ in other passages. This does not overturn the standard interpretation, but it opens the possibility of a secondary layer.

The prophecy begins by saying “Seventy weeks are determined” so it may be saying, there shall be 70 weeks of years, or 490 years – twice!

If that nuance is intended here, the verse could be hinting at two rebuildings of Jerusalem rather than only one:

  • the rebuilding in the Persian period that preceded Christ’s first coming
  • a later rebuilding that might begin a second prophetic countdown

If such a second rebuilding exists in history, it would naturally mark the starting point for another seventy-week (490-year) calculation.

The 60th Jubilee and Suleiman’s Walls

Counting forward from 1406 BC in 49-year blocks:

60 × 49 = 2,940 years

2940 − 1406 + 1 = 1535 AD (adjusting for no year zero)

Here’s what makes this striking: Sultan Suleiman the Magnificent of the Ottoman Empire issued a command to rebuild the walls of Jerusalem at almost exactly this time. The construction is documented by a physical inscription that still exists today, placing the work between roughly 1537 and 1541 AD, with the decree itself issued around 1535–1537.

That alignment is hard to dismiss as coincidence.


(The relevant part of this video goes between the 2 1/2 minute mark to the 3 1/2 minute mark.)

Adding another 490 years

If the second countdown begins from 1535 we are out of time. If the second countdown in Daniel 9:25 begins at the 1537 wall rebuilding:

1537 AD + 490 = 2027 AD, with the following Jubilee boundary arriving in 2028.

What that might mean is left deliberately open. This is exploration, not prediction.


June 2026 Update — AI Analysis Deepens the Picture

Depending on your point of view, this is where the article either falls apart or becomes much more interesting. Apparently, according to Maimonides the first 7-year Shmita occurred 21 years after entering Canaan. So, if the true count starts 14 years after they crossed into the land, this whole idea of a convergence falls down like a house of cards! But please check the Footnote #1 and Footnote #2 VERDICT** to see why the date I have settled on, 1401BC, is a strong contender.

If the dates below are correct, then it is compelling.

After publishing the first section I also put the framework to Claude AI for critique, asking several probing questions. The conversation that followed both challenged and refined the calculations — and ultimately produced a more precise and internally consistent result.

The key question I raised was whether the Jubilee count should begin from the Jordan crossing, or from Israel’s first actual harvest in Canaan. This matters because the Jubilee system in Leviticus 25 is fundamentally agricultural — it governs land rest, planting, and harvests. Claude’s response:

“Leviticus 23:10 establishes that the firstfruits count couldn’t begin until Israel actually reaped a harvest in the land. The argument follows naturally: you can’t count agricultural sabbaths until agriculture has started. Israel crossed the Jordan in spring, before the grain harvest. Joshua 5:11–12 records them eating from the land at Gilgal shortly after crossing, with the manna ceasing — marking the transition to Canaan’s agricultural cycle. The first actual harvest would have come weeks later, still within the same year.”

This discussion led to testing alternative years for when Israel actually conquered the entire area, and 1401 BC as a start date — representing the approximate period of Israel’s first harvest after more fully coming into the land, rather than the crossing itself. The results were striking.

Testing 1401 BC against three historical anchors

Anchor 1 — The Temple Destruction, 70 AD:

Distance from 1401 BC to 70 AD:
1401 + 70 − 1 = 1,470 years
1,470 ÷ 49 = exactly 30 cycles

A perfect hit. No remainder, no adjustment needed.

Anchor 2 — Suleiman’s Walls, 1540 AD:

60 × 49 = 2,940
2,940 − 1,401 + 1 = 1,540 AD

This lands precisely on the documented peak of Suleiman’s wall construction — although not at the 1537 AD decree to rebuild.

Anchor 3 — The 70th Jubilee and Daniel’s second countdown:

70 × 49 = 3,430 years
Take away 3,430 from 1,401 BC (start of count) + 1 = 2030 AD

And independently: 1,540 AD (wall) + 490 years = 2030 AD

Two completely independent calculations converge on the same year.

JubileeYearEvent
30th70 ADTemple destruction — exact hit
60th1540 ADSuleiman’s walls — precise match
70th2030 ADConvergence point

It’s worth noting, 2030 is also the target date of the World Economic Forum’s agenda for global economic and social transformation — making a convergence of the divine calendar with the devil’s counterfeit system!

That makes for some very interesting calculations, all with a narrow point of convergence.

The Math Explained
I asked Claude about why it subtracted 1 year for #1 anchor, but added 1 year for anchor #2 and anchor #3.

Claude’s reply: The difference is that Anchor 1 is calculating elapsed years between two dates, while Anchors 2 and 3 are calculating what AD year you arrive at from a BC starting point. These are two different operations and need different handling.
Let me think through this carefully with one consistent method:
The rule for elapsed years (BC to AD):
1401 + 70 – 1 = 1,470 ✓
The -1 accounts for no year zero. This is correct.
The rule for finding an AD year from a BC start:
If 1,470 years from 1401 BC = 70 AD, then the formula is:
AD year = elapsed years – BC start year + 1…
Hmm, let me verify:
1,470 – 1,401 + 1 = 70 ✓
So Anchors 2 and 3 using +1 are actually correct too.
The apparent inconsistency is just that Anchor 1 subtracts 1 to find elapsed years, while Anchors 2 and 3 add 1 to convert elapsed years back to an AD date. They are opposite sides of the same operation and both correct.


The 70 AD Connection — A Sequence Worth Noting

Matthew 24:1,2 & 3 link two separate things together – the destruction of the Jerusalem temple, and the end of the age that includes Jesus’ Second Coming.

This article suggests there may be an additional Jubilee link to each event – one that has never previously been seen!

The Jubilee system rested on three pillars: land rights, temple worship, and the covenant relationship between Israel and God. In 70 AD, when Roman forces under Titus destroyed Jerusalem, all three were simultaneously terminated.

  • The Temple destroyed
  • The priesthood dissolved
  • Israel driven from the land

The very mechanism that had governed Israel’s relationship to the land for over a millennium marked the moment of its own physical ending.

The sequence leading there is equally striking. The previous proposed Jubilee boundary falls around 21 AD — within the period of Jesus’ earthly life. Early in his ministry he stood in the synagogue and declared he had come to proclaim “the acceptable year of the Lord” — widely understood as a direct Jubilee proclamation, announcing the physical system fulfilled in himself.

So within one Jubilee window the spiritual Jubilee was proclaimed. At the opening of the very next, the physical system it superseded was gone forever.

Whether coincidence or design, the sequence is theologically coherent — and it anchors the entire framework to a verifiable date in ancient history.


A Pattern Within the Pattern

It is worth pausing to notice that the three historical anchors in this framework don’t fall on random Jubilee numbers — they fall precisely on the 30th, 60th, and 70th. These are not arbitrary multiples of ten. In scripture, 30 is the age of priestly commissioning and the age at which Jesus began his ministry — a number associated with readiness and inauguration. 60 appears in Daniel’s own imagery, most notably in the dimensions of Nebuchadnezzar’s golden statue. And 70 is perhaps the most loaded number in the entire Danielic framework — seventy weeks of years, seventy years of captivity, seventy nations in Genesis 10.

70 is the Biblical number of fullness and completion. The big question for me is not, will the Saviour return to mark the 70th Jubilee? It’s where does the correct count start from to arrive at the 70th? (See Footnote) Stepping back from whether or not these calculations are fully accurate, a 49-year Jubilee count does put us somewhere very near to the completion of this age of chaos, culminating with the disruption of everything, and the glorious second coming!

That the temple destruction falls on the 30th Jubilee, Suleiman’s rebuilding on the 60th, and the convergence point on the 70th — rather than on the 31st, 57th, and 68th, or any other combination — adds a layer of internal coherence to the framework that is difficult to attribute to coincidence.

If the Jubilee count is divinely structured, these three anchors may represent precisely what their numbers suggest: inauguration, renewal, and completion.

Hezekiah’s Deliverance: A 700-Year Milestone

A striking earlier picture of God’s deliverance emerges in the reign of King Hezekiah — one that carries echoes forward through the Jubilee count.

King Hezekiah stands out as one of the brightest lights among Judah’s kings. He inherited a kingdom steeped in idolatry from his father Ahaz, but he boldly reversed course. Scripture tells us he cleansed the Temple, restored proper worship, removed the high places, and led the people back to the God of their fathers (2 Kings 18:3–6). He trusted the Lord in a way few kings did.
It was during Hezekiah’s reign, (possibly about 50-70 years after Jonah went to Nineveh) in the face of an overwhelming Assyrian invasion, that one of the most dramatic deliverances in the Bible occurred.

In 701 BC — EXACTLY 700 YEARS after the 1401 BC starting point — Sennacherib’s mighty army surrounded Jerusalem. The situation was humanly impossible. Yet that very night, the angel of the Lord went out and struck down 185,000 Assyrian soldiers. By morning, the threat was gone. (Sennacherib went home and was assassinated by his own sons in the temple of his own god in 681 BC, and Nineveh was later completely destroyed within 100 years, in 612 BC.)

The exactness of 700 years from 1401 BC builds my confidence in starting the count from that date. Interestingly, this 700-year span (10 × 70) — and the number 70 carries special weight in Scripture as a marker of divine completeness and fullness (think of the 70 nations, the 70 elders, the 70 years of captivity, and of course Daniel’s 70 weeks).

While we must be careful not to overstate patterns, this 700-year interval lands the angelic destruction of the Assyrian army at a strategically “complete” point within the larger 70-Jubilee framework. It serves as a powerful historical preview: just as God supernaturally defended His people and preserved Jerusalem when the situation looked impossible under Hezekiah, we may see something even greater at the culmination of the 70th Jubilee.

It’s not a rigid prediction — my eraser is still ready — but it adds another layer of harmony to the count. A 700-year milestone built on multiples of 7, sitting inside the broader 70-cycle rhythm. God’s “nice timing” has a way of weaving these threads together.


Where Does This Leave Us?

Independent calculations — the 70th Jubilee count from 1401 BC, and the Daniel 9:25 second countdown from 1540 AD — converge on 2030 AD. The autumn of that year, around the time of the Day of Atonement in September or October, would be the natural Jubilee proclamation point within the Hebrew calendar.

What happens then? Honest answer: I’m still not 100% certain. This article looks at dates, but doesn’t actually set them. My eraser is still firmly in hand!

But A CONVERGENCE seems to be there. Make of it what you will.


You are currently inside the Bible prophecy door. (Previous article here)


Footnote #1: (Written by AI)

Based on the timeline of the Conquest and biblical chronology, here is the breakdown of how Caleb’s entry into Hebron in 1401 BC relates to the Shmita (Sabbatical year) and Jubilee counts:

​1. The Timeline and Caleb’s Age

​According to Joshua 14:10, Caleb stated that he was 85 years old when he requested his inheritance of Hebron. He noted that it had been 45 years since Moses gave the initial promise at Kadesh Barnea (when Caleb was 40 years old, as a spy):

“And now, behold, the Lord has kept me alive, as He said, these forty-five years… while Israel wandered in the wilderness; and now, here I am this day, eighty-five years old.”

  • 1446 BC: The Exodus from Egypt occurs.
  • 1445 BC: Caleb is sent as one of the 12 spies from Kadesh Barnea at age 40, and receives the promise of the land.
  • 1406 BC: The Israelites cross the Jordan River (exactly 40 years after the Exodus).
  • 1401 BC: Five years of initial heavy warfare and conquest take place. Caleb is now 85 years old (45 years after the promise) and takes possession of Hebron.

​2. The Start of the Shmita Count

​The commandment regarding the Sabbatical and Jubilee years in Leviticus 25:2 states: “When you enter the land I am going to give you, the land itself must observe a sabbath to the Lord.” 

​According to historical-chronological reconstructions (such as those matching the timeline of the conquest):

  • The Countdown Begins: The 14-year count for the first Shmita cycle officially began upon crossing the Jordan in 1406 BC. The first 7 years were spent conquering the land, and the subsequent 7 years were spent dividing it among the tribes.
  • Caleb’s Possession (1401 BC): In the 5th year after crossing the Jordan (1401 BC), Caleb successfully laid claim to and occupied Hebron, driving out the Anakim.

​3. Harvesting the Grain and “Counting to the Correct Year”

​The logic linking Caleb’s harvest to the calculation of the correct Shmita year is tied to the transition from the wilderness manna to eating the natural produce of Canaan:

  • ​In Joshua 5:11–12, right after crossing the Jordan and celebrating Passover, the manna ceased, and the Israelites ate the produce of the land (parched grain and unleavened cakes).
  • ​Because the command to count the Shmita years requires working, sowing, and harvesting the land for six years before letting it rest on the seventh (“For six years you shall sow your field…”), chronologists use the timeline of individual tribal distributions—beginning with major figures like Caleb who secured their inheritance early—to mark the definitive shift from nomadic travelers to settled agriculturalists.
  • ​By establishing that Caleb was actively farming his inherited portion in Hebron starting around 1401 BC, it serves as a historical anchor point. Counting forward or backward from these known agricultural settlements validates that the first official Sabbatical year (the 7th year of rest) took place after the land was completely subdued and divided.

To understand how Caleb’s timeline connects to the destruction of Jerusalem in 70 AD, we have to look at the math behind the consecutive 49-year Jubilee cycles and how chronologists tie biblical anchor points to historical events.

​In Jewish historical tradition (recorded in the Seder Olam and the Talmud), the year the Second Temple was destroyed by the Romans (70 AD) is specifically stated to have been a Sabbatical (Shmita) year—specifically, the year after a Sabbatical year or falling right on one depending on how the intercalary months and calendar shifts are calculated. However, major biblical chronologists use this exact window to show that 70 AD was the conclusion of a major Jubilee cycle.

​Here is how the exact alignment maps out from Caleb’s time to 70 AD:

​1. The Mathematical Span

​To get from a BCE/BC date to a CE/AD date, you add the two numbers together and subtract 1 (because there is no “Year 0” in the calendar transition).

  • Start Year: 1401 BC (Caleb settles Hebron and begins agricultural counting)
  • End Year: 70 AD (Destruction of the Temple)
  • Total Years: 1401 + 70 – 1 = 1470

​2. The Jubilee Alignment

​A Jubilee cycle consists of 49 years (seven cycles of seven-year Shmitas, with the 50th year serving as the Jubilee, which simultaneously functions as Year 1 of the next cycle).

​Dividing the total span of years, 1470, by the 49-year Jubilee span, we get 30 exact cycles.

Because 1470 divides perfectly by 49 without a fraction, 70 AD lands precisely at the culmination of the 30th Jubilee cycle relative to Caleb’s 1401 BC anchor.

​3. Why Caleb’s 1401 BC Date is the Vital Key

​Chronologists who favor this timeline point out that if you start counting the cycles from the exact year Israel crossed the Jordan (1406 BC), the math hits a snag because the first 5 to 7 years were spent entirely in active warfare. Leviticus explicitly demands that the land must be actively cultivated (“Six years you shall sow your field…”) for the count to apply.

​By using 1401 BC—the exact year the 85-year-old Caleb successfully drove out the giants from Hebron, took his inheritance, and began the first localized, stable Hebrew farming harvest—you establish the functional, agricultural “Year 1.”

​Following those exact agricultural cycles forward across history perfectly preserves the synchrony, meaning the tragic fall of Jerusalem in 70 AD wasn’t just a random historical date; it marked the precise mathematical closing of Israel’s 30th Jubilee era in the Promised Land.


Article Rewrite

Grok rewrote this article, putting it more simply.

I’ve chosen to keep both versions here.

A different Q & A Footnote follows it.

Grok Version:

Why the Jubilee Matters

Some may not realise it, but the Biblical Jubilee paints a powerful picture of the coming reign of Christ, when humanity is finally set free from Satan’s bondage. It isn’t just an ancient economic policy — it’s a prophetic shadow of liberation: debts cancelled, slaves freed, land restored. At its deepest level, it points toward the future restoration when sin and death lose their grip forever.
But the Jubilee also gives us a counting system. When you follow that count carefully using the biblical pattern, some striking alignments emerge.
First: How Does the Jubilee Count Actually Work?
49 years, not 50
There’s a common misunderstanding here (one I held for a long time myself). Many assume the Jubilee repeats every 50 years, but Leviticus 25:8 tells us to count seven sabbaths of years — seven times seven, equaling 49 years. The 50th year is the Jubilee, but it also serves as the first year of the next cycle. The two overlap. There’s no extra inserted year.
It’s like how Sunday is both the eighth day and the first day of the new week. The cycles flow continuously in blocks of 49. This detail matters enormously for the calculations that follow. Using 50-year blocks, the historical patterns fall apart. Using 49-year blocks as Leviticus specifies, they line up with surprising precision.
Where the Count Begins
Leviticus 25 ties the Jubilee system to Israel’s entry into Canaan. While the exact starting year isn’t pinpointed in Scripture, biblical chronology often places the Jordan crossing around 1406 BC. Some argue the count begins with the first harvest in the land. After careful consideration (including input from AI analysis), 1401 BC emerges as a strong, defensible anchor point — representing the time when tribes began taking possession of their inheritances and working the land.
Daniel 9:25 — A Possible Second Layer
Most are familiar with Daniel 9:24–27 and the 70 “weeks” (490 years) pointing to the Messiah. The standard reading — fulfilled in Jesus’ ministry and the end of the temple sacrificial system — remains compelling.
Yet verse 25 contains intriguing wording:
“Know therefore and understand, that from the going forth of the commandment to restore and to build Jerusalem unto the Messiah the Prince shall be seven weeks, and threescore and two weeks: the street shall be built again…”
The Hebrew allows for a nuance of repetition or “a second time.” This opens the possibility of two rebuildings of Jerusalem — and thus two 490-year countdowns: one leading to Christ’s first coming, and a later one pointing further ahead.
The 60th Jubilee and Suleiman’s Walls
Counting forward from 1401 BC in 49-year blocks:
60 × 49 = 2,940 years
2,940 – 1,401 + 1 (adjusting for no year zero) = 1,540 AD
This lands right on the peak of Sultan Suleiman the Magnificent’s rebuilding of Jerusalem’s walls (documented construction roughly 1537–1541, with activity intensifying around 1540). The alignment is striking.
Adding the Second 490 Years
If this second Daniel 9 countdown begins around the 1540 wall rebuilding:
1,540 + 490 = 2,030 AD
The following Jubilee boundary would fall in 2030–2031.
June 2026 Update — AI Analysis Deepens the Picture
After the initial draft, I ran the framework past Claude AI for critique. The conversation refined the starting point and tested it against solid historical anchors. The results became even more compelling.
Testing 1401 BC against three anchors:
Anchor 1 — The Temple Destruction (70 AD)
Elapsed years: 1,401 + 70 – 1 = 1,470 years
1,470 ÷ 49 = exactly 30 cycles. A perfect fit.
Anchor 2 — Suleiman’s Walls (1540 AD)
60 × 49 = 2,940 years from 1401 BC → lands precisely on 1540 AD.
Anchor 3 — The 70th Jubilee
70 × 49 = 3,430 years
From 1401 BC this converges on 2030 AD — matching the independent 1540 + 490 calculation exactly.
Jubilee
Year
Event
30th
70 AD
Temple destruction — exact
60th
1540 AD
Suleiman’s walls — precise
70th
2030 AD
Convergence point
The Math Explained (Simply)
Elapsed years between a BC date and an AD date: BC + AD – 1 (no year zero).
Landing year from a BC start: Elapsed years – BC year + 1.
Both operations are consistent sides of the same coin. The anchors hold up cleanly under this method.
The 70 AD Connection — A Sequence Worth Noting
In 70 AD, the destruction of the Temple, the dissolution of the priesthood, and the exile from the land ended the very system the Jubilee represented. It happened on the 30th Jubilee — the same number associated with priestly commissioning and the start of Jesus’ ministry.
Just one Jubilee cycle earlier (around 21 AD), Jesus had stood in the synagogue and declared “the acceptable year of the Lord” — proclaiming the spiritual fulfillment of Jubilee in Himself. Then, at the next major boundary, the physical shadow was removed. The sequence carries a profound theological coherence.
A Pattern Within the Pattern
Notice how the anchors fall on the 30th, 60th, and 70th Jubilees. These aren’t random. In Scripture, 30 speaks of readiness and inauguration, 60 appears in prophetic imagery, and 70 consistently signals fullness and completion (70 weeks, 70 years of captivity, 70 nations).
The question isn’t necessarily whether the Saviour will return exactly on the 70th Jubilee — but whether the count has been guiding us toward a major convergence.
Where Does This Leave Us?
Two independent lines — the 70th Jubilee from 1401 BC, and the second Daniel 9 countdown from the 1540 wall rebuilding — both point toward 2030 AD. The autumn season (around the Day of Atonement) would be a natural point for a Jubilee proclamation in the Hebrew calendar.
What happens then? I’m still not 100% certain. This remains exploration, not prediction. My eraser is still firmly in hand!
But a convergence does seem to be there. And 2030 also happens to be the target year for the World Economic Forum’s major global transformation agenda — a divine calendar intersecting with a counterfeit system. Make of it what you will.

** Footnote #2 – More AI Research, using Gemini and Grok

Apparently, according to Maimonides the first 7-year Shmita occurred 21 years after Israel entered Canaan. Who was he, and is that correct?

Maimonides (also known by the Hebrew acronym Rambam, 1138–1204) was a brilliant medieval Sephardic Jewish philosopher, Torah scholar, and physician. Born in Córdoba, Spain, he eventually settled in Egypt, where he served as a community leader and royal physician. He is famous for writing the Mishneh Torah, a monumental, comprehensive code of Jewish law.
Regarding his timeline for the Shmita (the Sabbatical year), yes — your information tracks exactly with his text.
In Mishneh Torah, Hilchot Shmita V’Yovel (Laws of Sabbatical and Jubilee Years), Chapter 10, Halacha 2, Maimonides breaks down the math:
“The 14-Year Delay: He explains that the biblical commandment to count Shmita cycles depends on everyone recognizing and cultivating their own family plots of land (‘Six years shall you sow your field…’). Because it took the Jewish people 7 years to conquer Canaan and another 7 years to divide the territory among the tribes, the counting didn’t begin immediately.”
The actual farming and official tracking started in the 15th year after entry. Therefore, six years of farming occurred, and the 7th year of the official cycle — which was the 21st year after they crossed into the land — became history’s first official Shmita year.
His calculation remains the foundation for how traditional Jewish calendar timelines reconcile ancient history with the modern 7-year Shmita cycle observed today in Israel.

Putting Maimonides aside — Could an earlier start date be justified?

Yes — and it is rooted in a more literal reading of the biblical text itself.
The Literal Torah Text (The Earliest Possible Date)
In Leviticus 25:2, God commands Moses: “When you come into the land which I give you, then shall the land keep a sabbath unto the Lord.”
A plain-text reading suggests the clock should start ticking the exact moment their feet crossed the Jordan River into Canaan. Under this interpretation, the very first year in the land is Year 1. Consequently, six years of farming would follow, making the 7th year after entry the first Shmita. This moves the first Shmita up by 14 years compared to Maimonides’ timeline.
Why this earlier date is defensible
The manna stopped immediately upon entering the land (Joshua 5:11–12). They had to begin eating from Canaan’s produce right away and start farming to survive.
A literalist can argue the land’s obligation to rest should logically begin 7 years later, not 21.
Many modern biblical chronologists and historians use the immediate entry date as Year 1. For example, some models pin the entry into Canaan at 1406 BC, which sets the very first Shmita at 1399 BC (the 7th year), completely bypassing the 14-year delay for conquering and dividing the land.
Why the Sages rejected the literal start
The Rabbinic tradition (Sifra, Talmud, etc.) overrode this based on legal phrasing. The Torah says “Six years you shall sow your field…” The Sages argued a person cannot legally own “their” specific field while the nation is still fighting a war of conquest or while the land is being distributed by lottery. To them, the land didn’t truly become “yours” until the full 14-year process was complete.
So while the 21st-year start won out in Jewish law, a 7th-year start is highly justifiable if you read the command as tied more to the geography of the land than to completed legal ownership.

If I calculate from 1401 BC, is that unreasonable? Could it be a correct year?

VERDICT

Using 1401 BC is a thoroughly researched landmark. If your model sees 1401 BC as the year Caleb and the first families took physical possession of their lands to begin farming in earnest, it serves as an excellent anchor for history’s very first Shmita cycle. It doesn’t contradict the text — it simply interprets the starting trigger differently from later rabbinic tradition. Both views have merit, but 1401 BC produces remarkably clean alignments with the Temple destruction, Suleiman’s walls, and the 2030 convergence. That alone makes it worth serious consideration.


NEXT: