3 others in the registry answer to the name Akkub. Every Akkub in the Bible
person
Akkub
עַקּוּב
Akkub was a Levite who served as a gatekeeper in the Temple during the post-exilic period.
- verses
- 5
- first named
- 1 Chronicles 9:17
- last named
- Nehemiah 12:25
- period
- Exile and Return
- tribe
- Levi
Description
Who was Akkub?
Akkub was a Levite who belonged to the family of gatekeepers during the post-exilic period, after the return of the Jews from Babylonian captivity. He is mentioned in several lists of Levites and Temple servants in the books of 1 Chronicles, Ezra, and Nehemiah.
In the genealogy of the Levites who settled in Jerusalem, Akkub is listed among the gatekeepers who were responsible for guarding the entrances to the Temple. (1Ch.9.17) The gatekeepers played a crucial role in maintaining the sanctity and security of the Temple premises.
Akkub is also mentioned among the Levites who returned to Jerusalem with Zerubbabel, the governor of Judah, after the Babylonian exile. (Ezr.2.42; Neh.7.45) This indicates that he or his descendants were part of the group that helped rebuild the Temple and restore the worship practices in Jerusalem.
Later, during the time of Nehemiah, Akkub is listed among the gatekeepers who were entrusted with the task of guarding the storehouses of the Temple gates. (Neh.11.19) These storehouses likely contained the tithes, offerings, and other resources necessary for the maintenance of the Temple and the support of the Levites.
In the context of the dedication of the rebuilt wall of Jerusalem, Akkub is mentioned among the Levites who were involved in the purification rituals and the celebration that followed. (Neh.12.25)
Akkub's repeated mention in the lists of Levites and Temple servants highlights the importance of the gatekeeper's role in the post-exilic Jewish community. They were responsible for maintaining order, protecting the Temple, and ensuring that the sacred space remained pure and secure.
Relations
Direct connections
Every entity the graph places in a stated relation with this one, grouped by the kind of link. Each relation is authored once and its inverse derived, so both ends always agree. Rows marked “registry” come from the identity spine rather than from a verse, and a row marked “which bearer is the source’s decision” is one where the name could have meant more than one person. The last group is not a relation at all — it counts the events two entities stand in together.
Places
Where this happens
A person is placed by the events they take part in, and an event has to clear three things to place them: it must say where it happened, that place must be one the gazetteer can put a coordinate on, and the verse must report it rather than foretell, command or ask it. Nothing anchored here clears all three. Where the text names a setting no gazetteer surveys — a vineyard, a palace, a plot of ground — it is left off rather than guessed at; where a place is named only in a prophecy, the map does not draw what was said to be coming as though it had happened; and a place reached only through a relation is not inherited, because standing beside somebody is not being somewhere.
No verse Atlas has read as a report puts this person anywhere.
Not read yet
Read it
Where to read it
Every verse of the text carried here that names this entity — 5, across 3 books.
Onward
Where this page goes
Nothing in the graph stands one hop from this entity yet. These are the best-connected entities of the same type, so the page still ends somewhere. Descriptions by STEPBible TIPNR.
Sources