One other person, place or group in the registry answers to the name Nekoda. Every Nekoda in the Bible
person
Nekoda
נְקוֹדָא
The descendants of Nekoda were among those who could not prove their priestly lineage after returning from the Babylonian exile.
- verses
- 2
- first named
- Ezra 2:60
- last named
- Nehemiah 7:62
- period
- Exile and Return
- role
- Man
Description
Who was Nekoda?
Nekoda is mentioned in Ezr.2.60 and Neh.7.62 as one of the families who returned to Jerusalem from Babylonian captivity but were unable to prove their lineage as Israelites or priests. This incident occurred during the time of Zerubbabel, who led the first group of exiles back to Jerusalem around 538 BC.
According to the text, the descendants of Nekoda, along with those of Delaiah and Tobiah, sought to be included among the priests but could not find their names in the genealogical records. As a result, they were considered unclean and excluded from the priesthood.
The importance of genealogical records in determining priestly lineage is evident from this account. The priests were required to prove their descent from Aaron, the first high priest, to be eligible for service in the temple. The inability of the Nekoda family to establish their priestly heritage suggests that their ancestors may have been among those who had intermarried with non-Israelites during the exile, thus compromising their lineage.
The exclusion of the Nekoda family from the priesthood highlights the significance of maintaining the purity and integrity of the priestly line. It also underscores the challenges faced by the returning exiles in reestablishing their religious and social order after years of captivity in a foreign land.
Apart from this incident, no further information is provided about the Nekoda family or their subsequent role in the post-exilic Jewish community.
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.
Ancestor of
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 — 2, across 2 books.
Onward
Where this page goes
Not the direct relations above — these are one hop further out, ranked so that a rare shared connection outweighs a common one. Descriptions by STEPBible TIPNR.
Sources