In October of 2022 I started building a
particular kind of searchable Bible numbers database. The
Lord Jesus showed me what to do, how to do it and also
gave me the name for it:
The “Atlas Pages Project”
The goal of the Project is to uncover hidden
Bible verse relationships. These relationships are based
on shared prime number factors and their placeholders
hidden inside each verse’s numbers.
Each book of the Bible has its’ own Atlas
Page and all verses studied within a certain Bible book go
only on to that dedicated Atlas Page. There is
cross-referencing within the Project’s pages, though.
With some exceptions the Atlas Page verse
entries are limited to two core numbers that are common to
all Bible verses:
1) Bible verse number
This is the verse’s numerical placement in
the 66 Bible books starting with Genesis 1:1 (Verse 1) and
ending with Revelation 22:21 (Verse 31102)
2) Total verse gematria (TVG)
This is the verse’s total gematria value
when all individual word values are added together. In the
verse entries the initials TVG stand for this value.
Which verses get entered:
Only the Bible verses that I think or know
are of prophetic significance, are of personal interest,
or the Lord specifically instructs me to include, are
entered into the database.
So, this is not a number database for all
the verses of the Bible. It’s a very small and targeted
subset rendered in a particular format. Others have built
all inclusive Bible verse and number databases and without
those sites this endeavor would not be possible.
The three websites I use for the source data
are credited at the end of this post with great
appreciation.
Before I show you how this actually works
let me first say that …
…anyone can do this. It’s extremely simple.
Anybody can follow the format, enter their own subset of
Bible verses (plus the numbers) and then get their own
verse relationship results. You just have to keep feeding
verses into archive.
The App I used:
The note app that I use to build the Atlas
Pages is called “Obsidian”.
Go to the link below to find out about it
and download it if you want to. It’s free for personal use
and has desktop and mobile versions; all are very powerful
and full of features. The app is in constant development:
It’s a markdown app and I’m building all of
the pages using the mobile version only.
I settled on Obsidian chiefly because I
could structure it to yield search results the way I
wanted them delivered. There are lots of instructional
videos online about getting started with Obsidian. Still,
if you have some other app of choice, use it.
The format:
Each Atlas Page verse entry is basically set
up in its’ simplest form as follows:
Scripture reference
Scripture verse text, in English.
Verse number (…Highest Prime Factor)<
prime placeholder (…Highest Prime Factor) etc
TVG (..Highest Prime Factor)< prime
placeholder (…Highest Prime Factor) etc
Tags: #tag1 #tag2 #tag3 #etc
Here is an actual Bible verse example
written the way it appears on the John Atlas page:
John 3:16
"For God so loved the world that He gave His only begotten
Son, that whoever believes in Him should not perish but
have everlasting life."
Verse 26137 (59 x 443)< pr87
TVG 14660 (... 733)< pr131 < pr33
#_59_ #_443_ #_87_ #_733_ #_131_
Looking at the Bible verse number example
above shows that 26137 has a highest prime factor of 443.
To the right of that shows that 443 is prime
number 87. That’s what pr87 means.
87 is 443’s placeholder number.
(Note: This is all based on using “1” as a
prime number).
Looking at the TVG number example above
shows that 14660 has a highest prime factor of 733.
To the right of that shows that 733 is prime number 131.
That’s what pr131 means.
131 is 733’s placeholder number.
…but notice the TVG example goes one step
farther than the Bible number entry. 131 is also a prime
number, thus it has its own placeholder. To the right of
that shows that 131 is prime number 33. That’s what pr33
means.
33 is 131’s placeholder number.
Special formatting note:
I use ellipses (…) in the entries to stand for factors
that are too small to include. I (usually) don’t include
factors below 37 as they are too common and return too
many results.
One last bit of data is left to include for
each verse’s Atlas Page entry, tags.
You can see that from above that I’ve tagged
all of the primes from the Bible verse and TVG numbers. I
did not include the non-prime 33.
The John 3:16 example shows you the bare
minimum form that a Bible verse entry must take for the
Project to return accurate verse results.
The verse entries can have more data in them
such as targeted key words in the verse, Strong’s numbers
and factors for those key words, in-text gematria for
those key words plus those factors etc, but all follow
this basic format.
Those additional data specifics will be
discussed in Part (2) which is upcoming as well as
examples of verses shown to be connected to each other via
these methods.
Special important note about the verse
entries and Obsidian Search:
For Obsidian to find separate verse results
across all of the Atlas Pages in the Project, there must
be a “return” (a line space) between each Bible verse
entry on whatever Page it is found.
At the time of this writing, my Gospel of
John Atlas Page has 37 total verses entered from that
book. Each verse has a “return” above and below all of the
verse data to place a separation between all verses. This
is required.
Now when I search across the entire Project
(all 66 Bible book Atlas Pages) for the tag (as an
example) #_733_ , or even just “733”, Obsidian will only
return the specific verses that contain that data. It
won’t return results from an entire Atlas Page of
entries.
Watch for a follow-up article:
Atlas Pages Project (Part 2).
Jesus is Lord.
********
As mentioned above, I use these three number
databases to find out the core numbers and their prime
factors. Many thanks to their authors:
Wade Balzer’s powerful site
(of which I use some):