Worship With Us Sunday School10 AM Sunday Morning11 AM Sunday Evening4 PM Thursday Night7 PM
1377 S 20th St, Louisville, KY 40210 Contact
True Words Baptist Church — Revelation 21:5
My TWBC Plan Your Visit Give
DEEP KJV WORD STUDY

Shishak

Begin with the exact English word as it appears in the King James Bible. Follow its whole-Bible usage, book distribution, related indexed forms, Webster 1828, every occurrence, and the occurrence-specific Hebrew/Aramaic/Greek mappings behind it.

7exact KJV occurrences 7Old Testament 0New Testament 2books containing the word 1mapped Strong's IDs 7occurrence-specific Strong's links
FIRST OCCURRENCE

1 Kings 11:40

Solomon sought therefore to kill Jeroboam. And Jeroboam arose, and fled into Egypt, unto Shishak king of Egypt, and was in Egypt until the death of Solomon.

Read in context →
LAST OCCURRENCE

2 Chronicles 12:9

So Shishak king of Egypt came up against Jerusalem, and took away the treasures of the house of the LORD, and the treasures of the king's house; he took all: he carried away also the shields of gold which Solomon had made.

Read in context →
KJV DISTRIBUTION

Where Shishak appears.

This is exact English-word usage from the canonical KJV token index, not a Strong's estimate.

1 Kings 22 verses 2 Chronicles 54 verses
ORIGINAL-LANGUAGE MAP

Which Hebrew, Aramaic, or Greek words stand behind this KJV word?

These relationships come from exact verse + token-position mappings. We do not assume that one English spelling always equals one Strong's number. A single English token can also carry more than one source tag, so the Strong's-link total can exceed the number of English occurrences.

Strong's data is a concordance/lexical reference layer. Scripture context controls interpretation. Lexical source data is shown separately from future TWBC editorial teaching.

EVERY OCCURRENCE

Read the word in context.

5 occurrences match the current filters. Each row keeps its exact KJV token position so Original Word and TSK remain occurrence-specific.

Clear
2 Chronicles 12:2
H7895

And it came to pass, that in the fifth year of king Rehoboam Shishak king of Egypt came up against Jerusalem, because they had transgressed against the LORD,

2 Chronicles 12:5
H7895

Then came Shemaiah the prophet to Rehoboam, and to the princes of Judah, that were gathered together to Jerusalem because of Shishak, and said unto them, Thus saith the LORD, Ye have forsaken me, and therefore have I also left you in the hand of Shishak.

2 Chronicles 12:5
H7895

Then came Shemaiah the prophet to Rehoboam, and to the princes of Judah, that were gathered together to Jerusalem because of Shishak, and said unto them, Thus saith the LORD, Ye have forsaken me, and therefore have I also left you in the hand of Shishak.

2 Chronicles 12:7
H7895

And when the LORD saw that they humbled themselves, the word of the LORD came to Shemaiah, saying, They have humbled themselves; therefore I will not destroy them, but I will grant them some deliverance; and my wrath shall not be poured out upon Jerusalem by the hand of Shishak.

2 Chronicles 12:9
H7895

So Shishak king of Egypt came up against Jerusalem, and took away the treasures of the house of the LORD, and the treasures of the king's house; he took all: he carried away also the shields of gold which Solomon had made.

WEBSTER’S 1828

English meaning and historical usage.

Dictionary data is kept visibly separate from Scripture and from lexical Strong's data.

No Webster 1828 entry was found for this exact KJV form or its conservative base-form candidates.

SOURCE & METHOD

Know what each layer is—and what it is not.

KJV English usageExact token counts, verse counts, first/last occurrence, and book distribution come from the canonical TWBC PCE KJV index.
Webster 1828Historical English dictionary material is reproduced as dictionary data, not as inspired Scripture or TWBC commentary.
Original Word / Strong'sHebrew, Aramaic, and Greek links attach by exact verse + KJV token position. No global “English word always equals Strong's ID” rule is used.

Curated TWBC teaching will remain a separate editorial layer. Raw source data is never silently rewritten to force a doctrinal conclusion.