(more features coming that can be read below)
-<>- book, chapter & verse counts of the Hebrew/Greek Bible database
The Hebrew Bible database of the Old Testament uses the Westminster Leningrad Codex (WLC).
The Greek Bible database of the New Testament uses the Scrivener’s Textus Receptus 1894.
This Bible database has 31102 verses & 1189 chapters like the King James Bible since I use a Hebrew-English interlinear version of the WLC (2013 version).
Features of the Hebrew/Greek Bible Gematria Database
• Choose 15 different gematria systems which are: reduced, ordinal, standard, Full reduced, Full ordinal, Full standard, reverse reduced, reverse ordinal, reverse standard, ord + sta, red + ord + sta, Full ord + Full sta, Full red + Full ord + Full sta, rev ord + rev sta & rev red + rev ord + rev sta.
You can read about these gematria systems here: Chapter I. Introduction to Gematria, Mathematics and Methods
• Find Bible verses & words with a specific value. It will search in the gematria system selected. • Search by verse order. There are 31102 verses in this Hebrew/Greek Bible database and you can enter an order over this to find verses when you count by rotation in cycles by the number of verses. So if you enter 31103 it directs you to the first verse. • Search by book, chapter & verses numbers in the Bible. You also can enter the book name or abbreviation instead of the book number. • Find a Hebrew word by Hebrew input. Find a Greek word by Greek input. Find an English word in the KJV by English input. • Strong’s concordance is used here so you can find words with it. Just input a Strong’s number starting H or G [example: H7225 or G3056]. • You can also investigate the definitions of words in the Bible with the Strong’s concordance feature when you click on the magnifying glass next to a word in the Strong’s table on the left side. • Results of different methods used to decode Bible verses with gematria, and you can also find methods of the verses. These methods are: <>Nr.W = Number of Words– – – Nr.L = Number of Letters– – – Nr.W + Nr.L
<>FLL = First & Last Letters – – –CL = Center Letter(s)– – –FLCL = First, Last & Center Letters <>2 FLL = Two First & Last Letters – – –3/4 CL = Three/Four Center Letters– – – 2 FLL + 3/4 CL = Two First & Last Letters + Three/Four Center Letters <>FLW = First & Last Words– – – CW = Center Word(s) – – – FLCW = First, Last & Center Words <>2 FLW = Two First & Last Words– – –3/4 CW = Three/Four Center Words – – – 2 FLW + 3/4 CW = Two First & Last Words + Three/Four Center Words <>W. surr. CW = Words surrounding Center Word(s) <>W. up to CW = Words added up to the Center Word (if there are two center words then it adds to the first of these) <>W. from CW = Words added from the Center Word to the last word (if there are two center words then it adds from the second of these) <>ultra calculation = (number of letters x product of letters)/(number of words x product of words) <>This method will not show the decimal sign & a maximum of 12 digits, so if you want the result with a decimal sign or more digits of the result then <>use the “Get gematria methods for verse(s)” at the end of the Diverse calculators page. And this method will not work on the added gematria systems, <>it will only work on the 9 singular gematria systems. <>If you want results of more methods than these or even get results of integrated verses, then use the two last tools at the end of the Diverse calculatorspage. • More improvements and features are coming like the feature that translates the Hebrew & Greek words into English when you search by gematria. -<>- One problem with this database is that the English KJV text misses punctuations, and I don’t think that I will get it fixed as I did a mistake on that part. I am very sorry for this, but getting the Hebrew & Greek text perfect was priority #1. So please do not copy-paste KJV translations from the database into your work because of this, but rather get the KJV verse from another website like here. -<>-
Another thing worth mentioning is that many verses have messed up Strong’s listing as you see in Vs(1618). You spot it fairly fast though. The website with the best Strong’s dictionary is blueletterBible.org. So use that website if you want the Strong’s listing of a verse that is off in my database. That website has a better Strong’s dictionary overall as it will translate many words into English that my database does not, so if you want to study Hebrew/Greek words of the Bible in general then I recommend that website. My website is focused on gematria. -<>- -<>-
-<>- grovescenter.org is in charge of the electronic WLC, while Tanach.us which also develops a WLC electronic database went on different paths after the 2016 version. grovescenter.org is currently going through changes in their website so they do not have a database there for users, but Tanach.us does. These two organizations do not deal with the English-Hebrew interlinear version, so their WLC has 46 fewer verses since they don’t use the English King James version ordering of verses as this website does. Many of the verses in the original WLC and the English-Hebrew interlinear WLC are identical with identical verse orders, but there are a lot of verses that are not also. All verses have been personally checked by me so that this database does not suffer from gematria errors, since they come automatically when dealing with Hebrew. -<>- -<>- I did only two critical changes to the Hebrew-English interlinear WLC I use on this website, and that was to swap verse# 12008 (2 Chro 36:14) with 2 Chro 36:14 from another interlinear database. Every other Hebrew-English interlinear database I have checked uses this version of this verse, so it should be correct to switch it. Nehemiah 7:68 missed because some versions of the Old Testament miss it due to a scribal error. I replaced it so the verse is there as it should be. Shane had to remove the markings of the Qoph ק & kaf כ which are markings for commented words. All commented words are removed by me as these things were not in the original texts, but were added by scribes. Including those would mess up the codes and give us wrong total values, so there was no option to include them.
The features of this database were developed by Shane Pillay who was hired by me. Special thanks to him for putting in 2 and a half years of work into this website & the Hebrew/Greek database. He did excellent work as you can see. His part of work was instrumental in the part of getting my book as incredible as possible.